Estoras Group

Call Directions Website Contact the business

Estoras Group Contact information, map and directions, contact form, opening hours, services, ratings, photos, videos and announcements from Estoras Group, Vancouver, BC.

Six in seven boards have no established strategy for how AI will reshape the workforce they are accountable for.Deloitte...
2026-11-20

Six in seven boards have no established strategy for how AI will reshape the workforce they are accountable for.

Deloitte's Global Boardroom Program, released this month, found that only 16% of organizations have a strategy for the workforce impact of technology transformation. Meanwhile, 49% of directors report their boards do not consistently include human capital considerations in AI and technology-transformation discussions, and nearly half have limited or no oversight of how investment divides between technology infrastructure and workforce enablement.

The capital is committed. The workforce side of the transformation is governed by exception.

Three moves that close the gap:

1. Put the workforce impact of AI on the board agenda as a standing item, not a slide inside the technology update. If the technology plan changes the work, the people plan belongs in the same paper.

2. Demand visibility into the investment split. How much of the transformation budget buys systems, and how much buys the capability to run them? Boards that cannot answer that are approving a strategy they cannot see.

3. Tie workforce metrics to transformation milestones. Attrition in critical roles, internal mobility, time-to-competence in redesigned jobs. These are the early indicators of whether the transformation is landing or leaking.

PM61, a majority-position portfolio company of Estoras Group, works at the intersection of IT and corporate stakeholders, where governance gaps between technology ambition and workforce reality surface early: helping leadership teams plan and execute technology solutions the wider organization is actually prepared to operate.

As partner-owners, our senior involvement keeps transformation decisions accountable to the whole operating system they change, not only the systems they install.

If your board cannot state its workforce strategy for AI in one paragraph, the technology strategy is not finished either.

STRATEGY IS A CHOICE, not a catalogue of everything a company could pursue.Strong corporate strategy makes the trade-off...
2026-11-16

STRATEGY IS A CHOICE, not a catalogue of everything a company could pursue.

Strong corporate strategy makes the trade-offs explicit: where to concentrate attention, capability, and management energy, and what not to pursue.

That discipline is reflected in EDX Motorsports’ focused offering. Its integrated karting-to-F4 pathway brings together arrive-and-drive programs, elite driver coaching, mechanical and race support, transport and storage, engine tuning, and equipment sales. EDX is also a certified Ligier Ambassador and authorized reseller.

The result is a clear platform with defined priorities, rather than a collection of disconnected activities. Estoras Group holds a minority position in EDX Motorsports and supports the business as a partner-owner, bringing senior involvement and advice aligned solely with the company’s best interests.

The strategic question is simple: which opportunities deserve your organization’s full commitment, and which should remain outside the plan?

Explore our approach: www.estorasgroup.com/solutions
Contact us: [email protected]

2026-11-13

Most companies are good at fixing problems. Very few are good at making them stop coming back.

The difference lives in what happens after the fix. A failure gets patched, the ticket closes, everyone moves on, and three months later the same problem returns wearing a different date. The organization is treating symptoms at speed while the cause quietly renews its subscription. Root-cause work is not slower firefighting; it is the discipline that eventually retires the fire.

The warning signs are familiar: the same incident recurring on a quarterly cadence under a new ticket number; fixes documented as "user retrained" or "restarted the system"; workarounds so entrenched they appear in onboarding documents; nobody able to say how many times this problem has happened before; a corrective-action log that records completion but never verification; firefighting celebrated in performance reviews more than elimination.

The cost compounds quietly. The same defect, delay, or downtime gets paid for repeatedly while appearing on no budget line. Capacity is permanently donated to repeat failures. Teams learn that speed of response matters more than depth of fix, so shallow patches become the culture, and leadership sees a stable operation that is actually a loop.

Treating it as a discipline rather than a heroic effort looks like this: separate correction from corrective action, because restoring service is not the fix; require every material recurrence to name its cause in physical, human, or systemic terms, with "human error" ruled out as a conclusion rather than accepted as one; verify effectiveness on a dated cadence after implementation instead of closing the ticket and moving on; track repeat-incident rate as an owned metric with a named owner; protect time for cause analysis the way capacity is protected for production; and celebrate the problem that stops coming back, not the fastest patch.

As a partner-owner, Estoras Group works alongside leadership to turn structural complexity into operational clarity and durable growth. Companies that compound operationally are rarely the ones that fix things fastest. They are the ones whose fixes stick, so each quarter starts with fewer fires than the last.

