Zodeen / Why it matters

Why it matters: projects fail on what the plan can’t see

The research, the two-minute film, how everything is connected, and one real week at Brightway.

Projects fail on what the plan can’t see

• 72% of project people spend half a day or more every month collating project reports by hand (Wellingtone, The State of Project Management 2026)
• 1 in 2 organisations do not have access to real-time KPIs (Wellingtone, The State of Project Management 2026)
• 81% of project professionals say projects have become more complex in recent years (PMI, Pulse of the Profession 2026)
• 45% over budget, on average, for large IT projects, delivering 56% less value than predicted (McKinsey with the University of Oxford (2012 study))

Zodeen in two minutes (2:09)

Brightway is launching a new app. One update, one overloaded engineer, two approvals, and a report that writes itself, recorded in the live product.

An example: Brightway app launch

• Monday: Off track. The new app’s go-live is forecast for December 11, a week late, because the cloud backend is 10 working days behind. Bob is booked at 208%.
• Isabella: She noticed. She tells Priya and Elena, Bob’s two project leads, and puts it on their My list.
• Bob: One update. Bob moves the backend from 35% to 60%. It is now inside its slack: go-live is back to December 4 and Bob drops to 158%.
• Elena: Approves. His payroll integrations move a week later; the payroll plan has the slack. Bob: 127%.
• Priya: Approves. Marcus helps on the backend for three days. Bob: 98%, and the launch is green.
• Friday: Reports. The stand-up, the weekly report and the steering pack already say all of this, with the evidence.

Get started · Why it matters · Features · Charts · Why Zodeen · FAQ