Who it's for
Who the product serves
A two-sided workflow for requesting, agreeing, and tracking what one project needs from another.
All work
Case studyPortfolio management2026
Strategy Dot Zero
Dependency module
One project wrote the dependency down. The other one was never told it existed.
Product model
1
Get and Give registers
Two registers: what a project needs, and what it owes to others.
2
Approval workflow
Request, review, accept, reject, or revoke across project boundaries.
3
Live dependency status
Progress that follows the provider's status report, with override.
Role
Product Designer for the dependency model, registers, and approval workflow
Timeline
2026
Platform
Web, project plan and portfolio dependency registers
Impact
An approved model that gives a dependency a second author, and a status that comes from work the provider is already doing.
What it is
The product, and where this work sits inside it.
Business position
Where it sits
A dependency is where a project records what it is waiting on from somewhere else. It sat as two tables inside one project's plan, visible to nobody but the person who typed it. It is now a request the other project has to accept, with a status that comes from reporting they already do.
Modules
- 01Get and Give registers
- 02Approval workflow
- 03Live dependency status
8 more sections
There is a lot more here — it is just under NDA.
The detail stays private under NDA. Ask me for the password.
- Where it lived
- Note or agreement
- The states
- Where status comes from
- What it points at
- What changes
- The work
- Looking back
One unlock opens every case study here for 30 days.