Skip to main content

Content Intent: Tutorial

Purpose​

Use when readers need to complete a task while following explicit steps.

Canonical Structure​

  1. Outcome and prerequisites
  2. Numbered execution steps
  3. Common errors and fixes
  4. Verification checkpoint

Best-Fit Formats​

  • article
  • blog-post
  • newsletter
  • reddit-post

Best-Fit Styles​

  • technical
  • professional
  • friendly

Rules​

Rule: Define the End State First​

Description: Tell readers what they will be able to do when finished. Negative example: Starting with background theory and no task outcome. Positive example: "By the end, you will produce a 5-part weekly update template."

Rule: List Prerequisites Up Front​

Description: Name required tools, context, and assumptions before step 1. Negative example: Revealing key dependencies halfway through the guide. Positive example: One short prerequisites block before instructions.

Rule: Keep Steps Atomic​

Description: Each step should include one action and one expected output. Negative example: One giant step with five actions and no checkpoints. Positive example: Step format: action sentence plus expected result.

Rule: Use Verification Milestones​

Description: Include short checks so readers know they are on track. Negative example: No confirmation until the very end. Positive example: "After step 3, your opening should name audience and payoff."

Rule: Add Failure Recovery Notes​

Description: Document likely failure points and quick fixes. Negative example: Ignoring common mistakes readers will hit. Positive example: "If this reads too long, split paragraph 2 into bullets."

Rule: End With a Reuse Path​

Description: Show how readers can apply the process again. Negative example: Ending at task completion with no reuse guidance. Positive example: "Reuse this checklist for every weekly post draft."