People

Technology is built and operated by people. The quality of the technical function is inseparable from the quality of the team — its composition, its capability, and the culture that determines how it works.

People — technology is built and operated by people. The quality of the technical function is inseparable from the quality of the team: its composition, its capability, and the culture that determines how it works. Most technical problems that appear to be architectural or process failures are, on examination, people problems — knowledge concentrated in individuals who cannot be replaced, teams structured around historical reporting lines rather than the work, capability that has not been developed because there was no senior technical authority to develop it, and culture that tolerates standards violations because nobody enforces them. Getting the people dimension right is not a soft consideration alongside the technical work; it is part of the technical work. What the people domain covers, across six areas: Team Structure (how the technical function is organised — whether the structure reflects the work it needs to do or the history of how it was assembled; reporting lines, role definitions and the distribution of accountability across the team); Capability Development (the technical skills, architectural understanding and professional judgment the team needs, where the gaps are, and how they are addressed through hiring, development or external support); Knowledge Management (whether critical knowledge is held by individuals or distributed across the team — systems and practices that make knowledge durable, not lost when someone leaves or is unavailable on leave); Hiring & Team Acquisition (the ability to identify, attract and evaluate technical talent — interview processes that assess what matters and hiring decisions that reflect the actual requirements of the role); Culture & Standards (the team behaviours that determine whether standards are applied consistently, whether technical debt is made visible, and whether quality is a shared value rather than an individual preference); and Mentoring & Leadership Development (developing technical leads and senior engineers into people who can own technical decisions, lead teams, and

Most technical problems that appear to be architectural or process failures are, on examination, people problems. Knowledge concentrated in individuals who cannot be replaced. Teams structured around historical reporting lines rather than the work. Capability that has not been developed because there was no senior technical authority to develop it. Culture that tolerates standards violations because nobody enforces them.

Getting the people dimension right is not a soft consideration alongside the technical work. It is part of the technical work.

What the people domain covers

Team structure. How the technical function is organised. Whether the structure reflects the work it needs to do, or the history of how it was assembled. Reporting lines, role definitions, and the distribution of accountability across the team.

Capability development. The technical skills, architectural understanding, and professional judgment that the team needs. Where the gaps are. How they are addressed — through hiring, development, or external support.

Knowledge management. Whether critical knowledge is held by individuals or distributed across the team. Systems and practices that make knowledge durable — not lost when someone leaves or unavailable when someone is on leave.

Hiring and team acquisition. The ability to identify, attract, and evaluate technical talent. Interview processes that assess what matters. Hiring decisions that reflect the actual requirements of the role.

Culture and standards. The team behaviours that determine whether standards are applied consistently, whether technical debt is made visible, and whether quality is a shared value rather than an individual preference.

Mentoring and leadership development. The development of technical leads and senior engineers into people who can own technical decisions, lead teams, and provide the kind of judgment that reduces dependence on external support over time.

The connection to mentoring

The Mentoring service at Sixteen Pillars addresses the people dimension specifically — building the decision capability of business leaders who are responsible for technical functions.

Start a Conversation