Skip to content
Writing Style Library

Skeptical

Measured doubt that refuses to commit ahead of the evidence and asks what would actually change the picture.

Skeptical

Section titled “Skeptical”

Skeptical tone is the register of measured doubt. It is not contrarian, and it is not dismissive. It is the tone of a reader who has noticed that the evidence does not yet support the claim and is unwilling to pretend otherwise. The skeptical writer asks “what would change my mind?” rather than treating the question as already settled in either direction.

The defining move of skeptical tone is naming what is NOT yet established. Where candid states uncomfortable truths and matter-of-fact states what is true, skeptical states what remains unproven, what the data does not actually support, and what we would need to see before committing. It is comfortable with sentences like “the evidence is thin here” and “this could be true, but we have not shown it.”

Skeptical tone is essential in research summaries, vendor evaluations, post-mortems where the root cause is contested, and any context where premature certainty would be a more serious error than acknowledged uncertainty. It signals epistemic humility without performing helplessness. The writer is engaged with the question, not refusing to engage.

Markers

Section titled “Markers”
  • Explicit gaps named: “we do not yet have evidence for X” or “this has not been established”
  • Falsification framing: “what would we need to see to believe this?”
  • Hedges tied to specific evidence, not generic softening: “given only N=12, this is suggestive at best”
  • Distinction between absence of evidence and evidence of absence
  • Counter-hypotheses surfaced rather than dismissed
  • Conditional claims: “if X holds, then Y - but we have not verified X”

When to use

Section titled “When to use”

Research summaries, vendor evaluations before commitment, contested post-mortems, strategic memos resting on unverified assumptions, and peer review contexts where the writer’s job is to test the claim rather than transmit it.

When not to use

Section titled “When not to use”

Pastoral or devotional writing, celebratory updates, operational instructions where the reader needs to act, persuasion contexts where measured doubt reads as weakness, and crisis communication where the audience needs direction.

Pairs well with

Section titled “Pairs well with”

researcher, pragmatic-architect, candid

Often confused with

Section titled “Often confused with”

candid: Candid states a truth the writer has identified and believes - it just refuses to soften it. Skeptical states that the truth has NOT yet been identified, that the evidence is incomplete, that the claim is unproven. Candid is the tone of conviction delivered honestly. Skeptical is the tone of conviction withheld until the evidence arrives.

Instruction

Section titled “Instruction”
Write in a skeptical tone. You are not dismissing the claim, and you are not endorsing it. You
are noticing where the evidence is thin and saying so. Name the specific gap: what has not been
shown, what assumption has not been verified, what alternative explanation has not been ruled
out. Use the question "what would change my mind?" as a structural device. Tie hedges to
specific evidence rather than generic softening. Treat counter-hypotheses as worth surfacing,
not as threats to swat down. The reader should finish with a clear picture of what is and is
not established.
Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Researcher, Pragmatic Architect, Candid

Avoid with

Section titled “Avoid with”

Pastoral, Reverent, Celebratory

Often confused with

Section titled “Often confused with”

Candid

Examples

Section titled “Examples”

The case for switching to async is real. India is at 3.2/5 attendance because 9:30pm is 9:30pm, and no amount of culture work fixes that. But before we commit, I want to be honest about what the 30-day trial can and cannot tell us.

What is established: the current standup hurts our India engineers. The 14-minute meeting with 4 minutes of signal is documented. Status not persisting is documented. These are the things I am sure of.

What is not established: that async standups will fix what we think they will fix. Thirty days is two sprint cycles. In thirty days we will know whether people post their updates and whether the Thursday session feels useful. We will not know whether async standups produce better coordination, fewer dropped handoffs, or higher India retention. Those are the outcomes we actually care about, and they take a quarter or two to show up.

I would also push on what “trial success” means. If thirty days in we have mixed results - say, 80% of engineers posting consistently, but two missed handoffs and one India engineer saying they feel less connected - what do we conclude? My worry is that we will read that result through whatever lens we already hold. The people who wanted async will see the 80%. The people who wanted sync will see the handoffs.

I am not arguing against the change. I am arguing for naming, before we start, what evidence would actually move us. What posting rate is the floor? What does “the Thursday session works” mean concretely - decisions made, blockers cleared, or just attendance? And what would make us roll it back?

If we cannot answer those questions now, the trial is mostly a vote of preferences with a calendar attached to it. Let us decide what we are measuring before we measure it.