PLANNING GUIDE
Describe the problem
Explain what happens today and where it becomes difficult. A concrete example is more useful than a long list of desired technologies.
Identify the users
List who will use the system, what each person needs to do and which information they should be able to access.
Separate essentials from later ideas
Define what must be included in the first version. Keep optional improvements in a separate list so they do not obscure the core purpose.
Document constraints
Include existing systems, available APIs, content ownership, target dates and any budget boundaries. Call out unknowns rather than guessing.
Define a useful outcome
Describe the workflows that need to work at handover and how you will review them. This gives everyone a practical basis for acceptance.
← All planning guides