Structure & Voice

Ship With Intent enforces a specific structure and voice across every piece of content. The rules aren't suggestions — they're tested constraints that determine whether a piece works or doesn't.

The Seven-Step Structure Arc

Every substantial post and video follows this arc:

1. Problem / Tension. Why does this matter right now? Framed specifically, not generically. The reader should feel the problem before they know what the piece is about.

2. Common Ground. Establish that the reader has been here. They've felt this tension, made this mistake, faced this trade-off. They're not alone — and you're not lecturing from above.

3. Socratic Layer. Ask the questions the reader is already asking before answering them. This is the critical step most content skips. If the reader is thinking "but what about X?" and you haven't addressed it, you've lost them. Surface the tension before resolving it.

4. Analogy. Make the abstract concrete. Analogies come before or alongside the conclusion, never after. After the conclusion, an analogy is decoration. Before it, an analogy is scaffolding that helps the insight land.

Analogies that work: systems that fail under specific conditions, everyday physical experiences, observable cause-and-effect. Analogies to avoid: sports (overused), military (wrong register), cooking (too gentle for this audience).

5. Answer / Insight / Conclusion. Let it land. Don't announce it. "So in conclusion..." kills the piece. The reader should arrive at the insight through the structure, not be told they've arrived.

6. Implication. What does this mean for how the reader acts or thinks going forward? The insight needs consequence — otherwise it's interesting but inert.

7. CTA. One call to action, specific, placed after the value is delivered. Not "subscribe" in the third paragraph. Not "follow me for more." A specific thing the reader can do next, earned by the value they just received.

The Hook Test

After reading only the hook — the first two paragraphs — would a smart, skeptical engineering leader keep going? If no, the hook failed. Rewrite it before touching anything else.

The hook creates genuine tension or curiosity. It doesn't summarize the piece. It doesn't start with the writer ("I've been thinking about..."). It starts with the reader's problem.

Peer-to-Peer Register

The voice writes to a respected peer. Not down to a student. Not up to an authority. The reader is someone with experience, judgment, and limited patience for ideas that don't earn their attention.

This register determines everything: word choice, sentence length, how much context to provide, when to be direct versus when to build. If you wouldn't say it on a phone call to a respected colleague, it doesn't belong in the piece.

What Kills the Voice

Specific patterns that get flagged in review:

Inspirational padding — "At the end of the day..." "It's all about..." "What really matters is..." These are filler that signals the writer doesn't have a point.
List-as-thinking-substitute — "Five tips for X" without an argument. Lists are structure, not substance.
Performed insight — "This one blew my mind..." "Game changer." If the insight is real, you don't need to announce that it's impressive.
Hedging — "I think maybe possibly..." "Could potentially..." Either commit to the point or cut it.
Generic leadership advice — Anything that could have been written by someone with Google access and no direct experience.

The Quality Checklist

Every piece is checked against specific criteria before publication:

Hook creates genuine tension or curiosity in first two paragraphs
Single, clear point (not "several things I've been thinking about")
At least one specific, grounded example (not a generic scenario)
At least one analogy, placed before or alongside the conclusion
Conclusion earned through the structure, not announced
No padding sentences that could be cut without losing meaning
The reader could summarize the main point in one sentence
Tone sounds like talking to a respected peer

A piece isn't ready when any of these fail. Multiple main points competing for the ending, an analogy that comes after the conclusion, a hook that starts with the writer instead of the reader's problem — these are structural issues, not polish issues.

Naming Rules

Five naming rules are enforced across all content:

The publication is Ship With Intent — never abbreviated, never lowercase "with"
The game is Poopborne — never "my game" or "the game"
The practice is Intent Engineering — never lowercase
No employer name anywhere in content (legal separation)
Thread names are capitalized as proper nouns