Process
Reusable process keeps repeated work from becoming improvised every time.
The process is intentionally practical. It should help choose the right work area, load the right context, reduce avoidable mistakes, and leave enough evidence for the next pass.
| Process area | Purpose |
|---|---|
| Project start | Define audience, purpose, scope, and the first useful slice. |
| Site preparation | Start and maintain sites from the existing site pattern. |
| Coordination | Keep decisions, notes, and responsibilities clear across work areas. |
| Project tracking | Turn durable work into scoped records with outcomes and follow-up. |
| Documentation | Leave restartable notes instead of relying on memory. |
| Review QA | Check links, guards, page rendering, and responsive behavior before release. |
Process Quality Bar
A useful process should answer:
- what starts it
- what context it loads
- what work area it chooses
- what work product it creates
- what review is required
- what should be improved after the work repeats
