09 · Serving vs. Directing (The Mindset Shift)¶
Every module so far has built a skill — listening, empathy, trust, delegation, communication, feedback. This module steps back and names the underlying mindset shift that ties them together: the default move from "I will tell you what to do" to "I will help you figure out what to do and clear the way for you to do it." This is the hinge Greenleaf's original essay (Module 1) turns on, and it's worth examining directly, because it's easy to intellectually agree with servant leadership while still directing by default under pressure.
1. Directing vs. serving as two different defaults¶
| Situation | Directing default | Serving default |
|---|---|---|
| Team member brings a problem | Give them the answer | Ask what they've already considered, then help them think it through |
| Someone makes a mistake | Tell them what to do differently | Ask what they think went wrong, then align on the fix together |
| A decision needs to be made | Decide it yourself and announce it | Gather input, clarify the criteria, decide last if you're the one who must decide |
| Something is blocking the team | Push through it yourself to keep things moving | Ask the team what's actually blocking them, then remove the specific obstacle |
| A new priority comes down | Reassign work top-down immediately | Explain the why, then let the team figure out how to reprioritize their own work |
Neither default is "always right." Under real time pressure or in a true emergency, directing is often correct — a servant leader still directs when the situation calls for it (Module 1 already ruled out the idea that servant leadership means never directing). The mindset shift isn't eliminating directing; it's noticing which default you reach for automatically, and deliberately choosing serving as the default when the situation allows for it, rather than directing purely out of habit or impatience.
2. Why the directing default is so sticky¶
Directing feels faster, feels more in control, and is what most people were taught leadership looks like from watching their own managers. Three specific pressures push leaders back toward directing even when they know better:
- Time pressure — serving takes longer in the moment (asking questions, waiting for someone to think it through) even though it's faster over time (the person can solve it themselves next time).
- Uncertainty about the outcome — directing feels safer because you control the result; serving means tolerating a result that might differ from what you'd have produced yourself.
- Identity — for many leaders, being the one with the answers is core to how they see their own value, and shifting to asking questions can feel (wrongly) like admitting inadequacy.
3. A simple in-the-moment check¶
Before responding to a problem someone brings you, a one-question check that catches the directing default in real time: "Am I about to answer this, or am I about to help them answer it?" If the honest answer is "I'm about to answer it," pause and ask instead: "What have you tried already?" or "What's your instinct here?" — genuinely serving defaults don't mean withholding your answer forever; they mean asking first, and only giving your answer if they're genuinely stuck or the situation doesn't allow the time for them to work it out (an emergency, a hard deadline, a decision above their authority).
4. A worked example¶
A team lead, Noor, gets a message from an engineer: "The staging environment is broken, what should I do?"
- Directing default: Noor immediately replies with the exact fix steps she knows from experience — quick, but the engineer learns nothing about diagnosing the next environment issue themselves, and the same question comes back next month.
- Serving default: Noor replies "What have you checked so far?" The engineer hasn't checked the deploy logs yet — Noor points them there ("start with the deploy logs from the last hour") without giving the answer outright. The engineer finds the actual cause, fixes it, and — critically — now knows the diagnostic pattern (check deploy logs first) for next time, which is exactly the kind of growth Greenleaf's original test (Module 1) asks whether a leader's service produces.
Noor still stepped in when it mattered (pointing at the deploy logs, since the engineer was stuck) rather than abandoning them to figure it out from zero — the mindset shift is about how she helped, not whether she helped at all.
How It Actually Works¶
The "directing default" is sticky because it is, structurally, a low-cognitive-load habit competing against a high-cognitive-load alternative. Directing draws on procedural memory and requires only retrieving an answer and stating it — fast, automatic, System 1 processing in Kahneman's framework. Serving (asking a clarifying question, resisting the urge to hand over a solution, tolerating the other person's slower path to the same place) requires actively inhibiting the automatic response and substituting a deliberate one — System 2 processing, which is metabolically and attentionally expensive and degrades fast under fatigue, time pressure, or stress. This is why leaders who are entirely capable of serving in a calm one-on-one revert to directing in a crisis: it isn't hypocrisy, it's the well-documented pattern of stress narrowing behavior toward whatever response requires the least cognitive resources to execute.
Why "the in-the-moment check" (pausing to ask which mode you're in) is the actual intervention, not a soft ritual. Because directing is the automatic default, the only reliable point of leverage is the brief window between the urge to direct and the act of directing — the same window targeted by the pause-name-choose sequence in Module 2. Once the directing response is underway (you've started talking, you've started explaining the answer), inhibiting it mid-stream is much harder than inhibiting it before it starts, because verbal production, once initiated, has its own momentum. This is why the check has to happen before responding, not as a self-correction partway through a sentence.
Why serving produces better decisions on non-trivial problems, not just better morale. Directing substitutes the leader's single mental model for the group's collective information — which is efficient only if the leader's model already contains everything relevant. On problems where the person closer to the work holds information the leader doesn't (which is most real problems, precisely because the leader is one level removed from the day-to-day detail), directing systematically discards that information before it's ever surfaced. This is the core insight behind the "wisdom of crowds" and distributed-cognition research: a single fast answer from the most senior person in the room is often less accurate than a slower process that aggregates several partial views, even when the senior person's individual judgment is strong.
Exercise¶
Over the next three days, each time someone brings you a problem or a question, pause before responding and ask yourself the one-question check: "Am I about to answer this, or help them answer it?" Track how many times your first instinct was to direct vs. serve. For at least one of those moments, deliberately choose the serving default even if directing would have been faster — ask what they've tried or what their instinct is before offering your own answer — and write 2-3 sentences on what happened and whether it changed the outcome.