Better decisions. Before the first line of code.
For the people who define the work, choose an approach, and take responsibility for a system. Questions to ask, examples to discuss, and checks to use with your team.
Start with the decision in front of you
Before development
Write a software brief that a team can build from.
A useful brief gives everyone the same job to solve. Define users, boundaries, inputs, and the evidence you will use to accept the work—without designing the entire system in advance.
Read the guidePlatform decisions
Should you start with a website or a mobile app?
Choose the approach after understanding the job and the device constraints. Compare access, offline behavior, device integration, and the work required to maintain each option.
Read the guideAcceptance and operation
Accept software your team can actually operate.
A working URL or an archive of source files is only part of a handover. Check accounts, documentation, deployment, recovery, and ownership so the next team can continue the work.
Read the guide
Have a project in mind? Start with what you know.
Describe the job, the constraints, and the parts you are still working out. We can use that to define the next step.