Recipe: researcher-confident-whitepaper
A composition of Researcher voice, Confident tone, Classical Argument style, and Whitepaper format. Used for authoritative position documents that advance a substantive claim through structured evidence and direct reasoning.
When to use
Section titled “When to use”You have a well-grounded position on a technical or strategic topic, the evidence supports it, and the audience needs a document they can cite, share, or use as a decision anchor. This recipe fits when the claim is genuinely debatable and the value comes from showing the reasoning rather than asserting the conclusion. It is the right tool for engineering practice recommendations, pricing model analyses, architectural guidance documents, and standards proposals where the reader will push back and deserves a real argument.
When to use something else
Section titled “When to use something else”If the audience is primarily non-technical and the goal is to move them emotionally rather than convince them logically, a Narrative Case Study in Warm tone will carry more force. If the decision is already made and you are documenting it for future maintainers, a Decision Log style ADR in Pragmatic Architect voice is more durable. If the argument is short and the audience is internal, a Problem-Solution style brief is faster to read and write than a full whitepaper.
Composition
Section titled “Composition”| Axis | Entry | Why |
|---|---|---|
| Voice | Researcher | Grounds every claim in evidence, names the method and its limits, and refuses to let conclusions outrun the data. The voice that earns citation. |
| Tone | Confident | Strips ritual hedges and states positions directly. The reader can push back on a clear claim; they cannot push back on a hedge. |
| Style | Classical Argument | States the claim early, presents evidence with warrants, addresses the strongest objection directly, and restates the claim in light of the full argument. The structure that distinguishes reasoning from assertion. |
| Format | Whitepaper | Long-form, sectioned, with executive summary and explicit recommendations. Gives the argument the space it needs and produces a document that stands on its own authority. |
Worked examples on this recipe
Section titled “Worked examples on this recipe”- The case for usage-based pricing
- Why small teams should adopt trunk-based development