Opportunity
·
Career Growth
Your Client Gave You 20 Problems. They Have Five.
Discovery produces long lists. The firms that create the most value look for the few root causes underneath, and the professionals who can turn twenty problems into five become the people clients ask for by name.

Ask a client to describe what’s wrong, and you’ll rarely get a short answer. Discovery sessions produce long lists: reports that don’t match, systems that don’t talk to each other, teams working off spreadsheets, approvals that take too long, data no one trusts. By the end of the week, there might be twenty items on the board.
Most teams treat that list as the scope. They prioritize it, estimate it and start working through it.
The firms that create the most value for clients do something different first. They look for the five problems underneath the twenty.
Why the list is longer than the problem
Long lists come from siloed thinking. Each department describes its pain from its own vantage point. Finance sees inconsistent numbers. Operations sees manual workarounds. Leadership sees slow decisions. Each complaint is real, but many of them are symptoms of the same few root causes.
Clients also tend to list what’s visible rather than what’s causing it. People describe the report that’s always late, not the data architecture that makes it late. They describe the meeting that drags on, not the unclear decision rights that make it drag.
Take a common example. A business wants to understand its margins, but the inputs that drive them live in disconnected systems and spreadsheets. That single root cause might generate a dozen separate complaints across the organization, from late reports to conflicting forecasts to analysts spending their weeks reconciling numbers by hand.
If you solve those twelve complaints one at a time, you’ll stay busy for a long time and the client will still feel stuck. If you identify the underlying issue and solve it well, many of the symptoms disappear together.
The real question is what you’re solving for
Delivery teams often have a great deal of autonomy in how they interpret a client’s needs. That autonomy is valuable, but it also means each person can end up solving for something slightly different. One product lead optimizes for the request in front of them. Another optimizes for the system. A third optimizes for the stakeholder who complains the loudest.
Before any of that, someone has to ask a simple question and keep asking it: what are we actually solving for here?
This is where a lot of efficiency is quietly lost. When every person on a delivery team interprets the client’s needs through their own lens, the team spends days debating priorities that a shared answer would have settled in an afternoon.
When a team agrees on the answer, everything downstream gets easier. Requirements become clearer. Trade-offs become easier to make. And the client starts to see the team as a strategic partner rather than a group working through a ticket queue. Getting there depends on asking better questions than the client expects, a discipline I described in Lead With Better Questions.
Questions that turn twenty into five
Here are the questions I use when I’m helping a team move from a long list to the few things that matter.
Which of these would disappear if something else were fixed? Group the items by cause rather than by department. Patterns show up quickly.
Which outcomes does the client care about most? Not features, but results: faster decisions, better margins, happier customers, less manual work. Map every item to the outcome it serves.
What does the client already know, and what can they not yet see? Clients are experts in their business. They’re often too close to it to notice how their problems connect. Showing them those connections is some of the most valuable work you can do.
What would make the biggest difference if we did it first? Not the easiest item. The one that unlocks the most.
What are we choosing not to do, at least for now? Saying it out loud protects focus and sets honest expectations with the client.
A skill that defines careers
The same skill happens to be one of the clearest markers of who’s ready for more responsibility.
Professionals who can turn twenty problems into five become the people leaders want in the room. They make complexity manageable. They help others focus. And they earn trust, because clients and colleagues can see that they understand the situation more deeply than the list suggests. They also tend to be the people clients ask for by name on the next engagement. It takes confidence to tell a client their twenty problems are really five, and even more to be right about it. That’s why the discipline has to be developed rather than assumed.
The same discipline applies inside your own organization. If you ask your teams what’s holding them back, you’ll get a long list too. Look underneath it. You may find that a few root issues, often about how people are led and how they work together, explain most of what’s on the board.
And you don’t have to fix everything at once. If your organization is operating at a three out of ten, getting to a five is a radical improvement. Start with the few things that matter most and let the rest follow.
Want to explore these ideas further? Learn more about my work on leadership, identity and conviction at www.theglennllopis.com.
A long list is a symptom of siloed thinking. Find the few problems that explain the rest.
© 2026 Glenn Llopis Group, LLC. All rights reserved.
This article is the original work of Glenn Llopis and is protected by copyright. It may not be republished, reproduced, distributed or adapted, in whole or in part, in print, online or by AI tools, without prior written consent. You are welcome to share the link or quote a brief excerpt with credit to Glenn Llopis and a link back to this page. For permission requests, contact solutions@glennllopisgroup.com.
Get the next essay in your inbox
New essays on leadership, identity and conviction, sent to you when they publish. Free, and you can unsubscribe anytime.
Thank you. You're subscribed to Conviction Chronicles.
Something went wrong. Please try again.



