Communication and discretion

"Hi Adaeze, just wanted to check in about the MedSupply thing — let me know your thoughts whenever you get a chance!" This message will sit unanswered for three days. Not because Adaeze doesn't care, but because it asks nothing specific enough to answer quickly. It hands her a vague feeling of obligation instead of a decision she can make in the fifteen seconds she has between clients.

A message that asks "what do you think?" gets a conversation. A message that asks "A or B?" gets a decision.

The shape of a message built for a busy person

Most of the people you'll message in this role are genuinely busy, reading on a phone, between things. A message built for that reader has three parts, in this order:

1. Context, in one line. Just enough that the reader doesn't have to reconstruct the situation from memory. Not the whole backstory — the one fact that makes the rest make sense.
2. The specific decision needed, named as a question with a shape. Not "what do you think" — "should I confirm the 5% or push back once more?" A question with a small number of named answers is answerable in one tap. An open question requires composing a reply, which is exactly the extra effort that makes a message sit for three days.
3. What happens if there's no reply by when. A default, stated plainly, so silence doesn't become its own kind of decision by accident. "If I don't hear back by Thursday, I'll confirm the 5% as the safer option" turns an unanswered message from a stuck task into a plan that proceeds either way.

Worked example: the same message, rebuilt

Notice the second version does more work up front — it costs you a little more time to write than the vague check-in did. That trade is almost always worth making: a well-built message takes an extra thirty seconds to compose and can save days of back-and-forth, or worse, a decision made too late because nobody actually decided anything.

When there genuinely isn't a small set of options yet

Not every message can be reduced to A-or-B — sometimes you genuinely need Adaeze's open judgement on something with no obvious shortlist. In that case, still frame it as a decision rather than a conversation: state clearly what you need from her ("I need your read on which of these two directions to take this in") rather than opening with "thoughts?" and hoping the question sharpens itself in her reply.

The same message — "confirming our call for Thursday" — reads as perfectly normal to one recipient and slightly abrupt to another, depending entirely on who they are and what they're used to. Tone isn't one setting you get right once. It's a dial you adjust for the specific person reading, every time, the same way lesson 5.5's escalation ladder adjusted for the relationship rather than repeating one fixed script.

Tone is not about being more or less polite. It's about matching the reader's expectations closely enough that the message doesn't have to work hard to be understood.

Three dials worth adjusting deliberately

1. Formality, by seniority and relationship. A first message to a prospective referral partner earns a fuller, more formal register than a fifth message to a supplier you've worked with for a year. Watch what the other person actually does — mirroring their own register is usually safer than guessing a fixed rule.
2. Directness, by cultural context. Some business cultures expect the ask stated plainly in the first line; others expect a warmer opening before the actual point. Neither is more correct — the mismatch is what creates friction, not either style on its own. When you don't know a contact's preference, a brief warm opening followed by a clear, direct ask works reasonably across most contexts without reading as cold in either direction.
3. Response-time expectations, by time zone. A message sent to London at 6pm Lagos time lands in the recipient's early evening too, since Lagos and London share very close clocks most of the year — but the same message sent to New York at 6pm Lagos time lands around lunchtime there, hours before their working day even starts to wind down. Naming the time difference plainly — "I know it's still morning for you" — shows the awareness without needing to get the exact math right in the reader's head.

Worked example: the same request, two contexts

Both messages do the same job — confirm a time, invite a reschedule if needed. The difference in register isn't decoration; it's calibrated to the relationship's actual history and what each reader will find normal, which is the entire point of adjusting tone at all.

When you genuinely don't know someone's preference yet

Default to slightly more formal than feels necessary, and slightly warmer than feels efficient. It is far easier to loosen up in a second message once someone's own style becomes clear than to walk back an opening message that landed as too casual for a relationship that hadn't been established yet.

A client's friend emails asking if Adaeze can fit her in for a same-day session — the diary is full, and even if it weren't, taking on new clients through informal referrals outside the proper intake process isn't something Adaeze wants to make a habit of. "No" is the honest answer. "No" by itself, unadorned, is also the fastest way to make someone feel dismissed rather than declined.

A bare "no" closes a door. A well-built "no" closes the wrong door and points at the right one.

Three shapes a decline can take, and when each fits