What is the oldest recurring problem in your operation, and what has every previous fix actually changed?

2026-11-11

Most companies can name every asset on their balance sheet; very few can name where their operating knowledge actually lives.

The real manual for how work gets done rarely sits in a document. It sits in the heads of a handful of long-tenured people: which supplier to call when the standard one fails, which customer requires what phrasing on a spec, why step four happens before step two, which report is trusted and which is theater. It is tribal, unwritten, and invisible until the day it walks out the door.

And unlike equipment or inventory, this asset depreciates silently. It is not amortized, not tracked, not owned. Attrition, retirement, and internal promotion all quietly transfer it or erase it, and the loss rarely shows up in a metric. It shows up later: a process that takes three weeks instead of three days, a workaround nobody can explain, a supplier relationship lost because nobody knew why it mattered.

The warning signs are easy to spot once you look:

The same questions reach the same two or three veterans every week, and their calendars are full of interruptions. New hires take months to reach full productivity and nobody can say why. Process documents exist but describe how things were done years ago, so people ignore them and ask a person instead. A departure last year is still causing small, unexplained friction today. And the answer to "why do we do it this way" is, too often, "because we always have."

The cost compounds quietly. Decisions slow down or get made worse because context is missing. Risk concentrates in the people nobody can afford to lose, which makes succession and growth planning harder than it should be. And when the company scales, every new site, shift, or team invents its own version of the same work.

The fix is procedural, not heroic:

Map the handful of processes where lost knowledge would hurt most, not every process. Capture the actual way work runs, including the workarounds, then decide which workarounds should become the standard. Attach an owner to each critical piece of knowledge, the way you would attach an owner to any other asset. Make documentation part of the work, written by the people doing it, refreshed when the process changes rather than on some annual ritual. And when someone with rare knowledge plans to leave, run a deliberate transfer, not a two-week handover and a farewell lunch.

Companies that grow steadily are rarely the ones with the most talented individuals but the ones whose knowledge outlives any individual, so the organization gets smarter every year instead of starting over.

Where does the most important knowledge in your operation live today, and could the business run without it tomorrow morning?

Change management is not complete when the announcement is made. It succeeds when people understand what is changing, wh...
2026-11-09

Change management is not complete when the announcement is made. It succeeds when people understand what is changing, why it matters, how their roles are affected, and where they can contribute.

That requires clear communication, stakeholder involvement, thoughtful engagement planning, and consistent reinforcement, turning awareness into adoption.

Estoras Group’s Change Management capability helps organizations manage the human side of transformation through clear communication channels and solid engagement plans that involve key players and stakeholders.

Archive Digital Marketing Agency complements this work with coordinated communication, creative development, digital content, user journeys, marketing automation, and campaign ex*****on. Together, these capabilities can help organizations deliver the right message to the right audience, across the right channels, at the right moment.

Archive is majority-owned by Estoras Group. As a partner-owner, we bring senior involvement and practical advice aligned with each client’s best interests, helping change move from intention to measurable adoption.

Learn more: www.estorasgroup.com/solutions
Contact: [email protected]

What helps your organization turn change communication into lasting adoption?

2026-11-09

Most companies know what needs to be produced this month. Very few can explain why it gets produced in that order.

Scheduling gets the attention: plans, calendars, capacity charts. Sequencing rarely does. Yet the order in which work moves through a plant, a service queue, or a project pipeline is one of the largest untapped productivity levers in a mid-market operation. Same demand, same equipment, same people: a different sequence produces different throughput, different lead times, and a different cash position. When sequencing is left implicit, it gets decided hourly by whoever shouted first or whichever job landed in the queue earliest, and the cost of that is real.

The warning signs are familiar to anyone who has stood on the floor of a busy operation. Priorities churn mid-week as hot jobs compete for the same resources, and expediting is routine and celebrated rather than treated as a defect signal. Batch sizes are set by equipment habit or a system default rather than by changeover and inventory economics. Work piles up invisibly in front of the constraint while upstream stations stay busy, so the plant looks fully loaded while the bottleneck starves or runs the wrong work. Delivery dates are defended with overtime and expedited freight instead of schedule discipline. Sales promises dates operations never actually loaded into the sequence. And when you ask what rule decides which job runs next, nobody can state one.

The consequences arrive quietly. Capacity is consumed by changeovers instead of output. Lead times inflate even as utilization metrics look healthy, because busy is not the same as productive. Working capital sits in work-in-process that no one chose to build. Firefighting becomes the operating system rather than an exception. And the most profitable orders wait behind whoever escalated loudest.

