Fusion
Book a session

The Idea to Impact Challenge

Select a problem or opportunity. Pick a workflow. Sixteen hours later, it's built, tested and deployed with user guides.

Pick a workflow your business actually runs, and we will take it the whole way. This is the sequence, with the clock running. Every step hands the next one a finished artefact — which is why the trace from the sponsor's problem to software running in production holds without anyone assembling it afterwards. Four of the sixteen hours are your people's time.

A ringed number is a step that needs people from the business. There are four of them.

  1. 01

    Sponsor session

    1 hour Business time 1:00h

    Sit with the sponsor and agree the problem to be solved, the opportunity, the success measures and who the stakeholders are.

    Session transcript
  2. 02

    Problem & Opportunity Statement

    1 hour 2:00h

    Produce the statement and the stakeholder artefacts straight from the sponsor session transcript.

    Problem & Opportunity Statement Stakeholders & Personas
  3. 03

    Observation sessions

    1 hour each Business time 3:00h

    Stakeholders walk you through the workflows they run today, and you capture the pain points and the openings to improve.

  4. 04

    Current state documented

    2 hours 5:00h

    Write up how the work runs today and what it runs on, then update the Problem & Opportunity Statement with what you learned.

    Current State Workflows Current State System Architecture
  5. 05

    Domain Model and Workflows Value Stream

    4 hours 9:00h

    Design the model the solution rests on, and the value stream its workflows make up between them.

    Domain Model Workflows Value Stream
  6. 06

    Workflow design and Model Specs

    1 hour 10:00h

    Design one workflow from the stream. Create the model specs behind it, or update the specs that already exist.

    Workflow design Model Specs
  7. 07

    Build and unit test

    1 hour 11:00h

    Build the workflow and unit test it.

    Working workflow Unit tests
  8. 08

    System tests written and run

    1 hour 12:00h

    Write the system tests, run them, and record what they returned.

    System tests Test results
  9. 09

    User guide and video

    30 minutes 12:30h

    Write the user guide and produce the walkthrough video, so the people who use the workflow can start on it.

    User Guide User Guide Video
  10. 10

    Users review and test

    1 hour Business time 13:30h

    Hand the guide and the build to the users. They review the guide and test the workflow against the way they actually work.

    Review findings
  11. 11

    Triage, fix, re-test

    1 hour 14:30h

    Triage the findings and fix them. Every artefact the fix touches is updated with it, and the system tests run again.

    Updated artefacts System test results
  12. 12

    Users confirm the fixes

    1 hour Business time 15:30h

    The users who raised the findings confirm the fixes. The record is current at the moment they sign off, not a week later.

    User sign-off
  13. 13

    Release notes, roadmap, production deploy

    30 minutes 16:00h

    Publish the release notes and the updated roadmap, then deploy to production. Both come off artefacts that are already current, which is why this step is measured in minutes.

    Release notes Roadmap Production deploy
  14. Run complete 16:00h
  15. 14

    Monitor usage, security and performance

    continuous

    From the moment it is live. Usage, security and performance are watched in production, and what comes back is the input to the next run.

Total

16:00h

Two working days from the sponsor session to the workflow running in production. Add an hour for every extra stakeholder you observe.

Business stakeholder time

4:00h

Four of the sixteen hours ask anything of your business: the sponsor session, the observation session, the review, and the confirmation. The other twelve run without them.

The running clock assumes one observation session. Nothing in the list is a status meeting, a handover, or a document written to catch a record up. Step 14 sits outside the clock, because the monitoring does not stop.

Start the clock on one workflow.

Step one is a one-hour session with your sponsor. Everything after it runs from what you agree there.

Book the sponsor session

Ready to pick your workflow?

One sponsor hour to start, sixteen working hours to production. Bring the workflow your team complains about most — that is the one worth proving.

Book your Challenge session See pricing