From Scribe to Consultant — Sharing Session Series
Every feature request, complaint, or wish a stakeholder brings to you is a message in a bottle. It floats on the surface, but its true origin lies deep beneath the waterline. The 7 Levels of Needs framework gives you a systematic way to dive from surface-level requests down to the core human and business drivers that actually define success.
This framework builds directly on the Iceberg Principle you explored in Session 1. While the Iceberg gives you the what (layers of human experience), the 7 Levels give you the how (a ladder of inquiry from feature request to vision).
L1 — Behavior (Feature Request): "I need a button that does X." The surface ask.
L2 — Pain & Frustration (Emotional Driver): "This process is driving me crazy." The feeling beneath the ask.
L3 — Perceptions & Assumptions (Belief Layer): "Management won't approve anything complex." The lens coloring the ask.
L4 — Expectations (Outcome Layer): "I expect this to save us 10 hours a week." The desired result.
L5 — Core Need (Fundamental Human Need): "I need to feel competent in my role." The human driver.
L6 — Business Value (Measurable Impact): "This aligns with our Q3 efficiency target." The organizational rationale.
L7 — Vision & Identity (Purpose Layer): "I want to be known as the person who transformed how we work." The identity stake.
Most BAs stop at L1 or L2. They hear the feature request, document it, and move on. The consultant-minded BA knows that the real need lives between L4 and L7. The feature request at L1 is just the stakeholder's best guess at a solution for a need they may not even be able to articulate.
The table below maps each level with its core question, typical stakeholder language, and what the BA should listen for:
| Level | Core Question | What They Say | What to Listen For |
|---|---|---|---|
| L1 — Behavior | "What do you want?" | "I need a dashboard." | Tangible feature, button, report, screen |
| L2 — Pain | "How do you feel?" | "This takes forever." | Emotion words: frustrated, tired, embarrassed |
| L3 — Perceptions | "What do you believe?" | "IT won't support that." | Assumptions about others, past experiences |
| L4 — Expectations | "What do you expect?" | "It should cut our workload in half." | Numbers, timelines, comparisons to peers |
| L5 — Core Need | "What do you need as a person?" | "I want to feel in control." | Acknowledgment, competence, autonomy, belonging |
| L6 — Business Value | "What value does this create?" | "We need to reduce churn by 15%." | KPIs, OKRs, strategic alignment |
| L7 — Vision | "Who do you want to be?" | "I want us to lead the market." | Identity statements, legacy, purpose |
As you read through each level in detail below, notice how each one builds on the previous. L1 is the tip of the iceberg. L7 is the deep current that moves everything.
L1 is the surface level — everything the stakeholder says, asks for, or complains about in concrete, observable terms. This is the domain of traditional requirements gathering: "I want a button," "The report should be in PDF," "We need a search bar." At this level, the BA acts as a scribe, capturing what is said without probing beneath it.
There is nothing wrong with L1. It is the necessary starting point. The problem is stopping there. Every feature request is a symptom of a deeper need. Your job is not to reject L1 — it is to use it as a doorway to the levels beneath.
| Speaker | Exchange |
|---|---|
| Client | "We need a real-time dashboard with 15 KPIs." |
| BA | "That's a good starting point. Before we define the KPIs, help me understand — what problem are you trying to solve with this dashboard?" |
| Client | "Our current reporting is too slow. By the time I get the data, it's already outdated." |
| BA | "So the real need is timeliness, not the number of KPIs. Let's explore that." |
Beneath every feature request lies an emotion. The stakeholder who says "I need a dashboard" may actually be feeling embarrassed when executives ask for updates and she has nothing to show. The HR manager who wants "a simpler system" may be feeling exhausted by manual workarounds. L2 is where you acknowledge and explore the emotional reality of the situation.
This is not about therapy. It is about validity and priority. A request driven by genuine frustration is more urgent than one driven by speculation. An emotionally connected stakeholder is more likely to champion the solution. When you understand the emotion, you understand the stakes.
| Speaker | Exchange |
|---|---|
| Client | "I'm honestly embarrassed every time my director asks for a pipeline update. I have to say 'I'll get back to you' and then spend two hours pulling data together." |
| BA | "That sounds exhausting. How often does this happen?" |
| Client | "Weekly, sometimes more. It makes me look unprepared even though I'm working hard." |
| BA | "So the real cost here is not just time — it's your confidence in those meetings. Let's design something that makes you look prepared in 30 seconds, not 2 hours." |
Every stakeholder comes with a set of beliefs about how the world works — about technology, about their organization, about what is possible. These beliefs may or may not be accurate, but they are real in their consequences. A stakeholder who believes "IT will never approve a new system" will design workarounds instead of asking for what they really need. A stakeholder who believes "the CEO loves flashy dashboards" will request visual features over functional ones.
Exploring L3 is delicate. You are not challenging the stakeholder's worldview — you are understanding the lens through which they see the situation. The goal is not to change their beliefs (at least not directly), but to see the problem through their eyes.
| Speaker | Exchange |
|---|---|
| Client | "I need a simple solution because IT takes forever to approve anything complex." |
| BA | "Tell me about that experience. What happened last time you tried to get something complex approved?" |
| Client | "Last year I proposed a CRM integration. It went through 4 review cycles and died in committee." |
| BA | "So you've learned that complex proposals don't survive. That makes perfect sense. What if we frame this differently — not as a big project, but as a pilot with measurable early wins?" |
| Client | "That might actually work. I didn't think of framing it that way." |
At L4, the stakeholder shifts from describing problems to describing what success looks like. This is the layer of outcomes, targets, and hoped-for results. "I expect this system to reduce our processing time by 50%." "My team should be able to onboard new clients in 3 days instead of 2 weeks." These are not yet measurable KPIs (that comes at L6) — they are the stakeholder's internal benchmark for satisfaction.
L4 is where many BAs stop their discovery, mistaking expectations for requirements. But expectations are still colored by assumptions and emotions. The real work is to validate whether these expectations are realistic, shared by others, and aligned with business value.
| Speaker | Exchange |
|---|---|
| BA | "If everything goes perfectly, what does success look like for you in 6 months?" |
| Client | "I want my team to stop emailing spreadsheets back and forth. We should have one source of truth that updates automatically." |
| BA | "That's a clear outcome. How would you know the team has stopped using spreadsheets? What metric would tell us?" |
| Client | "If I see zero spreadsheet attachments in my inbox for a week, that would be success." |
Beneath the expectations and outcomes lies something more fundamental: the core human need. This is the layer where the stakeholder's professional self intersects with their personal self. The need to feel competent, autonomous, respected, secure, or connected. These are the deep yearnings that Virginia Satir placed at the center of the Iceberg.
L5 is the most transformative layer for a BA to explore. When you understand someone's core need, you stop designing for a feature and start designing for a person. You move from functional requirements to human requirements.
| Speaker | Exchange |
|---|---|
| BA | "You mentioned wanting to look prepared in front of your director. What would it mean for you to feel truly prepared?" |
| Client | "It would mean I'm no longer anxious before those meetings. I could walk in and focus on strategy instead of scrambling for numbers." |
| BA | "So the deeper need is not just a dashboard — it's about your confidence and your ability to contribute at a strategic level. Is that right?" |
| Client | "Yes. I want to be seen as strategic, not just operational." |
L6 connects the human need to the organizational bottom line. This layer translates personal pain and human needs into business language: ROI, cost savings, revenue impact, efficiency gains, risk reduction. It is the bridge between the stakeholder's inner world and the business case that powers organizational decisions.
Many BAs make the mistake of jumping straight to L6 without exploring L2-L5. They ask "what is the ROI?" before understanding the human drivers. The result is a business case that feels hollow and fails to inspire. When you connect L6 value to L5 human needs, your business case becomes compelling because it tells a complete story.
| Speaker | Exchange |
|---|---|
| BA | "You mentioned saving 10 hours a week across your team of 5 people. What is that worth to the organization?" |
| Client | "At an average loaded cost of $50/hour, that's about $130,000 a year in reclaimed productivity." |
| BA | "And what about the cost of errors in the current manual process?" |
| Client | "We had a $200,000 billing error last quarter because someone copied the wrong number. So that's another risk factor." |
| BA | "So the business case is clear: $130K in productivity plus risk mitigation. Let's build that into the project charter." |
At the deepest level, every stakeholder has a vision for who they want to be — as a professional, as a team, as an organization. This is the layer of identity, purpose, and legacy. "I want to be known as the person who transformed our customer experience." "I want this company to be the industry benchmark for efficiency." These identity-level drivers are the most powerful motivators of all.
When you connect a project to L7, you create ownership and commitment. The stakeholder is no longer a requester — they are a co-creator pursuing a shared vision. This is the foundation of true partnership between BA and stakeholder.
| Speaker | Exchange |
|---|---|
| BA | "Imagine it's 2 years from now and this project has been a huge success. What story would you tell about what we accomplished?" |
| Client | "I would say that we transformed how our teams work. No more manual processes, no more silos. People actually enjoy coming to work because the tools support them instead of fighting them." |
| BA | "That's a powerful vision. And what would your role in that story be?" |
| Client | "I would be the person who saw that we needed to change and had the courage to start the conversation. I want to be remembered as the one who pushed for better." |
The natural flow of discovery is L1 → L7: start with the feature request and work deeper. But experienced consultant-minded BAs know a more powerful pattern: reverse mapping. Start the conversation at L7 (Vision & Identity) and work backward to L1 (Behavior). This approach changes everything.
When you start with vision, you:
Instead of: "Tell me what features you need for the new system."
Try: "Imagine it's a year from now and this project has been incredibly successful. What's different about your day-to-day work? What are you doing differently? How does it feel?"
Then work backward: What outcomes made that possible (L4)? What business value did we create (L6)? What human needs were fulfilled (L5)? And finally, what features should we build (L1)?
Reverse mapping takes more conversational skill because it requires you to hold the vision space without jumping to solutions. But it produces dramatically better outcomes because every feature decision is grounded in a clear, shared vision of success.
Knowing the levels is one thing. Knowing how to move between them in a real conversation is another. The following scripts show practical transitions you can use to guide stakeholders gently from one level to another. Use these as templates, not scripts — adapt the language to your natural speaking style and the relationship you have with the stakeholder.
BA: "You mentioned needing a real-time dashboard. Walk me through what happens during your week — where does the current process fall short?"
Client: "Well, I spend hours pulling reports every Friday afternoon. It's tedious and I dread it."
BA: "That sounds frustrating. What's the most draining part of that process for you?"
Client: "The repetition. It's the same queries every week. I feel like a machine instead of a strategist."
BA: "So the real pain isn't just the time — it's that you feel your skills are being wasted on repetitive work. Is that right?"
BA: "You mentioned feeling frustrated with the approval process. Why do you think it's so slow?"
Client: "IT is always the bottleneck. They don't understand our team's needs."
BA: "Tell me more about that. How did you come to that understanding?"
Client: "Every time we submit a request, it takes weeks. They ask for more information, we reply, they go silent."
BA: "So your experience tells you that IT is a blocker. What would need to be true for you to see them as a partner instead?"
BA: "Given what you've described, what would a great outcome look like for you?"
Client: "I want approvals to take no more than 3 days. And I want clear communication throughout the process."
BA: "That's a clear expectation. How would you track whether we're meeting that?"
Client: "If I don't have to chase anyone for status updates, that's a win."
BA: "You mentioned wanting faster approvals. What would having that change for you personally?"
Client: "I would feel less anxious. Right now I'm constantly worried something will get stuck and I'll miss my deadline."
BA: "So the deeper need is about feeling in control of your outcomes. Would you say that's accurate?"
Client: "Yes. I need to feel like I can deliver on my commitments without depending on unpredictable factors."
BA: "If we solve for that need for control and predictability, what would the business impact be?"
Client: "We would hit our project milestones more consistently. Right now we're delayed on 3 major initiatives because of approval bottlenecks."
BA: "What's the financial impact of those delays?"
Client: "Rough estimate: about $500K in delayed revenue per quarter."
BA: "If we deliver that $500K impact and create a predictable workflow, what does that mean for you and your team's identity?"
Client: "My team would be seen as the most reliable unit in the company. We'd set the standard for how work gets done."
BA: "That's a powerful vision. What would you want people to say about your role in making that happen?"
Client: "I want them to say I was the one who fixed the broken process. That I had the courage to challenge how things were done."
BA: "So we've established that your vision is to be known as the person who fixed the process and set a new standard. Let's work backward: what outcomes do we need to deliver for that to be true?"
Client: "We need 3-day approvals, zero manual follow-ups, and real-time visibility into request status."
BA: "Great. Now, what features would support those outcomes? Let's start listing what we need to build."
Client: "An automated approval workflow with notifications. A status dashboard. Integration with our existing ticketing system."
BA: "Now we have a clear line from vision to features. Let's document this and validate with your team."
Apply the 7 Levels framework to the following scenarios. For each one, identify the levels at play, practice the probing questions and transitions, and map the path from L1 to L7 (and back using reverse mapping).
Context: A warehouse operations manager requests "a better reporting system" because the current one gives him data that is "always 2 days old." He manages 12 supervisors and reports to the VP of Supply Chain weekly.
Client says: "I need real-time reports. By the time I get today's numbers, they're already history. My VP wants current data, not last week's news."
Questions for reflection:
Context: A customer service director wants to build a customer portal so clients can "track their own tickets." The current process requires customers to call or email for status updates. The CS team is overwhelmed with 200+ status inquiry calls per day.
Client says: "We need a self-service portal. Customers should be able to log in, see their open tickets, and check status without calling us."
Questions for reflection:
Context: A finance manager needs to migrate data from an old ERP system to a new one. She has been given this task by her CFO and has 4 months to complete it. She seems anxious and is requesting "a complete data migration tool with validation and rollback capabilities."
Client says: "I need a migration tool that can handle all 15 years of historical data, validate every record, and roll back if anything goes wrong."
Questions for reflection: