A straightforward way to improve what isn't working.

The process

1. 01

   Tell me what's not working

   The first step is simply to explain what is causing the problem.

   It might be a repetitive process, an awkward spreadsheet, slow software, two systems that do not communicate, or an idea for a better way of working.

   You do not need to translate it into technical language.

2. 02

   We talk it through

   We'll have a conversation about how the process works today.

   I will ask questions about who is involved, what information is used, how often the process happens, where time is being lost and what tends to go wrong.

   The aim is to understand the problem properly before discussing solutions.

3. 03

   Understand the process

   For straightforward work, the initial conversation may be enough.

   For more complex systems or uncertain requirements, some paid discovery may be useful. That can involve reviewing the current application, mapping a workflow, examining existing data or investigating a technical constraint.

   Where discovery is needed, that will be discussed before any work begins.

4. 04

   Recommend an approach

   Once I understand the problem, I will recommend what I believe is the simplest sensible way forward.

   That might be automation, an integration, a targeted improvement to existing software or a new application.

   Sometimes the right recommendation may be that no custom development is needed at all.

5. 05

   Agree scope and cost

   Before development starts, we agree what is being delivered, what is included and how the work will be priced.

   Smaller or uncertain pieces of work may be billed using an hourly estimate.

   Clearly defined projects may be quoted at a fixed price.

   If the scope needs to change later, we discuss the impact before the additional work is carried out.

6. 06

   Build, test and deliver

   Development is broken into manageable pieces rather than disappearing into a long build with no visibility.

   Where practical, you will be able to review progress during development and confirm that the solution matches the way you actually need to work.

   The finished work is tested before delivery, and any deployment requirements are agreed as part of the project.

7. 07

   Keep improving where useful

   Some projects finish when the agreed work is delivered.

   Others benefit from ongoing development as the business changes or new improvements become worthwhile.

   If regular support makes sense, we can discuss an ongoing arrangement. There is no requirement to continue beyond the original project.