One narrative across a growing product line
One product narrative held together through a four-segment market expansion and the launch of a second platform into the same audience.
- Role
- Senior Product Marketing Manager
- Timeline
- 12 months, three narrative phases
- Company
- Enterprise R&D software platform
- Collabs
- Product marketing, product, sales leadership
- The problemA four-segment market expansion and a second platform launch ran at the same time, into the same audience, with one story expected to carry both.
- The solutionA positioning architecture with one fixed problem frame at the top, then functional separation, a convergence narrative, and account risk tiers underneath.
- The resultOne throughline across four segments and two products, and twice the collateral reviewed against it in the same time.
Challenge
The market footprint went from one segment to four. The original problem frame resonated with the first audience and landed flat with the others, so the story had to stretch without fracturing.
At the same time, a next-generation platform launched into the same audience as the flagship. It was not a replacement, but its strengths sat exactly where the flagship was visibly weakest.
Both moves ran at once. A single positioning statement could not carry that, so the narrative needed levels: what stays fixed, and what is allowed to flex.
Strategy
One shared antagonist
A unifying problem frame sat at the top — one product, one mission, one problem it solves — so segment-specific messaging read as an elaboration of the story rather than a contradiction of it.
Functional separation
The two products had distinct functionalities. That difference was written down plainly and stated before customers experienced both, instead of being discovered in a demo.
Convergence narrative
The new platform's pilot phase was framed as the research phase of a convergence plan toward one unified environment, making a two-product coexistence a deliberate strategy and not a product-management problem.
Account risk tiers
Accounts tolerate ambiguity differently. Innovation-oriented accounts got forward-looking messaging about the new environment; conservative, compliance-sensitive accounts got protective messaging with the flagship front and centre. Same portfolio, two conversations.
Impact
Double the review throughput.
Decks, talk tracks, demo scripts, and campaign assets were checked against a written frame instead of re-litigated case by case — same review time, twice the volume.
Drift became checkable.
Reviewers could name which level of the architecture a piece had departed from, rather than arguing from taste.
Messaging without a gatekeeper.
Paired with the ICP and personas directory, the team could produce tailored, on-position messaging without a positioning owner in the room for every draft.
The next-generation platform positioning shipped shortly before my role was eliminated in a company-wide reduction, so I did not see it through a full sales cycle. The convergence framing and risk-tiered messaging are presented here as design decisions, not as validated outcomes.
Personal takeaway
Narrative consistency across a product arc requires knowing where you are in the arc at all times. What made that possible was the least glamorous piece: functional separation, written down plainly, before the conversations that mattered. Once the distinction existed on paper, drift stopped being a matter of judgment and became something anyone on the team could check — which is what doubled the review throughput.
Deliverable
Anonymized and streamlined. The deliverable is the architecture — what holds at the top, how two products were positioned to one audience, and how the arc stays honest over time.
The architecture is what makes flexibility safe. Fix the problem frame, then let the segment, product, and account conversations differ on purpose.
The architecture makes flexibility safe: one level is fixed, the rest are allowed to differ on purpose.
- Level 01 — Shared problem frameFixed
One product, one mission, one problem it solves. A single antagonist every segment recognises, stated the same way everywhere.
Rule: Never re-cut for a segment or a launch - Level 02 — Segment elaborationFlexes
Four segments, four versions of the same tension: the stakes, the vocabulary, and the proof change; the problem does not.
Rule: Each version must trace back to Level 01 - Level 03 — Product lineFlexes
Two products in market at once. Each one claims a distinct function inside the shared frame rather than a better version of the other.
Rule: Functional separation, written before launch - Level 04 — Account conversationFlexes
How far forward the story runs depends on how much ambiguity the account tolerates. The message tier is chosen deliberately, not improvised.
Rule: Two approved conversations per account tier