Idea to Delivery¶
Purpose¶
This workflow explains how a signal becomes a shipped and documented change.
Step 1: Capture the signal¶
A signal can come from:
- product discovery
- customer feedback
- ops incidents
- sales feedback
- technical issues
- compliance or security needs
Step 2: Qualify the signal¶
The owner clarifies:
- the problem
- who is affected
- expected value
- urgency
- dependencies
- whether the issue is recurring or structural
Step 3: Create the right artifact¶
Depending on complexity, the work may need:
- a Linear issue
- a product or technical spec
- an ADR
- an Eraser diagram
- a runbook update
Step 4: Plan execution¶
The work is scoped, prioritized, and assigned.
Step 5: Implement¶
The owner executes the work with the right level of review and coordination.
Step 6: Validate¶
The result is validated technically, operationally, and product-wise when needed.
Step 7: Document¶
If the work changes a durable behavior, process, architecture, or responsibility, the handbook must be updated.
Step 8: Close the loop¶
The issue is linked to the final documentation, merged work, and related decisions.