Where to start
What kind of work is actually in front of you?
You do not need to choose a storylineOS package first. Start with the question, how far the consequence travels and whether the underlying commercial view is still changing.

Recognition before route
The visible request is not always the real unit of work.
BOUNDED ENTRY
“This page or document needs to work better.”
The issue may genuinely be local. Start there without inventing a larger transformation programme.
PERSISTENT WORK
“Every asset request turns into the same unresolved strategy or value discussion.”
The artifact may be downstream of a continuing commercial question that needs to stay connected over time.
DOWNSTREAM ACTIVATION
“We know what we believe. We now need Sales, Marketing or other teams to use it well.”
The work may be primarily about transmission and activation rather than forming the commercial view again.
STILL UNRESOLVED
“We are not sure which of those is true yet.”
That is enough to start. The first useful move may simply be to distinguish the competing explanations.
Likely first move
Answer the first three questions.
The fourth question is optional. It only changes how continuing work might be operated, not the product depth itself.
The route is allowed to stay open until the evidence is clear enough.
Signal, Core and Amplify describe different depths of work. Managed is a separate choice about who operates continuing work.
​
You do not need to understand the product architecture before you bring us the problem.
