Skip to content
Robin Schreiner

UX Management · Product Leadership

← All notes

Think End to End · 3 min read

Stop collecting UX artefacts. Start connecting the evidence.

Personas, journeys, interviews, and analytics become useful when they help a team make the same decision.

This is part one of Think End to End, a series about connecting what we know about people to what we do next.

I have seen teams with a persona deck, a journey map, interview notes, a feedback board, and an analytics dashboard. Each looks reasonable on its own. Yet when someone asks which problem to solve next, the answer is still a matter of opinion.

We have collected the pieces. We have not connected them.

Start with the job someone is trying to do

Imagine a service where people submit an application. A journey might begin well before someone opens the form: they need to work out whether the service is for them, find the required documents, and decide whether they trust the process enough to share personal information. It does not end when they click Submit. They may need confirmation, a decision, or a way to correct a mistake.

That gives us a better starting question than “How do we improve the form?”: Can people complete the application and know what happens next?

Now the other pieces have a job:

The point is not to fill every box in a framework. It is to make the evidence available at the moment a team decides what to do.

Put every signal in context

Suppose the analytics show that many people leave on the document-upload step. That is a signal. It does not yet tell us to redesign the upload button.

Interview notes might show that applicants do not have the document at hand. Support conversations might reveal that the document name means something different to them. A few recordings might show an actual upload error. These are different problems, even if they appear at the same point in the funnel.

I would put the observations next to that step in the journey and ask: Who is affected? How often? What evidence supports each explanation? What do we still need to learn? Journey research guidance from NN/g describes the value of combining direct research with quantitative data for exactly this reason.

Turn the picture into a decision

The useful output is a sentence the team can test: “We think first-time applicants leave at the upload step because they cannot tell which document is required. Clearer guidance before they start should increase completed applications and reduce avoidable support contacts.”

That is a hypothesis, not a finding about everyone. It names a group, a problem, an action, and an expected outcome. We can check the explanation with applicants, change the experience, and measure what happens.

If the evidence points somewhere else, good. The map should change. A persona is not a character we need to defend, and a journey is not a poster we need to preserve.

Thinking end to end means keeping the line from people → behaviour → evidence → hypothesis → action → outcome visible. The next article asks how to choose the one outcome measure that keeps a journey focused.

Next: One journey, one success metric, several levers.

Keep reading

One journey, one success metric, several levers.