How to get stakeholder buy-in for continuous discovery

Continuous discovery rarely fails because the research was bad. It fails because it was expensive, the results took a while, and nobody senior was invested enough to protect it when priorities shifted.

For my MSc thesis I asked eight senior practitioners how they win support for this work and keep it. Their answers had less to do with proving research value in the abstract, and more to do with organisational politics done well.

Senior buy-in is a precondition, not a goal

The bluntest quote in my interviews was about exactly this. One participant said it is impossible to achieve this in a company that does not have senior stakeholder buy-in.

That is worth taking literally. If you do not have it, getting it is the first task, ahead of designing your process or picking a tool. A perfectly designed discovery practice with no senior sponsor is a hobby that will be cancelled in the next reprioritisation.

Find a champion

The most repeated tactic was to find an advocate in management who will speak for the work when you are not in the room. As one participant put it, identify your champions and they can spread the word within the company.

A champion does things you cannot do yourself. They defend the time in planning meetings, they explain the value in language other leaders trust, and they absorb the first round of scepticism so it never reaches your team.

Build that relationship deliberately, before you need it.

Run the experiment that convinces sceptics

This was the single most practical strategy in the research, and it works because it sidesteps the argument entirely.

Rather than trying to win a debate about methodology, run one small experiment. Let the team try it on something real and low stakes. Then hold a retrospective and let them compare it against how they normally work.

One participant described the effect: people compare the two, and most conclude that since the small experiment went so well, they are more open to trying it more widely on bigger projects.

The mechanism matters. Nobody is being told they were wrong. They are being shown a comparison and drawing their own conclusion, which is a far more durable kind of agreement. It also means accepting that some experiments will fail, and treating that as information rather than as an argument you lost.

Connect it to metrics leadership already watches

Abstract arguments about user-centricity do not survive contact with a budget review. Concrete connections do.

The strongest framing from my interviews was the north star metric: a top-level measure that, when it moves, moves revenue, market share and the other numbers leadership cares about. Underneath it sit input metrics your team can affect directly. Discovery then has an obvious place in the chain rather than sitting outside it.

I go into the full set of measures in how to measure the impact of continuous discovery, but the principle is simple. Do not ask people to value research on your terms. Show it moving something they already value.

Set expectations before anyone asks

A recurring theme: be honest and specific up front about what you expect and how long it will take.

One participant described letting teams implement this and giving it time for results to unfold, but setting out the results you want to achieve at the start, and being realistic about them. Unrealistic promises are what turn a slow start into a cancellation, because it looks like failure rather than the expected pace.

Two things to state early:

What outcome you are aiming at, defined before you begin.
Roughly when it is reasonable to judge it, so nobody assesses a six-month habit at week three.

Show progress continuously, not at the end

Discovery is continuous, so the reporting should be too. Practitioners kept stakeholders informed of progress and interim results rather than saving everything for a big reveal.

This does two jobs. It maintains buy-in through the quiet stretches, and it demonstrates the value of the work in real time, which is what builds the organisational belief that keeps it funded. Waiting for one impressive final report means months where, from the outside, nothing appears to be happening.

Expect the money conversation

Be prepared for the cost question, because it will come. One participant named it directly: the biggest challenge is what to do with the insights, and making the time and the money, because it is expensive to do this continuously. You have to justify it to stakeholders, budget holders and product managers.

Under financial pressure, companies deprioritise anything that feels exploratory, because they are driven by short-term performance metrics. Your defence is the chain you built earlier: this work feeds this metric, which feeds this business result, and here is the interim evidence.

Negotiate the delivery trade-off diplomatically

There is a permanent tension between shipping features and spending time on discovery, and stakeholders often prioritise the feature set. Participants were clear that this needs diplomatic communication and explicit agreements, not a fight.

The framing that works is not discovery versus delivery. It is that discovery is how you avoid spending delivery capacity on the wrong thing. Everyone agrees that building something nobody wants is the most expensive outcome available.

When leadership does not believe in it

One more honest note. Some participants worked with leaders who did not believe in setting objectives and hypotheses at all, which undermined the whole approach.

If that is your situation, the small-experiment route is more important than any presentation. You will not argue someone into a new belief about research. You may be able to show them a result they cannot explain any other way.