Product Marketing Manager · Metroscope · ~1.5 years
Building clarity around a technical product, its category and its commercial motion
Built positioning, messaging, packaging, enablement and competitive intelligence where no established Product Marketing system existed.
01
The challenge
Start with the situation, not the deliverables.
Metroscope sells predictive-maintenance software to nuclear and gas power plants. The product is genuinely technical, buyers are demanding and the category is still forming. There was no established positioning, enablement system or competitive rhythm.
- A category still being defined
- Highly technical stakeholders
- Regulated industrial contexts
- Internal artefacts requiring anonymisation
02
Research & insights
What changed the way I framed the problem.
Insight 01The first question is the market question—not which framework to apply.
Insight 02Technical depth makes simple messaging honest rather than approximate.
Insight 03Enablement succeeds through content, training and follow-up—not asset production alone.
03
Approach & decisions
A sequence of choices, not a pile of assets.
- 01
Build a value ladder from product mechanics to operational, business and strategic meaning.
- 02
Create regular competitive briefs plus reactive analysis triggered by field signals.
- 03
Treat packaging simplicity as part of the value proposition.
- 04
Use AI only with validated inputs, peer review and access to original sources.
04
Selected outputs
What the work produced.
- Positioning and value propositions
- Demo narratives and realistic use cases
- Packaging and pricing work
- Weekly and monthly competitive intelligence
- Governed AI-assisted workflows
The narrative is public. Product screenshots and internal working artefacts remain gated until fully anonymised and approved.
05
Impact
Evidence, with context and attribution.
- A Product Marketing system built from a blank page
- Greater technical credibility for demanding sales conversations
- A repeatable rhythm connecting field signals to narrative and enablement
What I learned
A playbook is a starting hypothesis about a company’s context, not a description of it. Adapt until the method and the context match.
What I would do differently
Define publication rules and measurement instrumentation earlier, so adoption and commercial impact are easier to demonstrate externally.