Every team, its own story. One moving product.
How a company in the middle of a pivot replaced a different story in every team with one framework that held across three service lines.
Problem, solution, result in thirty seconds.
A company changing faster than its story.
The company combines software with professional services. It was in the middle of a pivot: adding new services, bringing on new partners, and moving towards a different ideal customer.
Every one of those changes was sensible on its own. Together, they left each team with its own picture of what the company now was.
The brief was new positioning. The problem was alignment.
The ask was to update the positioning after the pivot.
But a new positioning statement alone wouldn't have fixed it. Each team was working from its own assumptions about who the customer now was and what the company offered, so Product, Sales and content were each telling a different story. The risk wasn't weak copy. It was a pivot customers couldn't follow and teams couldn't sell.
Every commercial problem sits somewhere on this chain, from choosing the market on the left to what Sales says on the right. Decisions on the left shape everything to their right.
The positioning needed rebuilding, but the bigger job was agreeing who the customer now was, and making sure every team told the same story to them.
Four decisions, in order.
I built the positioning to survive change, not to describe one moment in the pivot.
Start from core truths.
I rebuilt the positioning from the things that wouldn't change with the next product shift: the product's promise, the market insight behind it, and proven customer wins.
One shared framework.
I created one messaging framework for Product, content and Sales to share, so every team started from the same story.
Show every team how.
I wrote real examples showing each team how to adapt the message to different use cases, without drifting from the core.
Build it into daily work.
I embedded the narrative into onboarding, sales decks and roadmap reviews, so it stayed in use after the project ended.
One story. Three service lines.
What changed once every team worked from the same framework.
The same core story adapted to each service line.
GTM execution got faster once teams stopped reconciling versions.
Product shifts landed without losing buyer trust.
Alignment is not everyone agreeing with the slide.
A new positioning statement would have been out of date by the next product shift. What lasted was a framework built on things that don't change, and built into the work teams already do.