Develop and check changes away from the live service.
05Reference / Working with QIDMU
A clear way to begin.
What we agree on, how an idea takes shape, and what happens after release. A short guide to the work behind the interface.
01 / The starting point
You do not need a finished specification.
Bring the work as it is: who does it, where it becomes difficult, and what you would like to change. We can start with a conversation, a workflow or an existing product, then define a useful first scope together.
02 / Working together
Your knowledge shapes the system.
You bring the context of the business. We turn it into options, prototypes and working software, using human judgment and AI-assisted exploration. Reviews keep assumptions visible and important decisions in your hands.
- 01Listen
People, work and constraints
- 02Shape
Options and a first scope
- 03Make
Prototypes and working software
- 04Review
Feedback and agreed checks
- 05Use
Release, observe and improve
03 / Delivery
Make the next step concrete.
The sequence adapts to the project. A small website and a staff system need different depth, but both benefit from clear scope, something tangible to review, and testing before release.
01Understand
Users, needs and what success would mean
02Design
Flows, interfaces and the first version's boundaries
03Build
Implementation and checks against the agreed scope
04Operate
An agreed release and support plan; feedback for what follows
04 / Useful terms
The words behind the work.
- Prototype
- A way to test an idea or interaction. It may use sample data and does not, by itself, mean a production service is ready.
- AI-assisted workflow
- A model helps with a defined task, using selected information and permitted tools. Its limits, review points and operating costs are part of the design.
- Integration
- A deliberate connection between systems. Two products appearing in the same project does not mean every workflow or record is shared.
- Staging
- A separate place to review and test a release candidate before it reaches the people using the live system.
- Acceptance criteria
- The agreed checks that show the delivered work meets its scope. Business impact is a separate question that needs real-use measurement.
05 / Release and support
A release is a beginning, not a finish line.
Before release, we review access, test the important paths and agree how data will be protected and changes handled. After release, support hours, monitoring, maintenance and future improvements follow the project's agreement—not an assumed service level.
Review a candidate in a separate environment, with access appropriate to its content.
Release the approved scope, then observe and improve under the agreed plan.