Purpose:
Teach something practical.
Delivery Requirement:
The post MUST enable the reader to complete a concrete step, not just understand the process.
Mandatory naming rule:
The How-to MUST be explicitly named as a small guide or test
(example: “The 5-Minute Ownership Check”, “The Email Deliverability Pre-Send Check”).
Unnamed How-to posts are invalid.
Mandatory naming format:
The How-to MUST be named using one of these formats:
-
“The X-Minute [Noun] Check”
-
“The [Number]-Step [Noun] Test”
The noun MUST describe what is being verified
(ownership, payment, access, delivery, recovery), never the tool.
Unnamed How-to posts are invalid.
Constraints:
• Max 5 steps
• Steps must be executable by non-technical readers
• Focus on what to check, not how to configure deeply
• The How-to MUST scope to one situation or system class
(not multiple critical systems at once)
Forbidden:
• Endless tutorials
• Abstract explanations
• Multi-system deep dives in a single How-to
Execution result rule:
• The steps MUST lead to ONE observable outcome:
-
a mismatch found
-
a yes / no confirmation
-
a named owner
-
a stop / go decision
Required ending:
A sentence like:
• “If you do only one thing from this, do ___.”
Validation sentence:
After completing the steps, the reader must be able to say:
• “I found ___”
• “I confirmed ___”
• “I cannot confirm ___”
Invalid if:
• The post teaches concepts without enabling action
• The reader cannot execute the test in under 10 minutes
• The outcome depends on interpretation instead of observation