# How to Write Better with The Why, What, How Framework
source: https://eugeneyan.com/writing/writing-docs-why-what-how/ tags: #literature #writing #advice #howto uid: 202210042153 —
^ See the article itself as an example of this template.
Why: Start by explaining Why the document is important. This is often framed around the problem or opportunity we want to address, and the expected benefits. We might also answer the question of Why now?
Think of this as the hook for your document. After reading the Why, readers should feel compelled to blaze through the rest of your doc
What: After the audience is convinced we should solve the problem, share what a good solution looks like.
Together, they enable readers to evaluate and decide on proposals, make trade-offs, and provide feedback.
Another way of framing What is via requirements. Business requirements specify the expected customer experience, uplift to business metrics (success measures), and budget (constraints). They might also be framed as product or functional requirements. Technical requirements specify throughput, latency, security, privacy, etc., usually as constraints.
What should give the reader context on the problem / issue at hand / whatever the thing is trying to solve. Tell the reader what a good version of the solution that your thing is trying to solve looks like.
How: Finally, explain How you’ll achieve the Why and What. This includes methodology, high-level design, tech decisions, etc. It’s also useful to add how you’re not implementing it (i.e., out of scope).