1. No, with the reason, briefly. When the answer is genuinely final. State it plainly, give one honest sentence of reason — not a defensive paragraph — and stop. Over-explaining a firm no often reads as an invitation to negotiate it.
2. Not yet, with a real condition. When the answer could become yes under a different circumstance. Name that circumstance specifically — "not this week, since the diary's full, but there's a cancellation list I can add you to" — rather than a vague "maybe later" that quietly means never and everyone involved knows it.
3. Not this, but this instead. When you can't do what was asked but can do something smaller and genuinely useful. Offering the smaller thing turns a decline into a piece of help, and it's frequently what the person actually needed anyway.

Worked example: the same request, three honest responses

Notice none of the three is a "yes" — the diary genuinely is full in every version. What changes is whether there's something real and specific to offer instead of a flat door closing, and being honest about which of the three situations actually applies rather than defaulting to whichever sounds kindest.

Never manufacture false hope to soften the moment

The one failure mode worse than a blunt no is a "not yet" that isn't actually true — offering a cancellation list that doesn't really move, or a vague "check back soon" with no real chance attached. It feels kinder in the moment and corrodes trust the moment the person realises the hope was never real. Say the harder true thing rather than the softer false one.

A client asks to reschedule a session — an easy call, made a hundred times, well inside what you're trusted to decide alone. A client asks to pause therapy entirely and wants Adaeze's read on whether that's wise — not your call at all, and pretending otherwise oversteps in a way that could genuinely damage the relationship. Most of the requests that land on you sit somewhere between these two, and the skill this lesson teaches is sorting them fast and correctly.

Escalating too much makes you a bottleneck. Escalating too little makes you a liability. The line between them is a judgement you can actually train.

Three tiers, and a rough test for each

The test that sorts most borderline cases

When a request doesn't obviously fit one tier, ask: if I get this wrong, can it be undone easily, and does getting it wrong cost time or something bigger than time? A wrong guess on a reschedule costs an email to fix. A wrong guess on anything touching a client's care, money beyond routine amounts, or the practice's legal standing costs far more, and some of that cost can't be undone at all. Reversibility and stakes together, not either alone, are what should decide the tier.

Worked example: three real requests, sorted

Escalating well means bringing a recommendation, not just a problem

"This came up, what do you want to do?" is a valid escalation, but "this came up, here's what I'd recommend and why" respects the time of the person you're escalating to, and it's how you build toward being trusted with more over time — the same principle from module 4's handover file, applied to real-time decisions rather than a document.

By this point in the role, you know things about Adaeze's practice that almost nobody else does — which clients are struggling to pay, which referral relationships are shaky, what she said in frustration about a difficult supplier call. None of that is yours to share, discuss, or even hint at, regardless of who's asking or how casually the conversation seems to invite it.

Being trusted with information is not the same as being free to use it. Discretion is what keeps those two things separate, every time, without exception.

The categories worth distinguishing

Not all client-adjacent information carries the same weight, but the safe default treats most of it as equally off-limits in casual conversation. Three categories are worth naming specifically, because they come up differently:

1. What clients tell Adaeze, or what you overhear about them. Covered fully by module 7's confidentiality line — never repeated, never hinted at, regardless of the asker.
2. What Adaeze tells you about her own practice, frustrations, or decisions. A different kind of trust — she's not your client, but she is confiding in you as someone she relies on. Repeating her private frustration about a difficult client, even to someone who seems sympathetic, damages her trust in you just as surely as a confidentiality breach would, even though it isn't clinical information.
3. What you happen to know from being inside the business — finances, a shaky relationship with a referral partner, a mistake that hasn't been disclosed yet. Business-sensitive information that could cause real harm if it reached the wrong person, even unintentionally, through a conversation that felt harmless at the time.

The specific moments discretion actually gets tested

Discretion rarely fails in an obvious, dramatic moment — it fails in small, casual ones. A friend asks "so how's it going working for a therapist, must be interesting stuff you hear." A colleague at another gig makes a joke that invites a story in return. Someone flatters you into feeling like sharing a detail would make you seem more important or in-the-know. Each of these is a low-stakes-feeling social moment where the discipline actually gets tested — not a dramatic confrontation where the stakes are obvious.

Practise the redirect so it's ready, not improvised under pressure

The moment this gets tested is rarely convenient — a casual conversation, unprompted, no time to think carefully about the right response. Having a warm, natural-sounding redirect ready in advance, like the example above, is what stops a well-intentioned person from accidentally saying more than they meant to simply because they were caught off guard.