Start With Your Colleagues: Why Internal Discovery Comes First

The counterintuitive discipline of journey work is that the first round of discovery is not with customers — it is with colleagues. Before talking to the people who use the product or service, you need to understand the people who build and maintain it. What they know, what they assume, where they are blocked, and what solutions they are already developing.

This is not a workaround for limited customer access. It is a structural necessity.

What Internal Discovery Produces That External Discovery Cannot

Internal discovery — interviews with colleagues across product, marketing, engineering, customer service, and operations — produces two things that external research cannot replicate.

First, it surfaces the organizational reality behind the customer experience. The pressures that prevent teams from fixing known problems. The initiatives already underway that nobody outside the team is aware of. The knowledge that lives in customer service but never reaches product. The competing priorities that explain why certain pains persist quarter after quarter. This context is essential for designing solutions that can actually be implemented — and it is invisible to customers.

Second, it creates the political conditions for the work to succeed. When colleagues feel heard — when their pressures are documented, their emerging solutions are placed on the map, their constraints are acknowledged rather than dismissed — they become invested in the journey work. They start to see themselves in the map. That investment transforms the alignment workshop from a presentation into a genuine collaborative session.

"Before you can understand your customers, you must understand your colleagues. Discovery begins inside the organization, with the people who work closest to the experience. These interviews are the engine of your early insights, your first map points, and, crucially, your first alliances."

The Sequence That Works

Start with your sponsor — the product owner, team lead, or program director who invited the journey work. They know why the project exists, where the most significant friction lives, and who else you should speak to. The first interview is as much about building trust with the person who authorized the work as it is about collecting insights.

From there, expand outward in two directions: toward the teams closest to the experience (customer service, UX, direct sales) and toward the teams furthest from it (engineering, finance, legal). The closest teams will have the most granular customer knowledge. The furthest teams will have constraints and pressures that are invisible to those close to the experience.

The target is five to fifteen internal interviews, depending on the size and complexity of the organization. Saturation — the point at which new interviews are producing mostly confirmation of patterns already identified — is more important than a specific number.

The Tone That Works

Internal discovery interviews are not workshops. There are no exercises, no timers, no collaborative boards that participants need to navigate. They are conversations — structured, but disarmingly human.

The structure comes from the designer's framework: start with pressures ("what's not working for you right now?"), move to customer needs and pains ("what do you see customers struggling with?"), explore gains ("where does the experience work well?"), and close with emerging solutions ("what are you already working on?").

The humanity comes from the designer's posture: genuine curiosity about the interviewee's reality, not data extraction. When people feel heard rather than interviewed, they share more. They mention the embarrassing truth that they would not put in a survey. They describe the workaround they have been using for eighteen months because the real fix was never prioritized.

The best discovery interviews feel like conversations neither participant expected to have. That is when the most useful material surfaces — not despite the lack of structure, but because the structure was relaxed enough to allow it.