Operating with Clarity

The teams that move fastest at Systeric are not the smartest in the room. They are the clearest. Clarity is not a gift you are born with — it is a practice, and it rests on two habits: saying exactly what you mean, and asking why until the answer holds up. Everything below is how we do both here.

This is adapted for Systeric from Operating With Clarity; read the original for the full argument.

Two axes, every conversation

Whenever we talk — a weekly call, a Define session, a PR thread — two things are quietly being tested:

• How precise is the language? Are you stating a position, or hedging so you can’t be wrong?
• How deep is the questioning? Are you accepting the first plausible answer, or pushing until it actually explains the thing?

Most fuzzy outcomes trace back to a soft answer on one of these axes. A vague problem statement produces a vague solution. A “directionally yes” that nobody pinned down produces three weeks of building the wrong thing. Clarity is just refusing to let either axis go slack.

Ask why until the answer changes category

The famous version of this is the battery-pack question: everyone “knew” cells cost ~$600/kWh, until someone asked what the raw materials actually cost — about $80. The price wasn’t a law of physics; it was an inherited abstraction the room had stopped questioning.

We do the same thing in Discover: ask “why” until the answer stops describing this situation and starts describing how the system works. “Support tickets are up” is an event. “We moved the settings page without updating nav” is a contributing factor. “There’s no pre-release checklist for navigation changes” is the system. Each “why” should change the category of the answer, not just add detail.

The tell that you’ve hit something real: the fix feels smaller and more uncomfortable than you expected, and it points at a decision you made. Inherited abstractions feel safe because the room accepted them first. First-principles answers feel exposed because they’re yours — and they survive scrutiny better.

The one-sentence test

If you can’t state your position in one sentence, you don’t have a position yet — you have a vibe.

Before you bring something to a call, a Define doc, or a roadmap proposal, write the one sentence:

• Bad: “We should probably look at improving the onboarding experience, there are a few things going on there.”
• Good: “First-time users drop off at the OTP screen because the code takes 40 seconds to arrive; we should pre-warm the SMS provider.”

The first isn’t a position, it’s a gesture at a topic. The second can be agreed with, argued against, or tested. A position you can’t compress is a position you haven’t finished thinking.

This is why our problem statements must read cold — someone outside the work understands them without a follow-up question — and why quarterly proposals arrive as a point of view, not an open question.

No weasel words

Weasel words feel polite, but they are expensive: they push the cost of figuring out what you meant onto everyone downstream. “We might want to consider possibly revisiting this at some point” commits to nothing and clarifies nothing.

The discipline: say the thing, then defend it.

• “Directionally, this seems better” → “This is better, because checkout abandonment drops when we remove the address step. I could be wrong if returning users rely on it — let’s check.”
• “It’s kind of slow sometimes” → “P95 latency is 2.1s on the orders endpoint; our budget is 500ms.”
• “People seem to want this” → “Four of the last ten support tickets asked for it.”

Stating a position plainly isn’t arrogance — it’s a gift to the room, because now there’s something concrete to sharpen. This is the same instinct behind our writing: no weasel words, be direct and specific.

”I don’t know yet” beats hedging

Precision is not false confidence. The clearest thing you can say is often “I don’t know yet — here’s how I’ll find out.” That is a definite statement: it names the gap and the next step.

What it is not is soft cover. “Directionally” and “sort of” and “I think maybe” are hedges that let you avoid being pinned. “I don’t know the cause yet; I’m pulling the Metabase query this afternoon” is clarity. Genuine, named uncertainty is welcome at Systeric. Vagueness dressed up as humility is not.

Questions that open, not score

Depth of questioning only works if the questions are real. In a Define session or a leadership review, the job of a question is to find what’s missing or wrong, not to win a point.

• A point-scoring question protects the asker: “Did you even consider X?”
• A clarifying question protects the work: “What happens to in-flight orders when this deploys?”

The second makes the thing better and is safe to answer honestly. Ask the kind that surfaces gaps, and answer every question as if the asker is trying to help — because in a healthy room, they are.

Why this compounds

When a team knows that vagueness won’t survive — that someone will ask for the one sentence, the number, the actual cause — people sharpen their work before they bring it. The standard pulls quality forward. The opposite also compounds: once hedging is tolerated, everyone hedges, and nobody can tell what anyone actually believes. Clarity is a culture you set one conversation at a time.

Before you speak or write — a checklist

• Can I say my position in one sentence? If not, I’m not ready.
• Did I replace every weasel word with the actual claim and the reason?
• For any uncertainty, did I say “I don’t know yet” plus the next step, rather than hedging?
• Have I asked why enough times that my answer describes the system, not just the symptom?
• Is my question trying to improve the work, or protect me?

Next: The Team