The Readiness Gap: Transparency Survey to Product Digest
Knowing something is coming isn't readiness. Survey the time drain, then ship a digest that says what to do with it.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 94%
Itwaru's core distinction is between two things companies conflate: people knowing a launch is coming, and people knowing what to do with it. A roadmap status page delivers the first and creates the illusion of alignment; the second requires positioning, enablement, and customer readiness. She operationalises this with a two-sided survey that quantifies where PM time is leaking and how often revenue teams have to ask, then a recurring product digest engineered around 'here's how you get ready' rather than 'here's what's shipping', with a hard boundary against product marketing.
Origin
Born from Pendo's worst launch — the biggest since the launch of the product itself — in Christine Itwaru's fifth week at the company. The postmortem revealed the gap was not awareness (teams knew the feature was coming) but readiness. The digest and the survey were the systematic response.
Core principles
- 01Awareness is not readiness: 'it ships in Q4' is a status update, not enablement.
- 02Measure the gap before you fix it — survey both sides, PMs and revenue teams.
- 03The right success metric for internal alignment is the quality of inbound to the product team, time-bound.
- 04The digest exists to make people ready and jazzed, not informed.
- 05Product ops educates on value and usage; product marketing positions and sells. That line is non-negotiable.
How to run it
- 1
Run the two-sided transparency survey
Survey the product managers and the sales/success teams simultaneously on a 1-to-5 scale. Ask PMs: where is your time going, how much of it goes to firefighting for the revenue team, and how much quality time do you actually get with customers? Ask the revenue team: how often do you find yourself having to ask the product team questions?
Pro tip The survey's job is to tell you where to place your energy — you are looking for the biggest asymmetry between the two sides, not an absolute score.
Watch out Measuring product ops' effectiveness quantitatively is genuinely hard; use the survey to locate the problem, not to grade the function.
- 2
Pick the one flow to fix first
Diagnose which direction the transparency is missing. At Pendo the answer was product-to-revenue: information was not flowing out of the product org. Fix one direction before attempting both.
Pro tip Pendo's first target was aligning the success and sales orgs to the product team — a deliberately narrow scope.
- 3
Build the digest around 'what to do with it'
Create a recurring product digest. Explicitly do not build it around 'this is coming next quarter, go tell your customers'. Build it around how to get ready for it, how to get excited about it, what the added value is, how to use the thing, and how it changes each internal role's day-to-day.
Pro tip Tailor the 'how does this impact your role' section per persona — for example, what a new feature means specifically for a customer success rep's account-health workflow.
Watch out A status-keeping tool that lists dates will make the org feel informed while leaving it entirely unready — this is exactly the failure mode that produced Pendo's bad launch.
- 4
Hold the line against product marketing
State the handoff explicitly: product ops does not teach the revenue team to sell and does not teach them to position — that is product marketing's job. Product ops knows the product intimately enough to explain the new value, how to use it, and what it means for each role.
Pro tip Itwaru says she has never had anyone dispute this line once stated plainly — say it once, at the start.
- 5
Treat content and education as definition of done
Make enablement content and in-product education part of the product development lifecycle's definition of done, not a post-launch afterthought. Write the technical documentation, and weave education into the app itself so users can self-serve before reaching for docs.
Pro tip In-product education is what keeps users in and helps them upgrade — build the playbooks alongside product marketing.
- 6
Measure on quality of inbound, time-bound
Set a time-bound window (Pendo used a quarter) and monitor the quality of inbound questions to the product team. Success looks like a shift from 'teach me how to do this thing' to thematic questions like 'tell us what you do because our customers would benefit from this'.
Pro tip The qualitative shift in the type of question is the signal — you rarely need a number.
In the wild
The product area had been under development for roughly eight months and was the biggest launch in company history since the original product. Itwaru, five weeks in as the first director-level product hire, deliberately did not intervene — new layer, product people crave autonomy and trust. The launch went badly. The postmortem showed teams knew it was coming; they did not know the extent of it, how to position it, how to talk about it, or how to prepare customers and prospects.
→ The team sat down openly across functions to name what everyone could have done better, and Itwaru began formalising product ops out of the director-of-product role — with readiness, not awareness, as the design goal.
After the two-sided survey showed a transparency gap, Pendo's product ops team shipped a recurring product digest deliberately not built as a release calendar. Instead of 'this ships next quarter, go tell your customers', it covered how to get ready, how to get excited, what the value is, and how it changes each internal role — while explicitly leaving positioning and selling to product marketing.
→ The digest matured over several years and became the standing mechanism for product-to-revenue readiness; inbound to the product team shifted from how-to questions to thematic, customer-value questions.
Common mistakes
Confusing a roadmap status page with enablement
Telling people a feature ships in Q4 and updating the date as it nears satisfies the 'they knew it was coming' test while leaving the org unable to position it, talk about it, or prepare customers. This is the precise gap that broke Pendo's biggest launch.
Fixing the gap without measuring it
Without the two-sided survey you guess at which direction transparency is missing and how badly. The survey's asymmetries — PM firefighting hours vs revenue-team question frequency — tell you where to place limited energy.
Drifting into product marketing's lane
If product ops starts teaching the revenue team to sell and position, it duplicates PMM, creates conflicting guidance, and loses the internal-education mandate that made it credible.
Treating enablement content as post-launch cleanup
If documentation and in-product education are not part of definition of done, they arrive after the customers do — which is how a technically successful launch still lands badly.
Is it for you?
Best for
A product ops or product leader at a B2B company that just had a launch land badly internally, where sales and success knew what was coming but had no idea what to do with it.
Not ideal for
Companies with no revenue-team dependency on product knowledge — pure self-serve, no-touch products where there is no internal audience to make ready.
From the transcript
“there's the knowing something's coming and then there's the knowing what to do with and you can use just some sort of status keeping thing…”
“we sent out this survey across both product managers and the sales and success teams and we said you know where's your time going PMS…”
“I go back to this whole people can know when they're coming but they need to know what it is they need to do with…”
“the handoff is that we don't teach them to sell we don't teach them to position”
“product marketing positions and helps the revenue team sell their lead gen you know for all of the outbound and the campaigns that they're running”
“we monitored success just within I think it was a quarter was the time-bound space that we had it in on quality of inbound to…”
From the episode
Understanding the role of product ops
Christine Itwaru (Pendo)