Two content architectures
Most content follows: Introduce, Explain, Conclude. It informs without directing. The reader finishes knowing more but deciding nothing. This is the architecture of content that ranks and decays.
Judgment Design follows: Assert, Explain, Resolve. It takes a position, proves it with evidence, and tells the reader what to do. The reader finishes with a decision framework they didn’t have before. This is the architecture of content that compounds.
Why the difference matters
Explanatory content gets read and forgotten. It answers the question the reader already had. Judgment content gets cited and referenced. It reframes the question the reader thought they were asking.
The distinction isn’t about quality — both can be well-written. It’s about function. Explanatory content serves the reader’s existing frame. Judgment content changes the frame. Only frame-changing content compounds, because it creates new conversations rather than participating in existing ones.
The structure in practice
- Assert (first 10–15%): Take a clear, directional position. Someone should be able to disagree with it. If nobody would disagree, it’s not an assertion — it’s a summary.
- Explain (60–70%): Prove the assertion with evidence, frameworks, examples, and named tradeoffs. This is where specificity lives. Name the URL, the number, the competitor.
- Resolve (final 15–20%): Tell the reader exactly what to do. One specific, actionable next step. End on the strongest sentence in the piece.
The test
Read your last 5 published pieces. Count the assertions versus explanations. If the ratio is below 30% assertion, you’re producing content that informs but doesn’t direct. It will rank. It won’t compound.