Enterprise Research — 2025
Reading across the studies, not within them
Three populations, four instruments, six months of collection. Each group arrived with what sounded like its own set of complaints. Grouped thematically rather than counted by channel, they converged: one system failing in the same places, experienced from three different seats.
Research lead — mixed-method synthesis, thematic mapping, roadmap alignment
- pieces of feedback synthesized
- 500+pieces of feedback synthesized
- of continuous collection
- 6 monthsof continuous collection
- pain points tied to initiatives
- 5pain points tied to initiatives
The problem
Signal existed in volume across the enterprise. What did not exist was a single view of what hurt most — or a line connecting that pain to what the roadmap was actually funding.
- 01
Scattered by channel
Feedback lived in separate instruments owned by separate teams. No one held the view across all of them.
- 02
Fragmented by audience
Each population was heard in isolation, so recurring problems read as unrelated complaints.
- 03
Disconnected from planning
Pain was documented but never mapped to initiatives, leaving prioritization to argument rather than evidence.
The approach
Three populations, four instruments, one thematic map. Six months of collection and more than five hundred discrete pieces of feedback, grouped by the underlying breakdown rather than counted by the channel it arrived through.
Four instruments
- 01
Intercept surveys
In-product intercept data capturing reactions at the moment of friction, not in recall.
- 02
Qualitative interviews
Depth from both sides of the relationship, surfacing the reasoning behind the ratings.
- 03
Internal research
Surveys and interviews across every function working inside the shared system.
- 04
Prior study reuse
Existing findings retrieved through the research repository — no ground re-covered.
What I discovered
Each population arrived with what sounded like a distinct set of complaints. Mapped thematically, they converged — one system failing in the same places, described in three different vocabularies.
What each seat reported
Three vantage points
- One population felt the breakdowns as delay
- One felt them as ambiguity about what to do next
- One felt them as rework absorbed inside the process
Shared underlying breakdowns
One system, three descriptions
- Fragmentation — work split across places that do not talk to each other
- Data — what people need to trust and act on is missing, stale, or contradictory
- Escalation and ownership — no clear answer to who holds a problem once it leaves a queue
Thematic grouping across all four inputs — not channel-by-channel reporting — is what let the top five surface.
“Enterprise problems only look unrelated until someone maps them together.”
The outcome
Five pain points, each tied to an initiative, carried into quarterly planning as the basis for sequencing.
Pain connected to funding
Each of the five was tied to the initiatives that would address it, so prioritization ran on evidence rather than advocacy.
Alignment in quarterly planning
Leadership and product agreed on where to focus first — the findings went into planning rather than into a report no one opened.
A structural signal delivered
The synthesis surfaced that an orchestration approach could address several problems at once. It was raised to leadership; the organization is not ready to act on it yet.
Prior research compounded
Earlier studies were pulled forward through the repository, so six months of collection built on work already done.
The takeaway
Synthesis above the study: individual studies answer team questions. Reading across all of them is what surfaces the problems no single team can see.
Findings shaped as decisions: pain points tied to initiatives convert into planning. A ranked list of complaints does not.
Honest about readiness: the strongest structural finding was delivered, not forced. Knowing when an organization can act is part of the work.
A note on confidentiality
This account is generalized. Client and product names, internal system names, proprietary metrics, and verbatim participant data are omitted; figures are rounded and methods described at a level that conveys the reasoning without disclosing confidential material.
