A simple framework to help you move forward. Download it below.
The 334 is a deliberately simple model for getting work delivered without drowning in jargon, ceremonies, or consultants wearing expensive loafers.
It combines 3 roles, 3 artefacts, and 4 meetings into a lightweight system that helps teams make decisions, stay aligned, and keep momentum.
The three roles are:
- a Decision Maker who owns priorities,
- a Process Owner who keeps the machine running smoothly,
- and Team Members who do the work – the means of production
The three artefacts are:
- a prioritised backlog,
- small pieces of valuable work,
- and a visible wall or board showing progress.
The four meetings create a rhythm:
- planning,
- stand-up,
- showcase,
- and continuous improvement.
The model draws heavily on proven thinking, particularly the work of Jeff Sutherland and Ken Schwaber, whose Scrum framework helped popularise iterative delivery, visible work, and empowered teams. The 334 takes those useful principles and strips terminology and ensures applicability in traditional projects.
It keeps what works: clear ownership, short feedback loops, small batches of work, regular stakeholder visibility, and continuous learning. Then it translates them into plain English.
Why is it good?
Because complexity is usually made worse by confusion, not difficulty. The 334 reduces friction fast. It makes priorities visible, exposes blockers early, and gives teams a repeatable cadence for making progress. Instead of waiting months to discover nothing is moving, you know this week. Instead of ten people quietly assuming someone else owns a decision, one person does. Instead of status theatre, you get evidence. It is intentionally lightweight, which means energy goes into delivery rather than process worship.
Implementation is quick. Appoint the three roles, create a visible backlog, put current work on a simple board, and start the meeting rhythm immediately.
You don’t need new software, a transformation programme, or an offsite involving sticky notes Start with one team, run it for a fortnight, and refine from there. The 334 is not the only answer, nor does it pretend to be. It is one practical fix among many. But it is available, simple, and useful now.
Leave a comment