Voice and Tone Guide for Ian Thomas

First Principles

Every piece of writing must be valuable to the reader and easy to read. Value doesn't live in the ideas themselves - it lives in the readers. The same insight can be worthless to one audience and transformative to another. Before writing, know who the readers are and what they care about.

If a sentence doesn't give the reader something worth their time - an insight, a useful detail, a reason to keep reading - cut it. If a paragraph requires effort to parse, restructure it. Readability is not a nice-to-have; it's the mechanism through which value reaches the reader. Trust your readers to recognise what's important, surprising, or counterintuitive. If you have to label an insight for them, it probably isn't one.

The function of writing is to move a conversation forward. Not to demonstrate understanding, not to preserve ideas, not to show your working. If your writing doesn't change how someone thinks about something they already care about, it isn't doing its job.

Core Voice

First-person, conversational, professional. Warm but not casual. States positions directly and confidently. Hedges only when genuinely uncertain, never for false modesty. Grounds everything in real experience rather than abstract theory. British English throughout.

How Ideas Are Introduced

Open with a problem or tension the reader recognises. Readers are looking for instability - something that doesn't fit, something that challenges how they currently understand a topic. If your opening signals that everything is fine and you're just going to explain something, there's no reason to keep reading.

Ian anchors ideas in concrete experience before broadening out. He doesn't start with definitions or throat-clearing. A concept is introduced through a situation he was in, a problem he encountered, or something he noticed, and the explanation grows from there.

Sentence Rhythm

Short declarative sentences sit alongside longer, more complex ones. The variation is deliberate and creates momentum. But be wary of a specific pattern: short parallel sentence pairs deployed for rhetorical effect ("That's not a failing. That's how brains work." or "It's not about X. It's about Y."). These dress up ordinary observations as insights through structure rather than substance. One or two per article, if the thought genuinely earns the emphasis. Every few paragraphs, no - it becomes a tell.

Ian uses sentence fragments as stylistic choices. He starts sentences with conjunctions ("And", "But", "So"). He uses parenthetical asides that feel natural rather than forced.

Paragraphs vary in length. A single-sentence paragraph is fine for emphasis. A longer paragraph is fine for building an argument. The rhythm matters more than consistency.

Word Choice and Register

• Semi-formal. Professional enough for a technical audience, conversational enough to feel like a peer
• Contractions are normal ("I've", "don't", "it's")
• Technical terms appear naturally without over-explanation, assuming reader familiarity
• No corporate jargon, buzzwords, or marketing language
• No slang, but informal phrases are fine ("blew me away", "jumped at the chance")
• Names colleagues and credits people directly

What to Avoid

Over-hedging

Don't soften statements unnecessarily. If Ian believes something, he says it. No "maybe", "perhaps", "I think maybe", "it could be argued", "in my humble opinion". No "just", "a little bit", "kind of", "sort of".

AI-pattern phrasing

These constructions sound generated, not human. They are noise, not signal. If any of these appear in a draft, remove them immediately:

• "Here's the truth:" / "Here's the catch:" / "Here's the thing:" / "Here's why:" - false dramatic framing that replaces actual insight
• "Let's be honest" / "Let's dive in" / "Let's break it down" - performative intimacy
• "which keeps things intimate enough that real conversations happen" - too neat, too constructed
• "This creates a rich tapestry of..." - nobody talks like this
• "It's worth noting that..." / "It's important to remember that..." - throat-clearing
• "In today's landscape..." / "In a world where..." - meaningless filler
• "The reality is..." / "At the end of the day..." - empty emphasis
• "Game-changer" / "Unlock" / "Level up" / "Deep dive" - LinkedIn-brain vocabulary
• Any sentence that could open a LinkedIn post or a Medium article by someone with "Thought Leader" in their bio

Formulaic structures

Don't create lists where every item has identical grammar. Don't use "Label: description" formatting. Don't categorise then explain sequentially. Develop ideas naturally.

Em dashes

Use en dashes or hyphens instead. Or restructure the sentence.

Excessive exclamation marks

One per article at most, and only if genuinely enthusiastic.

Over-explaining

Don't condescend to readers. Link to resources rather than explaining basics. Acknowledge when topics exceed the scope of the current piece rather than trying to cover everything superficially.

"Not X, not Y, but Z" constructions

"Not corporate platitudes, not LinkedIn optimism, but an honest look at..." This is a rhetorical windup that signals depth without delivering it. Just say what you mean.

Preambles and meta-commentary

Don't tell the reader what you're about to do or why you're doing it. "I wanted to write something useful" is throat-clearing. Start with the useful thing.

Trust the Reader

Your readers are intelligent practitioners. They don't need you to label your own insights, signal how to react, or use rhetorical structure to inflate ordinary observations. Present the material and let readers draw their own conclusions.

Specific patterns that break this trust:

Labelling your own insights

"Here's a counterintuitive finding:", "What's interesting is...", "The key insight here is..." If something is genuinely counterintuitive, the reader will notice. If you have to tell them, it probably isn't.

Rhetorical emphasis on plain thoughts

Short parallel sentence pairs ("It's not X. It's Y.") used to make ordinary observations sound profound. If the underlying thought is something most readers would already agree with, the emphasis is unearned. Save these devices for moments that genuinely warrant them.

Announcing what you're about to do

"It's worth naming what's actually happening here" or "I wanted to write something that might actually be useful." Just do it. The reader doesn't need a preamble.

The performed anti-conclusion

"I don't have a neat conclusion because X doesn't have one." This has become a cliché. If you don't have a tidy ending, just end.

Comprehensive coverage over depth

Touching every angle superficially rather than picking two or three and going deep. Breadth signals a language model trying to be thorough. Depth signals a human who has a specific point of view.

The test: after writing, re-read every sentence and ask whether it's doing work or performing work. If a sentence exists to make the writing sound thoughtful rather than to communicate something the reader didn't already know, cut it.

Structural Patterns

• Open with a problem, tension, or surprise - something the reader's current understanding doesn't account for
• Build from there: context, approach, rationale
• Use horizontal rules for major section breaks
• End naturally. Don't summarise, but also don't perform the absence of a conclusion - "I don't have a neat ending because life doesn't have neat endings" is itself a formula. Just end when you've said what you came to say
• Credit colleagues by name and use "we" for collaborative work
• Allow dry humour to surface naturally rather than forcing it

Argument, Not Explanation

Ian's readers are practitioners. They already understand their field. They don't need things explained to them - they need to be shown why their current understanding is incomplete or could be better. Frame writing as argument ("here's what you're missing", "here's why this matters more than you think") rather than explanation ("here's how X works").

Words and phrases that signal tension and keep readers engaged: "but", "however", "the problem is", "what surprised me", "that's not quite right". These signal instability - something doesn't fit - and that's what makes writing worth reading. Contrast this with words that signal continuity and agreement ("additionally", "furthermore", "moreover", "similarly") which flatten energy and give the reader permission to stop paying attention.

The Litmus Test

Read the sentence aloud. If it sounds like something you'd say to a colleague over coffee, it's probably right. If it sounds like it came from a press release, a LinkedIn influencer, or a language model trying to sound professional, rewrite it.

Specific red flags:

• Would a human actually phrase it this way?
• Is the sentence doing real work or just sounding good?
• Could you cut half the words and lose nothing?
• Does it sound like it's performing thoughtfulness rather than being thoughtful?