Most first calls between agencies and clients follow a familiar pattern. The conversation starts with features, timelines, and scope. The focus quickly shifts to what needs to be built and how fast it can be delivered.
While this creates momentum, it often skips over the questions that actually shape whether the work will succeed. Over time, we have found that asking better UX discovery questions early changes not just the conversation, but the quality of the projects that follow.
Why Most First Calls Stay at the Surface
In most first call or discovery conversations, there is a natural tendency to begin with what needs to be built.
The default opening question is often some version of “what do you want to build,” which feels like a practical place to start. However, it tends to anchor the discussion around outputs rather than outcomes. Clients describe features, and agencies begin translating those features into scope. The conversation moves quickly toward estimates and delivery.
What often remains unclear is whether those features are connected to a meaningful definition of success, how they will be used in practice, and what constraints or trade-offs are already in play.
This is not a problem of intent. It is a problem of starting point. When the conversation begins with building, it becomes harder to step back and question whether the right thing is being built in the first place.
When the conversation begins with building, it becomes harder to step back and question whether the right thing is being built in the first place.
The Shift: From Features to Framing
Over time, we have moved away from leading with feature-based questions and instead rely on a small set of structured UX discovery questions that surface what matters before anything is scoped.
These questions are not complex, and in many cases they feel obvious once asked. What makes them valuable is how they reposition the conversation. Instead of focusing on what should be built, the discussion begins to explore why it matters, how it will be used, and what should be avoided.
This shift creates clarity early, before assumptions become embedded in scope or timelines.
Why These Questions Matter More Than They Seem
Early-stage conversations define more than just the starting point of a project. They shape how decisions are made, what gets prioritized, and how teams interpret success throughout delivery.
When discovery is shallow, uncertainty moves forward into development. Teams spend more time reacting, clarifying, and revisiting decisions that could have been explored earlier. This is something we explore further in our article on the pre-sales UX audit and how early clarity shapes better proposals.
When discovery is structured, that uncertainty is reduced before it spreads. Questions that might have surfaced mid-sprint are addressed before scope is finalized, allowing teams to move forward with a clearer understanding of what they are building and why.
This is not about adding process. It is about improving the quality of the thinking that informs everything that follows.
This is not about adding process. It is about improving the quality of the thinking that informs everything that follows.
1. What Does Success Look Like 90 Days After Launch?
This question reframes the entire conversation around outcomes rather than outputs.
Instead of focusing only on launch, it asks what should be different once the product is in use. This might relate to user behavior, operational efficiency, conversion, or internal workflows. The exact answer varies, but the exercise forces the team to define success in more concrete terms.
In many cases, this is the first time success is articulated beyond “it works” or “it launches on time.” Once success is clearly defined, it becomes easier to evaluate whether the proposed features actually support that outcome. It also creates a shared reference point that can guide decisions throughout the project.
2. Whose Job Gets Easier When This Ships?
Features often exist in isolation until they are connected to real people.
This question shifts the focus toward the individuals who will interact with the product, whether they are end users, internal teams, or both. It moves the conversation from abstract functionality to practical impact.
When a team can clearly identify whose job is being improved, it becomes easier to prioritize what matters and remove what does not. It also surfaces an important signal. If no one’s job becomes meaningfully easier, it is worth questioning why the feature exists in the first place.
3. What Is the Version of This We Refuse to Build?
Every project has constraints, but they are not always made explicit.
This question introduces boundaries early in the process by asking the team to define what “not good enough” looks like before work begins. This could relate to usability, performance, scope creep, or compromises that would undermine the product.
By making these boundaries visible, the team establishes a shared standard. It reduces the risk of gradual compromise over time, where small decisions accumulate and shift the product away from its original intent.
4. Who Has to Say Yes, and Who Just Has to Not Say No?
Alignment is rarely just about agreement. It is about understanding how decisions are made.
This question surfaces the structure behind the project. It identifies who is responsible for approving direction, who influences decisions, and where potential friction may come from.
In many cases, delays and misalignment are not caused by poor decisions, but by unclear ownership. When this is clarified early, teams can navigate decisions more effectively and avoid unnecessary friction later in the process.
What These UX Discovery Questions Change
Individually, each of these questions is simple. Together, they reshape how the project begins.
They move the conversation away from immediate execution and toward structured thinking. They surface assumptions before they are embedded in scope and create alignment before timelines tighten.
This does not slow down the process. It reduces the likelihood of rework, misalignment, and unclear expectations later. Over time, it also changes the type of conversations agencies have, with clients engaging more deeply and projects starting from a place of clarity rather than urgency.
When This Becomes a Pattern
Asking better questions once is useful, but making it a consistent part of how conversations begin is where the impact compounds.
Teams begin to recognize patterns earlier. Assumptions become easier to identify. Decisions become more intentional and grounded in shared understanding.
This is often the difference between projects that feel reactive and those that feel structured and predictable.
Final Thought
The first call in a project does more than gather information. It sets the direction for everything that follows.
When the conversation starts with better UX discovery questions, it becomes easier to build the right thing, align the right people, and move forward with greater clarity.
If you are exploring ways to bring more structure into your early conversations, this is often where it begins.
You can explore some of our recent work here: https://pepperplane.com/work/
If it feels relevant to how your team operates, you can book a discovery call and we can take a closer look at how this approach might fit into your process. Schedule your call here.
