You've mastered five integrated language systems. Now deploy them all simultaneously under real consulting pressure.
By the end of this lesson, you'll be able to:
In real consulting work, you never use just one system. A single client conversation demands that you:
This lesson is your integration point. You'll see how professionals blend these systems into one coherent voice that builds trust, manages expectations, and solves problems.
Speed round: retrieve expressions from all five systems. These are your building blocks for integration.
Saxon (direct, simple): help, end, get, use, make, give
French (mid-register): assist, complete, employ, provide, create
Latin (formal, abstract): facilitate, terminate, utilise, deliver, implement
Example: "We need to help the team get to the finish line" (Saxon, accessible) vs. "We should facilitate the team's delivery of milestones" (Latin, formal).
In consulting, you shift between these based on your audience: use Saxon with operations teams, Latin with the board.
Soft agreement: "I see what you mean, but..." / "That's a fair point. At the same time..."
Speculating safely: "It could be that..." / "On the one hand... on the other hand..."
Weighing up: "The case for X is strong. The case for Y is equally..." / "There's merit in both positions."
Example: "Your proposal is compelling. The data certainly supports the direction. What I'd add is that the implementation timeline assumes best-case resource availability. If we secure additional budget, we're in strong shape. If not, we may need a phased approach."
This says "yes, but" without seeming evasive. You build credibility by showing you've thought through both upside and risk.
Checking: "What I'm really getting at is..." / "Just to be clear, I'm not saying..." / "Does that land?"
Signposting: "Before I go into detail, the big picture is..." / "Here's what matters most..." / "Let me start with the headline."
Example: "Let me start with the headline: this initiative is feasible, but it depends on three things. First, stakeholder alignment—which I think we have. Second, budget. And third, timeline. What I'm really getting at is that success isn't about the concept; it's about execution discipline. Does that frame it clearly?"
You've signposted structure, delivered the headline, itemised dependencies, and checked understanding—all in one turn.
Softening phrases: "It's broadly in line with..." / "At this stage, I'd say..." / "There may be another angle here..."
Face-saving moves: "The numbers suggest X, though we should also consider..." / "That worked in context Y; in context Z, we might..."
Example: "The results are broadly in line with our forecast. What's interesting is that the variance in Region 2 may be telling us something about implementation approach. There could be another angle worth exploring there."
You've acknowledged results, hinted at a problem, and reframed it as opportunity—without direct criticism. This is face-saving imprecision at work.
Processing markers: "I'm thinking out loud here, but..." / "Actually, let me rephrase that..."
Building on ideas: "Building on that..." / "To your point, and extending it..." / "That makes me think..."
Example: "I'm thinking out loud here, but what if we approached this as a phased rollout? Actually, let me rephrase that—what if we tested the core functionality in market A first, then..." / "Building on what you said about customer retention, I'm wondering if the issue isn't acquisition cost, but post-sale support. Let me think through that logic."
You're modelling the thinking process. This builds trust because it shows you're working through problems in real time, not regurgitating pre-baked answers.
See how the five systems work together in a single professional turn. Then build your own.
"Do you think this strategy will actually work? Or are we just kicking the can down the road?"
Response:
"That's a legitimate concern. I see what you mean, but let me break this down. The headline here is that we have three components to this approach, and success isn't binary.
The first piece—market positioning—is something we can implement immediately with strong conviction. The data there is solid. What I'm getting at is that this alone doesn't move the needle.
The second piece is where it gets interesting. I'm thinking out loud here, but the risk mitigation depends on how aggressively we staff the new team. Actually, let me rephrase that—it depends on whether we facilitate a full transition or assist with a gradual handover.
On the third piece—yes, there's a timing variable. On the one hand, if we move fast, we capture market opportunity. On the other hand, we risk overextending resources. There may be another angle: a phased approach that de-risks both.
So, are we kicking the can? It could be that we are, if we treat this as a one-time push. What I'd say at this stage is: if we treat it as an integrated system with real accountability for each phase, we're not—we're building a foundation. Does that distinction land?"
What makes this work:
Use this framework. Respond to the prompt below using all five systems.
Hint: You might start by signposting ("What this comes down to is..."), then layer in hedging ("It could be that we need to..."), soften trade-offs ("There may be another way to resource this..."), think aloud ("I'm wondering if we should..."), and check ("Does that seem workable?").
"I appreciate that, because capacity is real. What this comes down to is sequencing and support. I see what you mean about being stretched, and I'd say there are actually a couple of angles here.
First, this doesn't require your full team to shift. It could be that we carve off a dedicated subset—maybe three people—and facilitate their transition to this work, while the rest maintain business-as-usual. I'm thinking out loud here, but what if we backfill their capacity externally for the first quarter?
Second—and building on that—there's a phasing question. We could either launch with full scope, or we could soft-launch with core features only. On the one hand, a full launch shows commitment. On the other hand, a phased approach buys us runway for learning and adjustment.
What I'd say at this stage is: this is solvable. It's not a capacity problem; it's a resourcing and sequencing problem. Does that distinction help? And which of those two paths—dedicated team with backfill, or phased scope—feels more realistic to you?"
You're presenting a recommendation to a sceptical board. Your data is strong but incomplete. Some board members disagree with your direction.
You've spent six weeks analysing the company's go-to-market strategy. Your recommendation: pivot from direct sales to a hybrid model with channel partners. The data supports this. But:
You have 2 minutes to present your case. You must acknowledge the concerns without backing down from your recommendation. Use all five language systems.
Model Opening (first 40 seconds):
"Let me start with the headline: the data supports a move to a hybrid go-to-market model. But I want to be honest about what that means. This isn't a simple pivot; it's a managed transition, and it comes with real costs.
Here's what I'm really getting at: our direct model works, but it's plateauing. We're seeing margin compression year-on-year, and CAC is rising faster than LTV. The opportunity is in channels—but I see what you mean, Sarah, when you say the model is unproven for us. It is. That's actually the key risk.
What the data shows is that for our product category and price point, a hybrid approach—we keep the top 30 accounts direct, we facilitate channel partnerships for the rest—gives us better unit economics at scale. The case for moving is strong. The case for staying with pure direct is also defensible if we can absorb the cost pressure. On the one hand, hybrid is riskier because execution matters. On the other hand, staying pure-direct is riskier because of the unit economics."
REGISTER: "facilitate" (formal) + colloquial summary (accessible) / PRAGMATICS: "here's what I'm really getting at" + "headline" / UNCERTAINTY: "I see what you mean, but" + "on the one hand...on the other hand"
Model Middle (next 40 seconds):
"Now, the implementation question. The cost is real. We need to invest in partner enablement, we need to manage channel conflict, and we need new operational capability. CFO, you're right to focus on margin. In year one, we're looking at maybe a 2–3 point hit while we build out the channel. What I'd say at this stage is that by year two, hybrid model should yield 150–200 basis points of upside. Not guaranteed, but the math is there.
I'm thinking out loud here, but what if we structure this as a pilot? We launch the hybrid model with three partner categories, we hit defined milestones on partner performance, and we gate further investment on those outcomes. That de-risks the margin question and gives us data before we go all-in."
IMPRECISION: "what I'd say at this stage" / THINKING: "I'm thinking out loud" + pilot reframe / PRAGMATICS: Check via structure proposal
Model Close (last 40 seconds):
"So—recommendation: approve the hybrid model, structure it as a gated pilot, and invest in partner enablement. This isn't kicking the can. It's a systems-based approach to growth with downside protection. Does that framing address the core concerns? And what do you need from me to move forward with confidence?"
PRAGMATICS: Reframe "kicking the can" + check understanding
What Works:
A major project isn't going well. You need to explain the situation to a client without destroying confidence, while being honest about problems.
You're three months into an eight-month transformation project for a key client. Expected progress: 40%. Actual progress: 28%. The gap is due to:
The client sponsor is on the call. She's invested politically in this project. She'll find out about the delay from someone else if you don't tell her now. You must:
You have 3 minutes to explain the situation, acknowledge impact, and present options.
Model Opening (first 50 seconds):
"I want to give you an honest update on progress. The headline is: we're tracking at 28% completion against our 40% target at this stage. I know that's not what we both hoped to see, and I want to explain what's driving it and what we're going to do about it.
Here's what I'm really getting at: this isn't a project crisis, but it is a reality-check moment. And I'd rather have this conversation with you now than have you find out from someone else. The gap is real, and there are real reasons for it."
PRAGMATICS: Headline + signposting + checking / PRAGMATICS: "What I'm really getting at" for clarity
Model Middle—Explanation (next 70 seconds):
"There are three things driving this. First, the stakeholder alignment piece has taken longer than we anticipated. That's partly our miss—we should have built more buffer into the engagement plan early on. It's also partly the reality of your organizational complexity, which we underestimated. On the one hand, that's a tough reality. On the other hand, what it's told us is that the change piece is going to be more important than we initially thought.
Second, scope. There's been some technical scope creep around the legacy system. We've facilitated those conversations with your team, and I see what you mean when you say 'those are important changes.' They are. But they weren't in the original charter. That's on me—I should have gated scope changes more tightly upfront.
Third, complexity. I'm thinking out loud here, but the system integration challenge is more intricate than anyone—including us—understood from the initial assessment. We thought we could move through that faster. Actually, let me rephrase that: we can move through it, but doing it properly requires careful sequencing.
What I'd say at this stage is: none of these is a showstopper. But together, they're real. And they change the math on the timeline."
THINKING: "I'm thinking out loud" + "let me rephrase" / REGISTER: "facilitate" (formal) + "move through" (accessible) / IMPRECISION: "what I'd say at this stage" / UNCERTAINTY: "on the one hand...on the other hand"
Model Close—Path Forward (remaining time):
"Here's what I'm proposing. We have three options. Option one: we extend the timeline by six weeks and keep the scope and team size as planned. The quality stays high, and you get everything we promised. Option two: we keep the eight-month timeline but reduce scope—we deliver core functionality first, non-critical enhancements in a phase two. Option three: we bring additional resources onto the integration work, which accelerates the timeline but increases cost.
My honest read? I'd recommend option one. It gives us the margin to do this right. But there may be another angle—maybe you have calendar constraints I'm not thinking about. What matters most to you here? And what do you need from me to move forward with confidence?"
PRAGMATICS: Three clear options + checks understanding / IMPRECISION: "there may be another angle" / PRAGMATICS: Final check + invitation to co-create
Why This Works:
Open-ended consulting challenge. The CEO asks a question with no simple answer. You have 30 seconds of thinking time, then you go.
You're in a strategy session. The CEO turns to you and asks: "Where should we be in 5 years? What does world-class look like for us?"
This is open-ended. You don't have a prepared answer. The room is watching. You need to:
30 seconds thinking time Then speak for 2–3 minutes.
Model—Thinking Out Loud (first 45 seconds):
"That's a great question, and I want to think through it properly rather than just give you a glib answer. Let me think out loud here.
I'm framing this in a few dimensions. One is scale: where do we need to be competitively? Another is capability: what do we need to be able to do? And then there's culture and values: what kind of organization are we building? Because all three have to align.
Building on that, let me start with what I see in the market. If we look at the competitive landscape, the companies winning five years from now aren't the ones that are just bigger. They're the ones with some combination of scale plus proprietary capability plus a talent brand that lets them attract world-class people."
THINKING: "think out loud" + "let me think through it" / PRAGMATICS: Signposting dimensions / THINKING: "Building on that"
Model—Framing the Vision (next 50 seconds):
"So here's what I think world-class looks like for you. On the one hand, you need to be meaningfully bigger—I'd say 2–2.5x revenue. You need proprietary IP in areas where competitors can't easily follow. On the other hand, it's not about growth for growth's sake. It's about whether you can deliver something your customers can't get anywhere else, and whether your people actually want to work here.
I'm thinking out loud, but what if we framed it this way: world-class is when you're the first call for your best customers, not because you're the cheapest, but because you're the most trusted. That's a maturity thing. That takes five years to build.
Actually, let me rephrase that. I think it's when you've moved from being a good vendor to being a strategic partner. That requires a shift in how you work—it's less transactional, more integrated."
UNCERTAINTY: "on the one hand...on the other hand" / THINKING: "I'm thinking out loud" + "let me rephrase" / REGISTER: "deliver" (formal) + "good vendor" vs "strategic partner" (conceptual shift)
Model—Realistic Framing (last 45 seconds):
"Now, here's where I'm less certain. The path to get there depends on some assumptions you'd need to validate. It could be that M&A is part of the answer—if you need capability you can't build. It could be that it's an organic build play. There may be another angle I'm missing about your competitive position or market dynamics.
What I'd say at this stage is: define what 'world-class' means for you first—is it scale, is it margin, is it innovation, is it customer intimacy? Because your five-year plan flows from that definition. Does that frame it? And what's your intuition on what matters most?"
IMPRECISION: "I'm less certain", "could be", "there may be another angle" / PRAGMATICS: Reframe to "define what matters first" + check understanding
Why This Works:
Use these to deepen your thinking about what you've just demonstrated.
You've completed the five-lesson series. Retrieve what you've learned. Reflect on what's shifted.
Name one expression or technique from each of the five systems. Then say why it matters in consulting.
Lesson 1: Register Switching
Name one Saxon/French/Latin contrast. Why does it matter? (E.g., "help vs assist vs facilitate")
Lesson 2: Calibrated Uncertainty
Name one hedging phrase. When would you use it? (E.g., "I see what you mean, but...")
Lesson 3: Pragmatic Clarity
Name one checking or signposting move. Why does it help? (E.g., "Just to be clear, I'm not saying...")
Lesson 4: Strategic Imprecision
Name one softening phrase. How does it help in difficult moments? (E.g., "There may be another angle...")
Lesson 5: Thinking Aloud
Name one thinking marker or self-correction. What does it signal? (E.g., "I'm thinking out loud here, but...")
You've now seen these five systems work together in consulting scenarios. Reflect on what you notice.
Complete this statement. Make it personal to you and your consulting practice.
"After this five-lesson series, I can now:
You've moved from understanding individual language systems to integrating them into a professional voice that:
This is how consultants build lasting credibility and move organizations. Not through bombast or false certainty. Through language that's precise, strategic, and deeply human.
Your edge as a consultant isn't just what you know. It's how you say it.