The sponsor opens discovery with the diagnosis already made: "The order-to-cash cycle is too slow. Replace the invoicing system." Your first week of interviews shows the delay has several parts, and the system is only one of them. "It's more complicated than that" is true, but it gives the sponsor nothing to look at.
This lesson uses a fictional engagement. It teaches the English for structuring a problem in discovery. What the problem turns out to be is still your diagnosis.
Four expressions carry that conversation, and each does a different job:
Unpack the assumption → map out the process → surface what came up → name the low-hanging fruit
Open the client's assumption: unpack
To unpack an assumption is to break it into its parts so the group can examine them one at a time.
"Before we scope a system change, let's unpack the assumption that the invoicing system is the driver. The delay has at least three parts."
Use it for something layered, not for a simple fact; a single clarifying point is explained, not unpacked. Aim it at the reasoning, never at the person: unpack the assumption, not unpack what you said. Break down itemizes a quantity; dig into investigates something not yet on the table.
Bad: "I'm not sure the system is really the issue." Better: "Let's unpack the assumption that the system is the driver. The delay has three parts: order entry, approvals, and the system itself."
Make the process visible: map out
To map out a process is to turn something scattered into an organized, visible version that everyone can review.
"We'll map out the order-to-cash process end to end, from order entry to cash received, before we decide where the time goes."
It produces the structure; it does not draw the conclusion. Lay out presents a plan that already exists; figure out solves something unknown. It is separable: map it out, never map out it.
Bad: "We need to understand the process better first." Better: "We'll map out the process end to end, so we can all see where the time goes."
Want to get better at distinctions like this?
Lyra Practice helps you learn the nuance of high-value workplace expressions, then practice using them in realistic situations.
See how Lyra Practice works →Bring hidden issues into view: surface
An issue surfaces when something hidden or unspoken comes into view. You can also surface an issue with a group.
"Three handoff gaps surfaced in the interviews that nobody raised at kickoff. I want to put them on the table today."
Use it only when the issue was not already in view; raise is the neutral verb when nothing was hidden. Surfacing makes an issue visible. It does not escalate, verify, or resolve it, and it does not say who should have seen it first. In discovery, "gaps surfaced in the interviews" describes the finding without describing the client.
Bad: "There are some things you didn't tell us about the handoffs." Better: "Three handoff gaps surfaced in the interviews that nobody raised at kickoff."
Keep easy separate from important: low-hanging fruit
Low-hanging fruit is a task that is both easy to do and worth doing.
"The approval thresholds look like low-hanging fruit: easy to change and worth changing, whatever we decide about the system."
It says nothing about how large the impact will be, so keep easy separate from important. It is uncountable, and it describes tasks, never people. It is a spoken expression; in the written deliverable, call them near-term improvements.
Bad: "There are some quick wins here too." Better: "The approval thresholds are low-hanging fruit: easy to change and worth changing. The system replacement is the larger, harder piece."
Nuance: opening, mapping, surfacing, sequencing
- Unpack opens the assumption behind a conclusion. It is not explain (one point), break down (a quantity), or dig into (an investigation).
- Map out makes the process visible. It is not lay out, which presents a plan that already exists, and it is not figure out, which ends in an answer rather than a map.
- Surface brings a hidden issue into view. Raise is neutral; escalate sends it up the hierarchy; flag marks it for attention.
- Low-hanging fruit is easy and worth doing. A quick win is a useful result achieved soon, whatever the effort. Move the needle is about impact, which low-hanging fruit never claims.
Dialogue
A fictional finance director and consultant, at the end of the first discovery week:
Finance director: The cycle is too slow and the invoicing system is the problem. How quickly can you scope the replacement?
Consultant: Before we scope a system change, let's unpack the assumption that the system is the driver. From the first week, the delay has at least three parts: order entry, approvals, and the system itself.
Finance director: So what do you propose?
Consultant: We'll map out the order-to-cash process end to end, from order entry to cash received, so we can all see where the time goes.
Finance director: We already know the process.
Consultant: Three handoff gaps surfaced in the interviews that nobody raised at kickoff, and I want to put them on the table today. And the approval thresholds look like low-hanging fruit: easy to change and worth changing, whatever we decide about the system.
Put together:
"Before we scope a system change, let's unpack the assumption that the invoicing system is the driver; the delay has at least three parts. We'll map out the order-to-cash process end to end, from order entry to cash received, so we can all see where the time goes. Three handoff gaps surfaced in the interviews that nobody raised at kickoff, and I want to put them on the table today. The approval thresholds look like low-hanging fruit: easy to change and worth changing, whatever we decide about the system."
Scenario
A different fictional client says its new-hire onboarding takes too long and wants a new learning platform. Your first week of interviews shows the delay sits mostly in equipment requests and manager approvals, plus two handoffs between HR and IT that nobody mentioned at kickoff. The approval step could be changed quickly.
Your turn. Answer in four sentences: open the assumption, say how you will make the process visible, say what came into view in the interviews, and name the easy, worthwhile fix separately from the platform decision.
Quiz
The client's project lead mentioned the approval bottleneck at kickoff, and your interviews confirmed it. Which sentence describes the situation precisely?
- "The approval bottleneck surfaced in our interviews."
- "The approval bottleneck you raised at kickoff is confirmed by the interviews."
- "The approval bottleneck is the low-hanging fruit, so it will move the needle."
Answer: 2. Nothing was hidden, so raise is the right verb and surface would imply a discovery that never happened. Sentence 3 uses low-hanging fruit to claim impact, which the expression never does.
Practice
Practice all four expressions in realistic discovery scenarios at Lyra Practice.
Return to English for Consultants for readouts, qualified recommendations, scope, and pushback.
Related guides
- Unpack in a Sentence: Natural Examples
- Map Out in a Sentence: Natural Examples
- Surface in a Sentence: 10 Examples
- What Does Low-Hanging Fruit Mean at Work?
- Surface vs Raise: What's the Difference?
- How to Ask a Client for Clarification Professionally in English
- How to Challenge a Client Assumption in English Without Losing the Room
- How to Present Findings in a Recommendation Readout in English