The product
A fictional operations platform connects the eight systems a regional field-service company already runs, monitors exceptions around the clock, and resolves routine failures before a person intervenes.
- Coverage
- Eight required operating systems
- Operation
- Around-the-clock exception monitoring
- Action
- Routine failures resolved before staff intervention
Room 1 of 3
- Technical shortlist · done
- Operating review · done
- Budget approval · done
Technical shortlist
The technical lead is deciding whether the product belongs on the shortlist at all. One unsupported system creates a custom bridge her team does not have time to own.
The hierarchy for the technical shortlist
That is the right lead in this room.
That claim is true. It is doing the wrong job in this room.
At qualification, breadth is not a vanity claim. It is the gate. The labor and budget consequence only matter after the buyer believes the product can cover the real environment.
West of Obvious · original public model
Operating review
The operations director believes it can connect. Now she is deciding whether changing the team's workflow is worth the disruption. Her staff already rotate through after-hours exceptions.
The hierarchy for the operating review
That is the right lead in this room.
That claim is true. It is doing the wrong job in this room.
Coverage has become the mechanism. The problem she feels is not eight systems; it is the labor required to babysit the seams.
West of Obvious · original public model
Budget approval
The CFO is choosing between the platform and another operations hire. She needs the economic decision, not a tour of the architecture.
The hierarchy for budget approval
That is the right lead in this room.
That claim is true. It is doing the wrong job in this room.
The buyer has moved from feasibility to tradeoff. Lead with the capacity decision, then show the operating burden and product facts underneath.
West of Obvious · original public model
The facts stayed still. The hierarchy moved.
Broad coverage can qualify the product. Labor can make the consequence felt. Capacity can close the business case. None is always the headline.
The roadmap gives product marketing facts. The buying room decides their order.
| Room | Decision being made | Lead | Why |
|---|---|---|---|
| Technical shortlist | Can this work here? | Capability breadth | Coverage is a hard gate |
| Operating review | Is the workflow change worth it? | Labor removed | The operating burden is what the team feels |
| Budget approval | What are we buying instead of? | Capacity before headcount | The tradeoff is the decision |
West of Obvious · original public model
Design notes
The idea. Product teams ship capability. Buyers encounter that capability through a decision. Positioning is the act of putting the right truth at the top without throwing the other truths away.
Breadth is not the villain. Breadth leads when it is a purchase gate. Later, the same breadth usually moves underneath the operating or budget claim as proof.
The model. The scenarios are fictional and intentionally small. The answer has to come from the company's own proof. A formula cannot supply it.
How it is built. One HTML file, vanilla JavaScript, no framework, no libraries, no build step. Native radio groups, visible progress, a screen-reader status line, reduced motion, and a no-JavaScript fallback.
Original public model · West of Obvious