Discover
Why: Different offices may have legitimate differences; do not erase them without agreement.
Deliverable: Stakeholder map and policy-variant inventory.
PRACTICE PROJECT / GUIDED PROJECT
Digitise leave requests without copying a broken approval process into software.
Read the brief and work through the deliverables before opening the reference approach. Your notes stay in this browser only.
A fictional 400-person company handles leave requests by email across three offices.
Employees cannot see request status and managers use different approval rules.
Employee IDs and balances are available from the HR system as a daily export; no live API is currently available.
Draft an approach here, or work offline. Notes are stored locally in your browser—not sent to a server.
This is one defensible approach, not the only correct answer. Compare the reasoning and trade-offs with your own work.
Why: Different offices may have legitimate differences; do not erase them without agreement.
Deliverable: Stakeholder map and policy-variant inventory.
Why: Status visibility is valuable even before full automation.
Deliverable: Request, approval and notification stories with role rules.
Why: Track whether the new flow reduces friction.
Deliverable: Approval time, clarification rate and adoption measures.