Before you start
- Someone who can explain the need and bring together the people involved.
Describe the problem to solve
Start with an observable situation: information arrives late, data is entered twice or teams cannot reproduce the same figure. A specific objective helps define a useful first scope.
- Describe the current process and who uses it.
- Give a recent example, anonymised where needed.
- Explain what should become simpler, more reliable or faster.
- List known constraints: timing, equipment, connectivity, existing tools or a budget to discuss.
Prepare a useful first conversation
The Contact form lets you choose your organisation, Kids or Youth Digital Academy. For a business project, select the closest topic and briefly explain your situation. Do not submit passwords or confidential files.
Agree the scope with the team
Before work starts, clarify the deliverables, reviewers, data needed and access to prepare. Schedule, pricing and applicable commitments are those agreed for your project.
- A business owner to explain and approve the process.
- A project contact to coordinate questions and decisions.
- Acceptance criteria: what will show that a deliverable meets the need.
- An agreed channel for sharing documents and tracking questions.
Test and hand over
Start with a representative case and fictional or appropriately anonymised data. Record any differences, then repeat the same test after a correction.
- Prepare a small test dataset and the expected result.
- Review the complete journey with the people who will use it.
- Record issues and the acceptance decision.
- Request a walkthrough, relevant documentation and support arrangements.
Troubleshooting
We do not know which tool to choose.
Start with the business problem and the tools already in place. The first conversation can help clarify the need.
The scope changes during the project.
Explain the change and its objective. Agree its impact on deliverables, timing and terms before including it.