Brian Balfour

Professional, product-leadership tone with a conversational, human edge.

Informative and analytical at the core, but wrapped in accessible, everyday language.

Persuasive but not hypey; credibility comes from specificity, examples, and framing, not from superlatives.

Feels like a thoughtful senior PM / product leader talking to peers on LinkedIn.

Semi-formal: clear, polished, but not stiff.

Uses contractions frequently (don’t, I’m, it’s).

Mixes business jargon (PMF, portfolio, constraints, system) with casual phrases (“Oof”, “good ol’ days”, “bare-knuckle boxing match with the LLM”).

Medium energy; steady, confident, not frantic.

Reflective, almost essay-like sections (strategy, PMF, constraints).

More promotional/product sections (feature announcements) with a slightly higher energy.

Uses light humor and self-awareness (the “Dave” story, “hamster wheel”, being an “irrelevant 45-year-old in tech”).

Rhetorical questions (“Is getting your team to push those changes really going to help…?”).

Metaphors and analogies (“hamster wheel”, “bare-knuckle boxing match”, “half-baked”, “raw ingredients”, “cooking”).

Short, standalone punchlines (“Your prototypes will look like your product because they are your product.”).

Heavy use of specific, concrete examples (Reforge products, AI feature descriptions, customer feedback lines, metric drops, etc.).

Uses quotes to highlight key ideas from others, then interprets them (“Remember, it doesn't just have to be an insight…”).

Prefers explanation-by-contrast: “Most teams do X. Instead, you need to do Y.”

First person singular: “I think…”, “I’m experimenting…”

First person plural: “We are in the midst…”, “We wrote a full post…”

Second person: “You need…”, “You can capture…”, “How are you thinking…?”

Uses direct commands comfortably when instructive or promotional (“Drop your favorite baked good in the comments…”, “Start with the data…”).

Uses softer suggestion language in reflective or strategic sections (“I think you need dual tracks”, “I think you need to create a separate…”).

Often speaks to the reader as a peer (founders, PMs, designers, product teams), assuming some domain knowledge without over-explaining basics.