Two situations distort the framework enough to need explicit handling: severe time pressure, and difficult stakeholder dynamics.
Time-Pressured Discovery
A 20-minute executive call doesn’t allow full L1 process mapping before bridging. The framework doesn’t change — the sequencing compresses.
Triage the topic list before the call, not during it. Decide in advance which one or two topics actually need an L2 bridge in this session, and let everything else stay at L0/L1 on purpose, flagged for a follow-up.
Bridge earlier than Module 5 would normally recommend, but say so explicitly: “Given the time we have, let me try to state this back to you now rather than fully unpacking it — tell me if I’m off.” Naming the compression protects against it reading as overuse.
Resist the temptation to spelunk to “make the most of the time.” Time pressure makes detail-chasing feel productive — it’s the opposite; it burns the limited time on the wrong altitude.
Difficult Stakeholder Dynamics
A dominant voice crowding out others. One stakeholder — often the most senior person in the room — answers for everyone. Their statements aren’t wrong, but the standing test (Module 7) needs to be actively applied, not just checked passively: ask directly whether the quieter stakeholder with functional standing agrees, rather than assuming consensus because no one objected out loud.
A disengaged or unresponsive client. Bridge attempts get non-answers (“sure, whatever works”) — this looks like confirmation but is really an unwillingness or inability to engage at the L2 level. Don’t record it as confirmed. Flag it as provisional, and consider whether the real stakeholder with standing on this topic is even in the room.
A client who resists altitude at all — insists on speaking only in L3. Some clients (often technical ones) want to hand you a spec directly. This isn’t wrong, but the same rule from Module 6 applies: L3 without a traceable L0/L1 underneath it is still worth a light-touch check, even when it’s unwelcome, because a technically fluent client can still be solving the wrong problem fluently.
Next: Module 18 — Assessment and the Proficiency Model.