What Before Why or How

Lead with the point before explaining why or how. Many documents bury the main idea deep in the text — state it first.

The Rule

Begin every document, pattern, prompt, or section by clearly stating the point or main idea first.

❌ DON'T bury the point

This article explores effective remote work. Over the past decade, remote work has transformed how teams collaborate. Companies have experimented with various approaches. Flexible schedules emerged as beneficial. Clear communication became essential. After much trial and error, best practices developed.

✅ DO state the point first

Remote work succeeds when teams establish clear communication rhythms. Set core hours for overlap, use async communication as default, and document decisions publicly.

Examples

Email

❌ DON'T build up to the point

Hi team, I've been thinking about our deployment process and after reviewing several options and considering our constraints, I believe we should…

✅ DO state the point first

We should switch to automated deployments. Here's why…

Documentation

❌ DON'T narrate the structure

This document describes the authentication system. First, we'll cover the history of authentication in our application, then discuss the various approaches we considered, and finally explain the current implementation.

✅ DO lead with the facts

The authentication system uses JWT tokens with a 24-hour expiry. Users authenticate via OAuth 2.0 with Google or email/password.

Why This Matters

• Readers can quickly determine relevance
• AI agents can extract information efficiently
• Busy readers get the point without reading everything