Research in an org that didn't ask for it
[Sample] How a research practice earns its place before anyone has asked for one.
Sample text, here to show how an essay is laid out. Replace it with the real piece.
Most organisations do not wake up wanting research. They want fewer surprises after launch, fewer arguments settled by seniority, and some confidence that the next quarter is being spent on the right thing. Research is one way to get those, but nobody puts it on a roadmap by name.
Start with a decision, not a study
The first project decides how the practice is seen for a long time. A broad discovery study produces a long document and a polite meeting. A study attached to a decision that is already scheduled produces a changed decision, and a team that remembers why it changed.
So the opening question is not what would be interesting to learn. It is which decision in the next six weeks is being made with the least evidence, and who owns it.
Make the work visible while it happens
Findings delivered at the end arrive too late to be trusted. People trust what they watched take shape.
- Invite the product manager and one engineer to every third session.
- Share raw notes the same day, before any synthesis.
- Write the one-page summary first and the full report only if someone asks.
A practice is established the day a team asks for research before being offered it.
What changes after a year
The requests change shape. Early on they are validation requests: confirm what we already built. Later they become framing requests: help us decide what to build. That shift, more than headcount or tooling, is the sign that the practice has taken root.
What it does not change
Research does not remove the need for judgement. It narrows the range of defensible opinions, which is a smaller and more useful thing.