Skip to content
Writing Style Library

Matter of Fact

States what is true without editorial coloring - neither cold nor warm, just accurate.

Matter of Fact

Section titled “Matter of Fact”

Matter-of-fact is the tone of the briefing that gets the decision made. It does not editorialize. It does not boost or undermine. It presents the situation as it is, trusting the reader to have the appropriate response. This tone is not cold - cold is a deliberate withdrawal of warmth. Matter-of-fact simply has no agenda about how the reader should feel.

Where warm tone says “this is a really exciting opportunity,” matter-of-fact says “this is an opportunity.” Where candid tone says “I will be honest with you - this is harder than it looks,” matter-of-fact says “this is harder than it looks” (without marking itself as candid). The difference is the absence of meta-commentary on the communication itself.

Matter-of-fact tone works best when the content is serious or technical enough that tonal performance would feel inappropriate, or when the writer wants to convey that they are giving a straight account with no spin.

Markers

Section titled “Markers”
  • Declarative sentences without hedging
  • No intensifiers: not “very important” but “important”
  • No mood markers: not “unfortunately” or “excitingly” - just the fact
  • Active voice stating what is
  • No meta-commentary on the communication: not “I want to be clear” but just the clear statement
  • Neutral sentence endings - statements close, not questions or emphatics

When to use

Section titled “When to use”

Status updates, incident reports, technical documentation, briefings, and any context where editorializing would undermine credibility.

When not to use

Section titled “When not to use”

Condolences, celebrations, persuasion, emotional support, and coaching contexts where tone aids retention and engagement.

Pairs well with

Section titled “Pairs well with”

pragmatic-architect, operator, candid

Often confused with

Section titled “Often confused with”

candid: Candid names the meta-communication explicitly - “I want to be direct with you” - and then says the hard thing. Matter-of-fact simply states the truth without marking it. Candid has an explicit frame; matter-of-fact has no frame at all.

Instruction

Section titled “Instruction”
Write in a matter-of-fact tone. State what is true without editorial coloring - no
intensifiers, no mood markers, no meta-commentary on the communication itself. Do not say
"I want to be clear" - just be clear. Do not say "unfortunately" - just state the consequence.
No "very," no "really," no "exciting." Declarative sentences. Active voice. Trust the reader
to have the appropriate response without your coaching.
Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Pragmatic Architect, Operator, Candid

Avoid with

Section titled “Avoid with”

Warm, Encouraging, Reverent

Often confused with

Section titled “Often confused with”

Candid

Examples

Section titled “Examples”

Proposal: Transition to Async-First Standup Format

The team currently holds a daily synchronous standup at 9am Pacific. Attendance has averaged 8 of 11 engineers over the past quarter. The three engineers who miss most frequently are in the UTC+5 timezone, where 9am Pacific is 9:30pm local. The meeting runs an average of 14 minutes.

The proposal is to replace the synchronous standup with a structured async update posted to #team-standup by 10am each engineer’s local time. The format uses three fields: what shipped in the last 24 hours, what is in progress today, and what is blocked or at risk. Blocked items must include a @mention of the person who can resolve the block.

The on-call engineer reads the channel by 9am Pacific each day and responds to blocked items within 30 minutes during business hours.

The synchronous meeting would be replaced with a weekly 60-minute working session on Thursdays. That session is not a status meeting - it is reserved for topics that require real-time discussion.

Expected outcomes:

  • All engineers participate on a schedule that fits their timezone
  • Blockers reach the relevant person with a direct mention rather than relying on meeting attendance
  • Status information is persistent and searchable rather than spoken and lost

Risks:

  • Engineers who do not read the channel regularly will miss updates
  • The format requires consistent participation to be useful - if three people stop posting, the value drops for everyone

Next step: Trial period of 30 days starting the week of May 19. Review at 30 days with a team survey and a look at blocker resolution time before and after.