More opportunities than delivery capacity.
Consider a fictional operator with three established stores across two markets. Acquisition is active, but each store reports differently. The same lean team is considering a new market, more creative testing, a site rebuild and an AI reporting tool.
The constraint is capacity: an operations lead can coordinate the work, the marketing team can maintain one shared testing backlog, and a developer has six days available during the next four weeks. The decision is which initiatives should start, wait or be rejected.
First, make the current operation comparable.
| Observed in the scenario | Interpretation to test | Immediate implication |
|---|---|---|
| Store reports use different sales periods and refund treatment | Cross-store comparisons may be misleading | Align definitions before reallocating significant spend |
| Creative ideas arrive through several message threads | Production may be constrained by handoffs rather than idea volume | Introduce one brief, approval point and shared backlog |
| A recurring report requires spreadsheet consolidation | A bounded reporting pilot may be useful after the inputs are agreed | Validate the manual version before automating it |
| A new market and a rebuild both need developer time | The available capacity cannot support all initiatives at once | Defer broad changes until their business cases are evidenced |
The working diagnosis is an information and coordination constraint. It remains a hypothesis: if the initial review instead finds a broken checkout or materially incorrect tracking, that issue moves ahead of the roadmap below.
The first deliverable is a short written memo showing which observations are established, which assumptions remain open and which decision each missing input could change. That prevents a roadmap from acquiring false certainty.
Sequence the dependencies. Limit the parallel work.
| Initiative | Decision | Reason / dependency | Developer allocation |
|---|---|---|---|
| Common revenue, cost and reporting definitions | Start first | Required for comparable commercial decisions | 0 days |
| Targeted tracking and data-source checks | Start with diagnosis | Resolve material data gaps before interpreting performance | 2 days |
| Shared creative testing backlog | Start in parallel | Removes an operational handoff without a software project | 0 days |
| Weekly reporting automation pilot | Start after definitions pass review | Build only against an approved manual reference report | 4 days |
| New-market launch | Defer | Requires a comparable baseline and a separate operating case | 0 days |
| Full storefront rebuild | Defer pending diagnosis | No evidence yet that a rebuild addresses the main constraint | 0 days |
The six development days are fully allocated. Additional work requires a trade-off. An apparently attractive project should not enter the plan without displacing something or adding accountable capacity.
Priority is expressed through the decision, the evidence and the dependency. A numerical score can help compare a larger backlog, but it cannot turn uncertain impact estimates into measured facts.
Four weeks. Explicit outputs.
One agreed reference.
Align reporting definitions and reproduce one week manually for all three stores. Identify material tracking discrepancies. Deliver a data dictionary, reconciliation notes and the diagnostic memo.
Owner: operations + finance. Developer: 2 days reserved for targeted checks.One testing queue.
Use a common creative brief and an explicit approval step. Review proposed tests against production capacity. Approve the reporting pilot only when the manual reference is accepted.
Owner: marketing + operations. Developer: 1 day for the approved pilot.One controlled workflow.
Connect the approved inputs, implement the checks and compare the output with the reference report. Record failures and rerun them after correction.
Owner: operations + development. Developer: 2 days.Evidence for the next cycle.
Document operation and recovery. Have the client team rerun the workflow. Review the creative backlog and revisit the deferred initiatives using the now-comparable baseline.
Owner: operations + commercial lead. Developer: 1 day.The sequence is conditional. If data reconciliation is not accepted in week one, the automation start moves. The calendar illustrates a capacity-constrained plan; it is not a delivery promise.
A deliverable needs a usable finish line.
| Deliverable | Acceptance evidence | Accountable function |
|---|---|---|
| Common reporting baseline | A reviewer can trace each metric to a source, definition and period; unresolved differences are listed | Finance / operations |
| Creative testing backlog | Each approved test has an hypothesis, asset owner, budget envelope and review point | Marketing |
| Reporting pilot | A clean period reconciles; failure fixtures stop; the team can rerun the process | Operations |
| Decision register | Deferred initiatives have a reason and a specific condition for reconsideration | Commercial lead |
Ongoing consulting would review this evidence with the team, update assumptions and resolve decisions that block execution. Campaign management or software delivery would have a separate scope. The client can retain its existing partners throughout.
Take the example apart.
Download the diagnostic memo, priority register, capacity allocation and acceptance criteria. These files contain only illustrative material.
Version 1.0 · Prepared 29 October 2026 · Reuse the method with your own reviewed definitions. Examples are provided for evaluation, without a guarantee of commercial results.