A brand that asksbetter questions.

It is

A place to work through ideas in public — because writing is how I figure out what I actually believe.

Lens 01

The problem space

There's a point where every team shifts from asking "what's actually happening?" to "how do we fix it?" That shift is almost always premature. And almost never noticed. Knowing where you are on the problem-to-solution spectrum changes everything.

Lens 02

Systems thinking

Every black box is a set of choices someone made for conditions that no longer apply. Systems thinking is the practice of seeing structure under behavior. Incentives create behaviors. Behaviors reinforce structures. Structures outlast the rationale that created them.

Lens 03

Tracking results

Most teams define success after the thing is built — and the definition lands on whatever the thing happens to be doing. That's not measurement. It's retroactive justification. Very few teams can finish the sentence: "we'll know this worked when…"

Ask, don't assert

Lead with questions. The headline is often a question. Ideas create space for thinking, not conclusions to download. If a sentence sounds like a lecture, rewrite it as a provocation.

Not: "Here's why X matters." — Yes: "What would it mean if X wasn't true?"

Short over long

Card bodies are 1–2 sentences. Let the writing do the work — the UI and the setup stay short. If you need three sentences to make the point, the point isn't clear yet.

Not: a paragraph that builds to something. Yes: the thing, with the paragraph behind a click.

Warm but direct

No hedging. If it's true, say it. The warmth comes from the quality of thinking, not the softness of the phrasing. "Most teams" is more honest than "some teams might consider."

Not: "It may be worth exploring whether…" — Yes: "Most teams skip this entirely and pay for it later."

Open in another domain

Ground the abstract idea in a concrete history before naming it: the printing press, photography's effect on painters, FMEA in the military, the jury that deliberates only after all evidence is in.

Seen in: collapsing moats, failure modes, problem definition.

Draw the distinction

The core move is separating two things that get conflated, then marking the gap plainly. "Those are not the same thing." The essay lives in that gap.

Symptom vs. problem. Activity vs. outcome. Survival vs. sound design.

Land it on one line

After a paragraph builds, drop a single short line on its own. The white space carries the emphasis, not bold or punctuation.

"Sign-ups don't recover." / "It got assumed."

Use

• problem space / solution space
• misframed / framing
• feedback loop / system
• assumption / unstated assumption
• teams, practitioners, builders
• working through, navigating, exploring
• notice, see, recognize
• precisely, specifically
• almost always, most teams
• the thing
• failure mode (the specific way it breaks)
• table stakes
• leading / lagging indicators
• vanity metric
• the tell
• name the pattern

Avoid

• leverage, synergy, ecosystem
• self-described guru, oracle, visionary
• actionable, scalable, impactful
• in today's [anything]
• disruptive, innovative, game-changing
• journey, transformation, pivot
• holistic, robust, seamless
• go-to resource, one-stop
• best practices (without critique)
• share my perspective on

Message 01

Problem framing is the work that precedes the work

Teams who skip problem definition end up building the right solution to the wrong problem. The diagnostic period isn't delay — it's the highest-leverage part of any project.

Message 02

Every organization is a system with invisible feedback loops

Incentives create behaviors. Behaviors reinforce structures. If the same problem keeps reappearing in a new hat, it's not a people problem — it's a structure problem.

Message 03

You can't measure what you define after the fact

Most teams define success to match what they built. Real measurement is decided before building. "We'll know this worked when…" is a sentence that must be completable before the sprint starts.