The Hierarchy of Engineering Needs is a model that organizes stages from foundational capabilities through enablement to leadership and outcomes. The model addresses why teams require structured layers of support to operate effectively, highlighting technical foundations, team practices, and organizational enablers. The approach arises from practical experience across engineering and leadership roles in diverse organizations. The framework aims to guide improvement efforts by identifying missing capabilities, focusing investment where it yields the most impact, and enabling sustainable, predictable delivery through deliberate organizational and technical practices.
Actually started out in semiconductor manufacturing and electronics and then arrived in New Zealand 2007 and then was just doing straight software engineering from there on and sort of traversed in between engineering and leadership roles. I was the CTO of a New Zealand company called Accordo and then did a stint as the general manager for engineering at Xero for one of their portfolios and then other ones in between here and there.
Yes, another thing. Why do we need another thing? That is totally valid, yes. Even the books on our respective shelves are full up. Why do you need another thing? Well, this is, in fairness, it's a retake on an old thing or several old things, but the Hierarchy of Engineering Needs is a model that we use and have been using for the past several years and have deci
Collection
[
|
...
]