# The one-workflow brief

A reusable planning worksheet from RED / Jay Fan.
Use this with your own team or bring it to a project conversation. No signup is needed.

## 1. Describe the situation
- What does the business or team do?
- Who performs the task, and who uses its result?
- What tools, documents or devices are already involved?
- Write down one ordinary example. Use fictional or anonymised data when sharing.

## 2. Follow the current workflow
| Step | Person responsible | Input | Action | Output | What goes wrong? |
| --- | --- | --- | --- | --- | --- |
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
| Handoff | | | | | |

## 3. Choose the first useful slice
- One person we can design for:
- One task they need to complete:
- The result they must be able to inspect or take away:
- What we will intentionally leave for a later phase:
- One comparable sample or reference, if available:

## 4. Define acceptance
- Starting state and test inputs:
- Steps a representative user should be able to perform:
- Expected output and who checks it:
- An invalid input or failure case to test:
- Device, accessibility, offline or performance requirements:

Avoid claiming a measured improvement until a baseline and a real observation exist.

## 5. Agree the handover
- Scope, schedule, price and revision allowance:
- Data, content, licences and permissions needed:
- Who owns or maintains the result:
- Access, hosting, backups and restore instructions, if applicable:
- Source files, exports and documentation to deliver:
- Who approves release:

This worksheet is a discussion aid, not a quote, contract or engineering specification.

Related notes: https://red1213.com/notes/from-website-to-workflow/
Project desk: https://red1213.com/start/
Contact: jayfan1213@gmail.com