Practical insights
Better questions make
better software briefs.
Practical notes to help shape an initial conversation. A final recommendation depends on the product, the people using it and the constraints around it.
Product planning · Practical guide
The smallest product that completes the journey.
Choose between an app, website or automation. Then write a brief that gives your first release a clear boundary.
Read the guide Android · Practical guideOffline is a product decision.
What happens to work when the connection disappears? Think about continuity, ownership and recovery before adding screens.
Read the guideStart with context.
Keep the brief useful.
A useful brief explains what happens today, where the process gets difficult and what a person should be able to complete afterwards. It gives the project a shared point of reference.
Examples can help, but remove personal information and confidential details from the first message. If access to an existing system is needed, agree that access separately.
Prepare a project brief ↗