Discovery template
Brief template for a PHP project
A good brief does not design the whole solution. It clarifies the problem, constraints and pending decisions so business and technology start the same conversation.
1. Expected outcome
What should change for users and business.
2. Initial scope
What is in, out and still open.
3. System and context
Technical and organizational baseline.
4. Data and integrations
Information and systems crossing the product.
5. Quality and operations
How it reaches and stays in production.
6. Pending decisions
Uncertainty to resolve.
Turn answers into decisions
- Work through it with business, product, technology and operations.
- Attach real examples of inputs and outputs.
- Separate requirement, preference, constraint and assumption.
- Review after discovery; do not treat it as an immutable contract.
Content connected to this decision
Continue with diagnosis, execution or related experience.