Outcomes, not outputs
If you can build it, it’s an output. If you can achieve it, it’s an outcome. Every initiative gets framed as “ensure a result for a stakeholder”—because features ship, but only results compound.
THE OPERATING SYSTEM
How the work actually gets done
Good strategy is a system,
not a slide.
Every business I have grown ran on the same machinery underneath: a few non-negotiable principles, one piece of honest math, a gated pipeline that spends money only after questions get answered, and a calendar that makes all of it inevitable. The products change. The machinery does not.
GOVERNING PRINCIPLES
Non-negotiables that protect the model
Five rules that outrank
everyone’s opinion.
No feature wars
Chasing a competitor’s spec sheet is how categories commoditize and margins die. Priorities come from customer pain and strategic objectives—never from tit-for-tat comparison.
Relentlessly seeking why
Why this product? Why this feature? What pain does it kill? Asked constantly, in every review, until low-value work has nowhere left to hide.
ROI ≠ easy
Scoring supports prioritization; it does not replace judgment. Nothing gets built just because it’s convenient. It has to solve a real pain, tie to a theme, and move a stakeholder.
Nothing is permanent
Every priority lives on a Now / Later / Future horizon and gets revalidated on a schedule. Confidence has a line: above it you’re committed, below it you’re aspirational—and honest about which is which.
Where they came from
Written the hard way—from launches that worked, launches that didn’t, and the difference between them. They govern every framework on this page.
Argue with one of themTHE PRIORITIZATION MATH
One formula, honestly applied
Priority = (Value ÷ Effort)
× Confidence.
Most teams score value and effort, then quietly ignore the odds. The confidence multiplier is the honesty tax: it makes optimism pay rent. A thrilling idea at 50% confidence loses to a solid one at 95%—and it should.
Every candidate lands in one of four boxes. The boxes end debates that used to take meetings.
Do firstHigh value · low effort
Strategic betsHigh value · high effort
Fill-insLow value · low effort
AvoidLow value · high effort
Score a project of yours
0.75Strategic bet
The real matrix scores live projects against themes, pains, and portfolio verticals. This is the arithmetic; the judgment is the product.
THE TEN GATES
Questions before money, every time
A launch pipeline where nothing
moves until it has answered.
Every gate has the same anatomyObjective→Questions to answer→Tasks to execute→Named executive sign-offs
Prove the opportunity before anyone spends a day on it.
“Do we understand the customer pain points—and can we address them profitably?”
Exit sign-off: CEO/Finance · Bus Dev · SalesLet R&D veto fantasy before it becomes budget.
“Academically, does technical see any red flags that would halt development?”
Exit sign-off: Technical · OperationsProve it on the bench before promising it to anyone.
“Do the bench trials show real promise of hitting the product goals?”
Exit sign-off: Technical · Product · FinanceConfirm it scales before scheduling machine time.
“Does the bench design align with what production can actually run?”
Exit sign-off: Operations · Technical · FinanceFirst real runs, first real customer feedback.
“Are we comfortable with how the product is scaling?”
Exit sign-off: Product · Operations · FinanceProve you can make it twice. Then a third time.
“Can we repeatedly and consistently produce it—at the finalized cost?”
Exit sign-off: Operations · Technical · FinanceThe story, the training, the collateral—before day one.
“Do we have a compelling product story built on features the customer feels?”
Exit sign-off: Marketing · Sales · Bus DevLogistics verified, labels physically checked, inventory staged.
“Have we verified initial inventory is ready to move?”
Exit sign-off: Operations · CEO · Bus DevCoordinated release—channels trained, feedback loop live.
“Are sales teams ready for the day-one sales process?”
Exit sign-off: CEO · Bus Dev · Marketing · SalesThe mid-mortem: what did the market actually say?
“Have we completed the six-month review—and made corrections?”
Exit sign-off: CEO/Finance · SalesTHE FULL LIFECYCLE
Birth to end-of-life, nothing orphaned
Most companies manage launches.
The system manages lives.
Birth
Idea → launchTen gates, pre-mortem first. Kill it on paper before it kills a quarter.
Growth
0–18 monthsMid-mortems at 6 and 12 months. The market gets a formal vote, twice.
Maturity
Annual reviewsKPIs against targets. Margin defended, not assumed.
Decline
Detection → decisionA revitalise-or-retire gate—so decline is a decision, not a drift.
End of life
Off-ramp & successorLast-order dates, inventory burn-down, successor linkage, post-mortem.
The knowledge loop: every post-mortem feeds the next business case. What the last product learned, the next product inherits—including the successor plan, the pricing gaps, and the mistakes nobody wants to repeat twice.
LAUNCH CHOREOGRAPHY
Parallel workstreams, one release
Day one is a performance.
The rehearsal is the plan.
Product & manufacturing
Trials finalize while customer beta tests run in parallel—each feeding the other, neither waiting.
Sales & enablement
Training, documentation, and pricing land before launch day, not after the first confused customer call.
Market & channel
Collateral, digital assets, and press staged to a timeline that respects a simple truth: public information travels faster than freight.
The divergence pointGlobal launches split by region deliberately—inventory, inquiry handling, and publicity sequenced so no customer sees a product they cannot yet buy.
THE OPERATING RHYTHM
Strategy with a calendar
A strategy without a cadence
is a wish.
Frameworks fail quietly when no meeting forces them to speak. The rhythm is what keeps the machinery honest—each cycle at the altitude it deserves.
Product stand-up
Blockers surfaced while they are still cheap.
Product review
Progress against gates, honestly scored.
Portfolio review
Leadership re-ranks the whole board—nothing is permanent.
Strategy reset
Vision, objectives, and themes revalidated top to bottom.
Exit reviews
Named sign-offs. Decisions with authors, not committees.
THE COMMERCIAL LAYER
Because a launch is not a sale
Empathy first.
Spec sheet second.
Name the pain
In the customer’s words, not the brochure’s. The static. The failed prints. The support line that never answers. If they don’t recognize themselves in the first sentence, the rest is noise.
Prove they’re not alone
The pain is shared, named, and understood—which means it is solvable. This is the moment a vendor becomes a partner.
Show the relief, with receipts
Only now do capabilities enter: each one mapped to a pain already named, each claim carrying its evidence. Differentiation that answers something beats specification that answers nothing.
Every organization I lead gets a powerstatement built on this structure—one page that every salesperson can stand on. It is the stage-gate principle applied to selling: no claim advances until the pain it solves has been named.
You’ve seen the shape.
The playbook is a conversation.
The frameworks on this page are running in a real business today. If you want them running in yours—adapted, not copied—that starts with 30 minutes and a straight answer.