Problems › The Team Is Not Executing the Plan › Manufacturing
When a plan to lift contribution per machine hour is not executed, the plant is rationally maximising utilisation on the customer that drives the margin problem. The version of this question that applies to manufacturers is not the generic one. The $45M automation case depends on the very customer that causes the margin problem — so an answer that ignores contribution per machine hour will be confidently wrong. The analysis has to start from capacity utilisation and customer concentration rather than from revenue.
When a plan to lift contribution per machine hour is not executed, the plant is rationally maximising utilisation on the customer that drives the margin problem. The version of this question that applies to manufacturers is not the generic one. The $45M automation case depends on the very customer that causes the margin problem — so an answer that ignores contribution per machine hour will be confidently wrong. The analysis has to start from capacity utilisation and customer concentration rather than from revenue.
Execution failure is rarely unwillingness. It is normally that the plan requires changeovers or scrap reduction the structure, the incentives around capacity utilisation or the need to protect volume from the concentrated customer actively discourage, and operators resolve that conflict the way the measured hours pay them to.
The diagnostic question is not why the takt is missed but what the plant director is asked to give up in contribution per machine hour when capacity is shifted to the automation case, and who compensates for the lost utilisation on the existing customer.
The second common cause is arithmetic: the plan requires more machine hours than exist once changeovers and scrap are accounted for, and rather than saying so the three plants quietly run the subset they can and the automation case never reaches the required volume.
These three together are the signature. One on its own usually points somewhere else.
✓ Weekly contribution per machine hour reports remain flat while changeover counts and scrap rates are logged as improved.
✓ Capacity utilisation is reported at target but the automation case volume does not appear in the monthly run.
✓ Operators are measured on takt and utilisation that the required sequence of runs directly reduces.
The move that usually makes it worse. Communicating the automation case more often, which addresses a comprehension problem that does not exist and delays changing the contribution per machine hour target that does.
It is for you if you run or finance a manufacturer and the plan is understood and agreed and still nothing changes. It is the situation where the numbers are available but nobody has put them in an order that produces a decision.
It is not for you if Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Below is an excerpt from a real run of this analysis on a manufacturer. It is a sample profile rather than a customer, and it is unedited engine output — this is the format you get, on your own numbers.
The subject is Kessler Industrial Components, a sample company profile used for testing rather than a customer — $310M revenue, three plants.
Excerpt from a real Percision run · Cost Reduction & Efficiency · sample company profile
The move. Zero-capex JV turns existing tooling into recurring aftermarket cash flow that de-risks the entire diversification sequence.
The leak it closes. Eliminates 25–30% dealer take-rate currently captured entirely by OEM captive aftermarket
The assumption it rests on. Partner dealer network maintains exclusive shelf space for 5 years — the engine put the probability at 0.75.
| Investment required | $0 capex; $1.3M one-time operating expense for engineering time and legal fees |
| Expected return | Infinite (zero capex) on $12M Year-3 EBITDA |
| Revenue, year 1 | $4.8M aftermarket revenue (8% penetration) |
| Revenue, year 2 | $9.6M (14% penetration) |
| Revenue, year 3 | $14.4M (22% penetration) |
| Exit criteria | Terminate JV if aftermarket revenue run-rate remains below $2.4M annualized by Month 12 or if OEM contractual IP challenges block >30% of target SKUs |
This is one move out of a full analysis. Read a complete report — every page, no email required.
This question routes to Organizational Alignment Model, one of 29 engagements the platform runs. For manufacturers it works through contribution per machine hour, capacity utilisation, customer concentration and scrap, then produces the sequence rather than a list of options — which move first, what it funds, and the observation that would say the sequence is wrong.
You watch the analysis get built before paying anything. Read a complete report here if you would rather see the depth first.
Change what people are measured on before asking them to behave differently. Buy-in follows the incentive far more reliably than it follows the explanation.
Occasionally. Far more often it is a structure problem that looks like a people problem, which is worth testing first because replacing people does not fix a structure and is expensive to discover.
Usually yes, but for capacity reasons rather than comprehension. A plan with three priorities that fit the capacity available beats one with twelve that do not.
Materially, yes. The $45M automation case depends on the very customer that causes the margin problem — which changes both the diagnosis and the order of the fixes. The metrics that decide it here are contribution per machine hour, capacity utilisation, customer concentration, and an answer built on industry-general benchmarks will usually point at the wrong one first.
Less than most people expect. Your last twelve months of revenue and cost split the way you already split it, plus whatever you hold on contribution per machine hour and capacity utilisation. The analysis is explicit about what it is assuming where your data stops, which is more useful than waiting for numbers you may never have.
Percision is the wrong tool if you already know the answer and only need execution capacity, or if the business is pre-revenue — then the constraint is evidence about the market, not analysis of your own figures. Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library. Also wrong if you need facilitation, politics, or someone to sit with a lender or buyer. Those are human jobs.
Percision is not a lawyer, tax advisor, auditor, licensed appraiser, clinical or regulatory filer, or an AI implementation shop. It does not do HR casework, creative-only brand work, or impersonate a named consulting firm. It is a strategy analysis engine — not a template library.
Describe the situation in your own words and we will tell you which analysis answers it — before you sign up for anything.
Describe my situation →Prefer to skip ahead? Go straight to the free diagnostic.
English · Español · Deutsch · Português · Français · Italiano · Nederlands · 日本語 · 한국어 · 中文 · Polski · Svenska · Türkçe · العربية · Tiếng Việt · ไทย · हिन्दी · עברית