Skip to content
Writing Style Library

Candid

Names the uncomfortable truth directly - not harsh, but unwilling to pretend the hard thing is not there.

Candid

Section titled “Candid”

Candid tone is what you use when avoiding the truth would be a disservice to the reader. It is not brutal - it does not lead with the negative for its own sake. It is the tone of a trusted advisor who says “I need you to hear this” and then says it clearly, without burying it in hedges.

The difference between candid and blunt is care. Blunt does not consider how the truth lands. Candid delivers the truth in a way the reader can actually receive it - with context, with a path forward, and without contempt. Candid tone is often preceded by acknowledgment: “I know this is not what you wanted to hear, and here is why it matters anyway.”

Candid tone is particularly valuable in feedback contexts, in post-mortems, in situations where there is organizational pressure to soften or defer. Using it signals to the reader that you are not managing their feelings at the expense of the truth.

Markers

Section titled “Markers”
  • Names the hard thing directly and early, not buried in paragraph four
  • Explicit signaling: “I want to be direct about this” or “Here is the honest picture”
  • Acknowledgment before the hard truth: “I know this is not what you hoped for”
  • Path forward after the truth: “Here is what we can do”
  • Active voice for the difficult claims
  • No euphemisms for negative outcomes

When to use

Section titled “When to use”

Feedback conversations, post-mortems, honest status updates when the news is hard, coaching contexts, and situations where organizational pressure is pushing toward softening.

When not to use

Section titled “When not to use”

Formal diplomatic communication, legal writing, PR communication, and contexts where candor would be received as aggression.

Pairs well with

Section titled “Pairs well with”

pragmatic-architect, columnist, operator, matter-of-fact

Often confused with

Section titled “Often confused with”

matter-of-fact: Matter-of-fact simply states the truth without marking it. Candid explicitly frames its own honesty - “I want to be direct with you” - and then delivers the uncomfortable thing. Candid has an explicit commitment to truth-telling as part of the message. Matter-of-fact does not editorialize about the communication at all.

Instruction

Section titled “Instruction”
Write in a candid tone. Your reader deserves the honest picture, and you are going to give it
to them. Name the hard thing directly and early - do not bury it. Acknowledge the difficulty
before the truth: "I know this is not what you hoped for." Then say the thing. Provide the
path forward. No euphemisms for negative outcomes. Active voice for difficult claims. The
difference from blunt: you care how this lands, so you give context. But you do not hide the
truth to protect feelings.
Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Pragmatic Architect, Columnist, Operator, Matter of Fact

Avoid with

Section titled “Avoid with”

Reverent, Warm, Pastoral

Often confused with

Section titled “Often confused with”

Matter of Fact

Examples

Section titled “Examples”

Team,

I want to be direct about something: our daily standup is not delivering what it is supposed to deliver, and we need to change it.

Here is the honest picture. We have three engineers who join at 9:30pm their local time on most days - and when they cannot make it, they miss information that affects their work. We have engineers who post “same as yesterday” most Tuesdays because nothing has actually changed since Monday’s standup. We have blockers that get mentioned in the meeting and then disappear because nobody wrote them down. The standup takes 14 minutes on average and the signal-to-noise ratio is not good.

I know this is not news to some of you. I have been aware of it for a while and I should have said something sooner.

Here is what I think we should do: replace the synchronous standup with an async format for 30 days. Three questions, answered in Slack by 10am local time: what shipped, what is in progress today, what is blocked or at risk. Blocked items require a @mention. I read the channel each morning and make sure blocks get resolved the same day.

This does not fix everything. If people do not post consistently, the format breaks. If I do not read the channel attentively, blocked items will pile up. I am asking for your participation and holding myself accountable to the same standard.

The synchronous meeting I want to preserve is Thursday working sessions - real collaboration, not status.

I would rather try this and learn than continue a format that is not working. We will review at 30 days and make a permanent call together.

Any questions, come find me.

Appears in diff-pairs

Section titled “Appears in diff-pairs”