← Home
A practical first project
Start with one practical project.
A focused piece of work around one recurring task, page, workflow or information journey, agreed before work begins.
What the project is for
The aim is to make one useful thing clearer, easier to review or more manageable: for example a repeated admin task, a page that needs clearer decisions, a small workflow, an approved-information journey or a prototype for a bounded process.
Cost, timing, scope, data handling and fit are agreed before work begins. No numeric price, price range, checkout or payment link is published here.
What it normally includes
- 1. Understanding the task and context.
- 2. Agreeing boundaries, approved information sources and human-review points.
- 3. Producing one practical improvement, map, prototype or build.
- 4. Reviewing it together.
- 5. Handing it over clearly.
- 6. Deciding whether to stop, refine or continue.
What it does not imply
- An open-ended transformation programme.
- Automatic high-impact decisions.
- Compliance, legal, medical or regulatory approval.
- Guaranteed time savings, productivity, revenue or any other outcome.
- Replacement of human judgement, approval or accountability.
- Unagreed additional work or ongoing support.
People retain judgement, approval and accountability. No automatic high-impact decision is introduced.
How to begin
Start with a broad, non-confidential outline. If the work looks suitable, the next step is to agree the practical project before any work begins.