Closing the gap is procedural, not heroic. Make the sequencing rule explicit, whether that is earliest due date, critical ratio, or margin per constraint-hour: write it down, teach it, and enforce it. Protect the constraint by scheduling around it, keeping it fed, and never letting it wait on a material shortage or a decision. Size batches on changeover and inventory economics rather than habit. Cap work-in-process so queues expose problems instead of hiding them. Freeze the schedule for a defined window and route every priority change through one gate with its cost attached. Measure schedule adherence and on-time completion, not just utilization. And re-sequence on a stated cadence rather than every time someone walks onto the floor with an exception.

Companies that deliver reliably are rarely the ones with the most capacity. They are the ones whose sequence turns the capacity they already have into on-time, profitable throughput.

What rule does your operation use to decide what runs next, and could anyone in the building write it down?

Estoras Group works alongside leadership as a partner-owner, turning operational visibility into stronger profitability, resilience, and scalable growth, with advice aligned solely with each company's best interests.

2026-11-06

Most companies know the size of their order backlog down to the dollar. Very few can tell you how good what is in it actually is.

A backlog is treated as a scoreboard: the bigger the number, the stronger the business. But a backlog is not one asset. It is a portfolio of orders that differ wildly in margin, deliverability, and durability, and the size of the number says nothing about the quality of what sits behind it. Celebrating a record backlog while the wrong orders fill it is one of the quieter ways a strong year becomes a weak one.

Warning signs it is happening:
• Backlog reported in revenue or units, never in margin or contribution
• Orders booked with delivery dates operations never agreed to
• Cancellation and reschedule rates untracked, so the "firm" book quietly leaks
• A large share of the backlog resting on a handful of orders or one customer's release schedule
• Capacity plans built from backlog numbers nobody has validated against real throughput
• Sales recognized and rewarded at booking while operations absorbs what was promised

The consequences arrive in sequence. Capacity fills first with whoever booked earliest, not with the most profitable work. The cash cycle stretches as underpriced orders consume material and hours at thin returns. Delivery dates slip, and the trust that took years to build erodes one missed commitment at a time. By the time the backlog converts, the revenue is real but the profit is not what the scoreboard promised.

What to do about it:
• Measure backlog in margin and ship-ready terms, not just dollars
• Validate deliverability against demonstrated capacity before the order is counted as secured
• Track cancellation and reschedule rates as a quality signal, not an administrative footnote
• Age the backlog: stale orders that keep slipping are liabilities wearing an asset's clothes
• Tie booking incentives to deliverable margin, not booking volume
• Review order-book mix against capacity in a standing cadence, before the quarter is committed

The companies that grow steadily are rarely those with the biggest backlog. They are the ones whose backlog would still look good if it were sorted by margin instead of size.

Where does your backlog rank its orders today: by when they were booked, or by what they are worth?

Estoras Group works alongside leadership as a partner-owner, turning operational visibility into stronger profitability, resilience, and scalable growth. Our advice is aligned solely with each company's best interests.

2026-11-04

Most companies forecast every month. Very few can tell you how good their forecasts actually are.

Forecast accuracy is treated as a fact of life rather than a measured process. The number gets revised, the explanation gets delivered, and the accuracy of the forecaster itself never enters the conversation. That is a gap, because a company that cannot measure its own forecasting has no way to know whether it is steering with an instrument that works.

The warning signs are consistent:

Every forecast revision is explained after the fact, but nobody records what the forecast said and what actually happened.
Forecast error gets discussed as a story (weather, timing, a big customer moved) rather than as a number with a trend.
The same function is systematically over-optimistic quarter after quarter, and leadership keeps anchoring on its numbers anyway.
Accuracy is measured at the level where the error averages out nicely instead of at the level where decisions are made.
The sales pipeline, the demand plan, the financial outlook and the capacity plan each carry their own picture of the future, and nobody reconciles which one the company is actually betting on.
Forecast accuracy never appears in any operating review, so no one is ever asked to improve it.

The consequences compound quietly. Inventory and capacity decisions get sized against numbers nobody has calibrated. Cash planning runs on a revenue curve whose error rate is unknown. When a real miss arrives, leadership cannot tell whether the market moved or the instrument has always been off, so the wrong lesson gets learned.

The fixes are procedural, not heroic:

Measure forecast accuracy at the grain where decisions are made (SKU, customer, region, month), not at the consolidated level where misses hide.
Track bias separately from error. A forecast that is always 8% high is not an accuracy problem, it is a calibration problem, and it is fixable.
Record every forecast before the period closes and keep the history. Accuracy cannot be measured on numbers that were revised after the fact.
Judge forecasters on calibration over confidence. Someone whose 70% scenarios land 70% of the time is more valuable than someone who is always certain.
Reconcile the operational forecast with the financial one on a stated cadence, and write down which number the company is actually committing to.
Put forecast accuracy itself in the operating review with a named owner, the way uptime and quality are owned.

Companies that grow through uncertainty are usually not the ones with the best view of the future. They are the ones that know exactly how blurry their view is, and price that blur into every commitment they make.

What is the error rate on the forecast your company is betting this quarter's capacity on, and does anyone actually know?

Estoras Group works alongside leadership as a partner-owner, turning structural complexity into operational clarity and converting operational visibility into stronger profitability, resilience, and scalable growth. Our advice is aligned solely with each company's best interests.

Is a critical technology initiative moving, but not delivering?When performance stalls, adding more activity rarely fixe...
2026-11-02

Is a critical technology initiative moving, but not delivering?

When performance stalls, adding more activity rarely fixes the underlying problem. Recovery starts by reconnecting three essentials: business objectives, decision-making, and ex*****on.

PM61 enables IT and corporate stakeholders to collaborate, analyze, plan, and execute technology solutions with greater clarity. The focus is not simply on completing a project. It is on redirecting the work toward outcomes the business can see and measure.

That means challenging assumptions, establishing clear decision gates, resolving misalignment early, and translating technical ex*****on into meaningful business value.

Majority-owned by Estoras Group, PM61 brings a partner-owner perspective and senior involvement to complex technology initiatives. Our advice is aligned solely with the client’s best interests, helping organizations recover momentum without losing sight of the result.

Is your technology initiative active, but not effective? Let’s reconnect the plan to the performance the business needs.

Explore our solutions: www.estorasgroup.com/solutions
Contact us: [email protected]

2026-11-02

Most companies treat the annual budget as a planning exercise. In practice, it has become a negotiation ritual, and the numbers that survive it are often the least useful ones on the page.

The pattern is familiar: the budget cycle starts in late summer, consumes months of management attention, and produces targets shaped more by politics than by evidence. Departments sandbag their forecasts to make the year achievable. Leadership pads the targets back up to satisfy the board. Both sides know the game, so both sides play it. By the time the budget is approved, it is a peace treaty rather than a plan, and everyone quietly agrees not to test it too hard.

Warning signs your budget process has become theater:

- Targets are negotiated down (or up) before anyone discusses what the business actually requires
- Spending proposals are judged on the confidence of the presentation, not the evidence behind the case
- Resource allocation follows last year's split with a percentage adjustment, rather than the strategy
- The budget is final for the year, but the market it was built to serve moves weekly
- Managers spend Q4 gaming next year's baseline instead of closing this year's gaps
- Nobody can explain how a budget line connects to a growth initiative or a capability the company needs

The consequences are quiet but expensive. Resources stay committed to what was promised in October instead of what the business needs in June. High-potential initiatives wait for the next cycle while legacy spending renews itself. And leadership loses its most useful financial instrument: a budget honest enough to reveal where the business is actually choosing to go.

What to change, none of it heroic, all of it procedural:

1. Separate target setting from resource allocation. A target should describe ambition; the budget should describe what it costs to pursue it. Merging them corrupts both.
2. Build budgets from drivers (volume, price, capacity, headcount by activity) rather than incremental adjustments to last year's lines. Driver-based numbers are far harder to sandbag.
3. Require every material spending request to state the decision it supports and the outcome it commits to, not just the cost.
4. Cap the cycle at six weeks. Long cycles reward gaming and punish candor.
5. Replace the annual lock with a rolling outlook: a full-year budget, revisited quarterly with a stated trigger for what would change it.
6. Review the budget process itself each year: where did the numbers drift, who negotiated hardest, and what did that negotiation cost in honesty?

Companies that grow steadily through uncertainty are rarely those with the most ambitious budgets. They are the ones whose budget process produces numbers leaders can actually act on, because the negotiation was about the business, not the baseline.

What would have to change in your budget cycle before the targets in it felt like commitments rather than openings?

Estoras Group works alongside leadership as a partner-owner: turning structural complexity into operational clarity, and operational visibility into stronger profitability, resilience, and scalable growth. Advice aligned solely with each company's best interests.

Address

Vancouver, BC

Alerts

Be the first to know and let us send you an email when Estoras Group posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Estoras Group:

Shortcuts

Share