By role¶
Every guardrail names the roles that lead it. Find the guardrails for your role, what to show in each phase, and when to work with an architect.
Prototype - testing with users
This section is an early prototype that we are testing with users. It may change a lot, and some of it may be wrong. Check with your solution design authority before relying on it, and tell us what works and what does not through the feedback link above.
Roles use the names in the DDaT Capability Framework. Leading a guardrail means making sure the team meets it and can show it - not doing all the work alone. Most guardrails are shared, and every role should know the Must guardrails for its phase.
| Role | Guardrails you lead | Must |
|---|---|---|
| Product manager | 16 | 4 |
| Delivery manager | 10 | 5 |
| Service designer | 11 | 2 |
| Interaction designer | 9 | 3 |
| Content designer | 3 | 2 |
| User researcher | 8 | 1 |
| Developer | 41 | 11 |
| Technical architect | 32 | 6 |
| Security architect | 20 | 12 |
| Data architect | 10 | 3 |
| Performance analyst | 4 | 0 |
You can also filter the guardrail library by role.