A requirements document does not have to be long. It has to be clear enough that two people reading it picture the same system.

What to put in

Cover the essentials in plain language.

  • The problem and who has it
  • Who will use the system and what each person does
  • The must have features, in order of importance
  • The rules the system must follow, such as VAT or approvals
  • What it must connect to
  • How you will know it works

Keep wishes separate

Split what you need on day one from what would be nice later. A short list of must haves keeps the first version small enough to finish.

Add real examples

Attach the forms, spreadsheets and emails you use today. Real examples answer questions that a description cannot.