Most organisations don’t fail at "digital" because they can’t build software; they fail because they underinvest in the work that delivers better digital outcomes.
So I put together a small framework (and a deliberately simple site) called RAADDDR - pronounced “rad-door”:
It’s a practical way to talk about what great digital teams actually do - day in, day out - without turning everything into a "transformation" slide deck.
RAADDDR = seven core activities great digital teams do (continuously):
- Research - understand real user needs and contexts.
- Analyse - make sense of the problem, the data, and the landscape (including privacy, accessibility and security).
- Architect - make technical choices that stay maintainable under real demand.
- Design - shape end-to-end services that people can actually use.
- Develop - build quality software.
- Deliver - ship value reliably, with the right checks, controls and assurance.
- Run - operate services properly: reliability, incidents, performance, and compliance.
Miss one, and you’ll pay for it later - usually with interest.
Public good
The content is published into the public domain (CC0), so you can copy it, remix it, and reuse it freely. Also: no ads. No email gate or pay wall. (tips are welcomed though 🙌)
Who it’s for
If you’re any of the following, RAADDDR is meant to be useful:
- You’re building or leading a digital product or service team
- You’re hiring and want a clearer map of the capabilities you actually need
- You’re mentoring people and want language for the craft and career paths
- You’re trying to explain "digital" to leadership
Two asks (after you’ve had a look)
1) Suggestions and improvements: if anything feels unclear, missing, or wrong, tell me - or open a suggested change via GitHub.
2) If you think it’s good: please share it and use it. The only way frameworks like this help is if they actually get used and adopted.
Top comments (0)