Skip to the content.

How to Start a Document from Scratch

About this sample. My own framework for approaching a new documentation project, developed from experience leading documentation for regulated fintech and GRC products.

Introduction

Writing a document from scratch follows a process similar to developing software. Just as software is built to achieve a defined purpose, a document needs a clear purpose, audience and problem to solve. We can follow a Document Development Life Cycle (DDLC), much like a Software Development Life Cycle (SDLC), to keep that process structured and repeatable.

I use a five-stage approach I call POWER:

Here’s how each stage works.

Planning

Planning is where the writer defines the goal, purpose, scope and target audience of the document.

Key steps

Output: Audience analysis, documentation plan, content outline, template and style guide.

Audience analysis

Understanding who you’re writing for shapes every decision that follows. Different document types serve different audiences with different needs.

Identify your audience

Understand their purpose. Are they trying to solve a problem, configure a feature, or learn a new skill?

Understand their expertise level

Customize accordingly

Estimate time using

Organizing

This stage is about gathering and structuring the information the document will need. Raw information from subject matter experts is rarely ready to write from directly — it has to be arranged so the final document is accurate, correct and complete.

Key steps

Output: Collected data, use cases and technical details.

Writing

This is the drafting stage. Working from the planned template and structure, the writer builds the content from the information gathered, including only what’s relevant to the document’s purpose.

Key steps

Output: A reviewed and improved documentation draft.

Release

The final stage is releasing the document.

Maintenance. Documentation needs to stay current as requirements and the product evolve.

Key steps

Output: Updated, well-maintained documentation.