A working day.
A tool that fits it.
If a spreadsheet is doing the job of a whole system, show me how you use it. We can work out which part would benefit from a proper application.
For a specific business process with people, information and decisions to bring together.
Start with one complete task.
Walk me through what happens now, from the first request to the finished job. We identify the information needed, who can change it and the point where the next person takes over. That gives the first version a clear purpose.
Try the important screens.
The prototype uses agreed sample data so you can follow the main journey. I want to know where you get stuck, which detail is missing and what you would expect to happen next. Prototype scope and the move into paid build work are agreed first.
Build the checks around the work.
Roles, record history, exports and validation are chosen for the job. We agree the test cases, how existing data is checked before import and what should happen when information is incomplete.
Plan the handover.
The proposal covers accounts, source code, documentation and any training. Hosting, backups, licences and future changes have stated responsibilities and costs.
A few things to sort out.
Can we start with one department or process?
Yes. A focused first release can cover one complete journey. We agree what is included and what can wait.
Will it work on a phone?
We agree the devices and usage before design. A browser app can have layouts for office screens and phones; native app features need their own scope.
Show me the bit
that slows you down.
A task, a spreadsheet or an idea you want to work through. Describe it first and we can agree what to look at next.