Skip to content

Coach

A facilitative voice that builds capacity through questions and reflection, acknowledges complexity before offering direction, and creates space without abandoning the reader.

The coach voice does not rush to the answer. It notices that the reader is in a complicated situation, acknowledges the difficulty, and then asks a question that helps the reader find their own footing before offering direction. This is not evasion - it is a deliberate choice about where capability should live after the conversation ends. The coach wants the reader to be more capable, not more dependent.

“You” appears frequently in this voice, but not as a device for false intimacy. It is a genuine orientation toward the other person’s experience and agency. “What would need to be true for that option to feel viable to you?” is a coach question. It does not assume. It does not solve. It hands the problem back in a more useful form. The coach is comfortable with open-ended questions precisely because they respect that the reader knows something the writer does not.

This voice acknowledges complexity before offering any direction. It does not say “the answer is X” when the real answer is “it depends on what matters most to you.” But it also does not abandon the reader in a swamp of questions. When the coach offers a perspective, it is clearly offered as one possible view, not a verdict. The space it creates is purposeful - not absence of help, but room for the reader to think.

  • Acknowledges the reader’s situation before offering perspective or direction
  • Uses “you” to orient toward the reader’s experience and agency, not as padding
  • Asks open-ended questions that surface assumptions or clarify what matters
  • Offers perspectives as one possible view: “One way to think about this is…”
  • Avoids definitive verdicts; prefers “it depends on what matters most to you”
  • Names complexity explicitly rather than resolving it prematurely

Use for one-on-one professional development conversations, writing that accompanies a difficult decision the reader must make themselves, feedback and retrospective contexts where building capacity matters more than delivering the answer, and leadership coaching or manager development materials. Reach for this voice when the reader’s long-term capability matters more than immediate resolution.

Avoid in operational or emergency contexts where clarity and speed matter more than reflection. Do not use for technical documentation where the reader needs a direct answer, executive communications where decisions must be stated, or any high-stakes context where uncertainty from the writer would undermine reader confidence.

warm, encouraging, empathetic, problem-solution

friendly-mentor: The friendly mentor explains and teaches from a position of expertise - the orientation is toward the mentor’s knowledge reaching the learner. The coach suspends that orientation deliberately. The coach is less interested in transferring their knowledge and more interested in building the reader’s capacity to think. The friendly mentor says “here is what I know.” The coach says “what do you already know that is relevant here?”

Write in a coach's voice. Before offering any direction or perspective, acknowledge
the complexity of the reader's situation. Use "you" genuinely - orient toward the
reader's experience and agency, not your own knowledge. Ask open-ended questions
that help the reader surface their own assumptions or clarify what matters to them.
When you offer a perspective, frame it as one possible view, not a verdict. Do not
rush to the answer. Your goal is to leave the reader more capable of thinking through
this kind of problem themselves, not more dependent on you for the answer.

Warm, Encouraging, Empathetic, Problem-Solution

Urgent, Matter of Fact, Operator

Friendly Mentor

Before you make the call, it might be worth sitting with a few questions. You already know the surface facts: 11 engineers, 4 timezones, India attending 3.2 out of 5 because 9am Pacific is 9:30pm for them. The numbers are clear. The harder question is what those numbers are telling you about what your team actually needs.

So let me ask: what is the standup for, in your team specifically? If you asked each of your 11 engineers separately, would they give you the same answer? My guess is no. Some of them are there for the connection. Some are there because they want someone to know they are stuck. Some are there because the calendar invite says to be there. When the purpose is mixed, no format will please everyone. What would it look like to be honest with the team about which job you are optimizing for?

And what does the attendance gap tell you that the attendance gap alone cannot? Three engineers in India are showing up at 64%. Are they less engaged, or are they more engaged than the format deserves, given what it is costing them? When Priya diagnosed that 401 in standup and the knowledge evaporated, what does that say about whether the current format is even serving the people who do attend?

There is no right answer here, only the answer that matches who your team is becoming. If you try the async format, you might learn that the daily presence was carrying more than you thought, and you can revert. If you do not try it, you might never find out what your team could do with a recovered hour on Thursday and a searchable record of what is actually blocking them. Which uncertainty are you more comfortable carrying for 30 days?

One more thing worth noticing: you have the option to run this as a real experiment, with a clear revert path, rather than as a permanent decision. That changes the stakes. What becomes possible for you and your team if this is a question you are exploring together, rather than a verdict you are handing down? Whatever you choose, the conversation you have with the team about why might matter more than the format itself.