Turning a Position Into Priorities

A finished position — a clear, evidenced, checkable sentence about where the company sits — answers what the company has decided. It doesn’t, by itself, answer what to actually do next, in what order, with what resources. That translation, from a decision to an actual sequence of priorities, is a distinct piece of work that gets skipped surprisingly often: organizations finish the strategic decision, feel a genuine sense of accomplishment at having reached it, and then default to whatever the existing operational calendar already had planned, rather than deliberately re-sequencing priorities around what the new decision actually implies.

Why a position doesn’t automatically produce priorities

A position is a static description of where the company stands; priorities are a sequence of specific actions across time. Getting from one to the other requires a separate judgment: given everything the new position implies, what has to happen first, what can wait, and what should stop entirely because it no longer serves the decided direction. Without this translation, a company can have an excellent, well-evidenced position sitting in a document while its actual operational activity — the campaigns already scheduled, the product roadmap already committed, the hiring plan already in motion — continues largely unaffected by what was just decided.

What actually has to happen to translate decision into sequence

Turning a position into priorities means auditing existing plans and commitments against the new decision specifically, not generally — does the next quarter’s planned campaign still make sense given the new position, does the current product roadmap still serve the buyer the position has decided to focus on, does existing messaging still hold or does it now contradict what was just decided. Each of these requires a specific judgment call, informed by the position, rather than an assumption that everything already planned remains fine simply because nobody explicitly canceled it.

Why some things genuinely need to stop, not just start

The uncomfortable half of this work is at least as important as the exciting half. A new position often implies that some existing activity — a campaign built around an old claim, a product initiative aimed at a buyer the anti-persona work identified as the wrong fit, a piece of messaging still circulating with pre-decision language — should actually stop, not just be supplemented with new activity layered on top. Organizations frequently do the easier half of this translation (starting new things aligned with the position) while avoiding the harder half (stopping existing things that now contradict it), which produces a confusing hybrid: new, on-position activity running alongside old, off-position activity that nobody explicitly decided to keep, simply because stopping it wasn’t as satisfying as starting something new.

Why sequencing, not just selection, matters

Even once the right set of priorities is identified, the order they happen in matters — some priorities are prerequisites for others, and getting the sequence wrong can waste the value of work done too early or too late relative to what needed to happen first. A rollout of new external messaging before internal teams have been prepared to tell the story consistently, for instance, creates exactly the inconsistency the underlying position was meant to eliminate. Sequencing well requires holding the whole set of implied priorities in view together, rather than acting on whichever one feels most urgent or most exciting in isolation.

Inceptik does not turn the position into the longest possible list of initiatives. What matters are the few changes without which the new decision would remain invisible, their sequence, and clear ownership. The narrative architecture first turns the position into repeatable claims; the completion criteria for strategy work show whether the decision is ready to produce priorities.

Continue with related topics

• Decision Rules Instead of Taste Debates
• From Position to Narrative Architecture
• Knowing When Strategy Work Is Actually Done

FAQ

Who should be responsible for translating a position into an actual priority sequence? Ideally the same people with the standing to hold the governance mandate for the brand more broadly — this translation work benefits from real authority to actually stop existing activity that no longer fits, which a purely advisory role often lacks.

How often does this translation need to be revisited? Whenever the position itself changes on a genuine structural trigger, and periodically as a check that operational activity hasn’t quietly drifted back toward pre-decision default, since organizational habit tends to reassert itself gradually even after a deliberate initial re-sequencing.

What’s the most common mistake in this step? Adding new, on-position activity without stopping old, off-position activity — producing a confusing mix that undermines the clarity the position was meant to create, because the market and the internal organization both still encounter the old version running in parallel with the new one.

---