EXECUTIVE FIELD GUIDE · COO / CFO
When should recurring work become a system—or a product?
Pattern-to-Product is the SerialLabs method for deciding whether recurring operational friction should become a bounded system, a reusable capability, an owned product or, under stricter conditions, a new venture.
01 · THE EXECUTIVE DECISION
Four questions before the next commitment.
The method starts with one material process. It does not assume that repetition proves a market, that a prototype proves value or that technical reuse proves product economics.
Is the friction structurally recurring?
Look for the same trigger, evidence, decision, authorised action and outcome—not merely a common label.
COO signalRecurring exceptions, delayed decisions, manual coordination or local workarounds.Can a bounded intervention change the result?
Agree the baseline, minimum useful movement, observation period, authority and stop rule before outcomes are seen.
CFO signalA decision rule that distinguishes evidence from enthusiasm.What can legitimately travel?
Separate a stable core from local data, integrations, policy, language, roles and change requirements.
Product signalA second qualified context served without uncontrolled redesign.Should we own a product?
Require independent demand, safe rights, repeatable support, credible distribution and coherent economics.
Capital signalProduct ownership beats the best credible non-product alternative.02 · WORKED ANATOMY
The pattern is not the dashboard.
Order Exception Control shows why the unit of analysis is a relationship among eight elements. The example is illustrative, not a client performance claim.
<C, T, A, I, D, X, O, G>| C Context | A distributor or manufacturer managing customer orders across inventory, warehouse and carrier systems |
|---|---|
| T Trigger | A sequence of stock, fulfilment, cut-off, shipment or carrier signals raises the risk of a missed commitment |
| A Actors | Supply-chain operations, warehouse, customer service, account owner and the systems that hold the evidence |
| I Information | Order lines, stock, promised dates, warehouse events, carrier status, customer importance and prior interventions |
| D Decision | Which order needs intervention now, why, and who is accountable? |
| X Action | Assign ownership, expedite, replan, escalate or communicate with the customer within defined authority |
| O Outcome | Earlier ownership and resolution, fewer avoidable misses, and a recorded explanation of what changed |
| G Guardrails | Commercial thresholds, role permissions, escalation rules, evidence lineage and human approval for consequential actions |
The product candidate is not “an exception dashboard”. It is a repeatable way to detect, decide, act and learn inside an accountable boundary.
03 · EVIDENCE BEFORE COMMITMENT
Seven states. Six transitions. A stronger claim at every step.
The sequence is not a waterfall. Evidence may send the work backwards, reduce the core, retain a useful internal capability or stop the product claim entirely.
- 01Observed frictionIs the condition material?
- 02Pattern candidateDoes the structure recur?
- 03Working systemCan a bounded intervention operate?
- 04Measured proofDid an agreed outcome move?
- 05Reusable coreWhat survives contextual change?
- 06Owned productDo demand, rights and economics justify ownership?
- 07Platform or venture optionDoes a larger coordination or company logic exist?
THE CLAIM HIERARCHY
A demonstration proves existence. Nothing more.
- 07Economic
Can value be delivered and captured repeatedly?
- 06Demand
Does another buyer choose the outcome under real constraints?
- 05Transfer
Does the result or core replicate in another context?
- 04Attribution
Can the change credibly be related to the intervention?
- 03Outcome
Did a predeclared measure cross its threshold?
- 02Operational
Does it work inside the intended environment?
- 01Existence
Can it be built?
04 · CAPITAL ALLOCATION
The seven productisation gates.
All seven gates must be supported for Productise. Gate 6 is hard: unsafe rights or governance block the decision rather than lowering a score.
Recurrent problem
Does the same material structure recur?
Independent cases, stable decision/outcome anatomy and understood counterexamples.
Demonstrated value
Has a working intervention produced a meaningful outcome?
Baseline, observation period, threshold, outcome and claim boundary.
Stable reusable core
Can a common core serve a second qualified context?
Transfer evidence, bounded adaptation, explicit interfaces and versioned evaluation.
Repeated demand
Do independent buyers choose the same outcome?
Paid commitment, procurement movement, renewal, repeated use or credible willingness to pay.
Supportable operating model
Can we implement and support it repeatedly without exceptional founder intervention on every sale?
Repeatable deployment, service levels, observability, incident response, change control and bounded support burden.
Safe ownership and governance
Do we have the rights and controls to own and operate it?
Provenance, contractual rights, data boundary, risk controls, human authority and exit arrangements.
Credible distribution and economics
Can it reach, convert and retain customers at a coherent cost?
Route to market, support model, product investment, horizon and credible cost ranges.
Core reuse ratio measures the share of qualified functionality delivered by the core. Adaptation ratio measures the share of delivery effort consumed at the edge. High functional reuse can still hide uneconomic adaptation.
05 · THE GATE REVIEW
Four defensible decisions—not one approval path.
Incubation is not a partial pass. It requires a named gap, a test, an owner, a budget and an expiry date.
Do not increase commitment; preserve the learning record.
Approve ownership against a defined investment and review horizon.
Run the predeclared test before the expiry date.
Keep the legitimate capability without a market-facing claim.
06 · A BOUNDED FIRST COMMITMENT
AI Opportunity Sprint
The Sprint is a 2–3 week diagnostic around one recurring process and one bounded decision. It is designed to produce a better-evidenced next decision, not to pre-sell a product build.
- Owner and access
- A named operating or financial owner, people closest to the work and agreed representative examples or available data.
- Deliverables
- Current-state diagnosis, Pattern Candidate Record, initial pattern anatomy, evidence and rights gaps, and a scoped recommendation.
- Decision
- Stop, investigate a named gap, reuse a capability, or scope a separate paid Proof of Value.
- Fixed fee agreed in advance
- The signed scope defines the fixed professional fee, included work, exclusions, expenses, taxes, payment terms and the boundary to any later Proof of Value.
07 · BEFORE APPROVAL
Use the lens that matches the decision.
Operating, financial and product leaders ask different questions. The method forces the answers into the same evidence record.
Operating reality
- Where does the same exception consume judgement and coordination?
- Who owns the decision and who may authorise action?
- Which variations are legitimate edges rather than defects?
- What must never be automated or broadened without review?
Investment discipline
- What is the current cost of delay, rework, failure and manual control?
- Which baseline and threshold would make the decision credible?
- What investment and horizon are being approved—and against which alternative?
- Which support, assurance, integration and change costs survive the prototype?
Transfer and demand
- Use deployments to discover constraints without letting one client define the core.
- Test independent demand separately from delivery success.
- Prefer market-first when demand can be tested earlier at materially lower cost and risk.
- Version every product claim with its evidence and limitations.