How we work
A collaborative process that keeps the problem, the scope and the next decision in view.
Understand the problem before specifying the solution.
Discuss your users, existing tools, constraints and priorities. Identify the key workflows and the outcome the project needs to achieve.
Outcome: A shared problem statement and initial scope.
Make the proposed solution concrete.
Map the main journeys, explore the interface and agree what is included. Identify technical dependencies and acceptance criteria.
Outcome: An agreed direction and a prioritised delivery plan.
Turn the plan into working software.
Develop in manageable increments. Review the important workflows together and use feedback to refine the implementation.
Outcome: Working software and visible progress against the scope.
Check the details that matter.
Test the agreed behaviour, review access and error handling, and prepare deployment and handover. Resolve release-blocking issues before launch.
Outcome: A reviewed release and practical handover documentation.
Keep improvement intentional.
Review what has been delivered and identify useful follow-up work. Agree any ongoing support, maintenance or further development separately.
Outcome: A clear view of ownership and future priorities.
Timing depends on scope, complexity, dependencies and feedback. A delivery plan is agreed after discovery rather than promising a fixed timeline before understanding the work.
New requirements are considered against the agreed scope. Their effect on priorities, cost and timing should be clear before the additional work begins.
A person who can explain the problem and make decisions, access to relevant non-sensitive examples, and timely feedback on the agreed milestones.
Handover and ownership are discussed as part of delivery. Ongoing maintenance and support need an explicit agreement appropriate to the system.
A new product, an awkward workflow or an idea worth exploring. Tell us what you want to improve.