# Your workflow project brief

Use this with your team or any software builder. No technical specification required.

## 1. The problem
- Which recurring process are we improving?
- Who experiences the problem?
- What happened the last time it went wrong?

## 2. The current workflow
Write one line per step: trigger -> person responsible -> action -> tool -> next step.
Include the finish: how do you know the work is complete?

## 3. Tools and information
- Tools we need to keep:
- Where the authoritative customer/project record lives:
- Information that gets copied more than once:
- Integration access or exports available:

## 4. Exceptions and permissions
- Missing or duplicate information:
- Late approvals and other blocked steps:
- Who may view, edit, approve, or send:
- Actions that always require a person:
- What happens if a connected service is unavailable:

## 5. The first useful version
- One complete outcome it must deliver:
- Features explicitly outside this first version:
- Who will test it:
- An ordinary test scenario:
- An exception test scenario:

## 6. Value and success
- Runs per week:
- Minutes of manual effort per run:
- Current errors, delays, or missed follow-ups:
- Target after launch:
- Who will measure it, and when:

## 7. Delivery and ownership
- Decision-maker and available kickoff date:
- Data cleanup or migration required:
- Hosting, provider, and support costs to confirm:
- Code, accounts, documentation, and export handoff:

A focused first release completes one valuable workflow. It does not need to replace every tool.

Custom App Guy — https://customappguy.com
Discuss this brief: https://customappguy.com/workflow-call