The Organisational Planning and Talent Management track of the OAC Fellowship starts from this premise and extends it through the Japanese concept of hitozukuri — the making of people. In this management philosophy, hitozukuri is not separate from monozukuri, the making of things. The development of people and the development of products and processes are architecturally integrated. A supervisor’s primary role is not to manage output but to design developmental assignments calibrated to each person’s current capability — the Ability + alpha principle, where alpha is the carefully judged stretch that builds capability without overwhelming it. This is not a talent programme bolted onto operations. It is operational architecture designed so that the daily work itself is the development system. And it is budgeted, structured, and expected — not discretionary.
This reframes what organisational planning actually is. It is not headcount forecasting. It is the design of the management architecture through which people encounter problems of appropriate complexity, receive coaching that develops judgment rather than compliance, accumulate capability through structured experience rather than classroom instruction, and eventually develop the ability to develop others. The four-step OJD cycle — identify suitable work, assign it with intent, monitor and lead through the process, create a sense of achievement — is not a performance management technique. It is an architectural design for how capability compounds through an organisation, one developmental cycle at a time, embedded in the rhythm of work rather than extracted from it into a training room.
Talent management as most organisations practice it is a filing system with ambition. It catalogues people into roles, maps succession against an organisation chart, runs engagement surveys that measure sentiment rather than capability, and sends executives to development programmes that produce temporary insight but no lasting architectural change. The reason most executive development fails to persist is structural, not pedagogical. Programmes are funded as discretionary expenditure, approved annually, and disconnected from the executive’s terms of engagement. When budgets tighten, development is the first thing cut. When a new CEO arrives, the previous programme is abandoned. The signal this sends is unmistakable: development is optional, not architectural. For executive development to be lasting, it must be written into remuneration and benefit packages as a joint commitment — the organisation committing resources and protected time, the executive committing to a developmental journey with deliverables that change how the organisation operates. This is not a training entitlement. It is a contractual recognition that the executive’s capability development and the organisation’s architectural development are the same investment.
The programme teaches HR directors and organisational development leaders to see their organisations through information flow rather than organisation charts. Where does knowledge about people’s actual capability reside, and how does it reach the person making assignment decisions? How does learning generated through problem-solving on the gemba travel to the people designing development pathways? Where does the organisation’s management architecture create conditions for capability accumulation, and where does it inadvertently destroy it — through excessive rotation that prevents depth, through promotion criteria that reward visibility over developmental contribution, through planning cycles that treat people as deployable resources rather than accumulating assets?
The Field reconnaissance is particularly transformative for this track. The study of your culture by holding a mirror to it. Participants observe not a talent management system but a management architecture where development is inseparable from daily operations and inseparable from how the organisation values its people. The supervisory system, the coaching routines, the escalation architecture — these are not HR programmes. They are the organisation’s operating system, designed so that every operational interaction is simultaneously a developmental interaction.
What becomes visible is that culture is not created by values statements or engagement initiatives. It is produced by architecture. And architecture that develops people must be invested in with the same seriousness as architecture that develops products — committed to contractually, budgeted explicitly, and protected from the organisational short-termism that has made most executive development a temporary experience rather than a permanent capability.
Architectural Disciplines
Fields of Practice
theme
1
Developing People as Architectural Principle
— embedding the making of people into the operating system so that daily work is the development system rather than extracting development into programmes separate from operations.
theme
2
Developmental Assignment Architecture
— designing the OJD four-step cycle as the organisation’s primary capability accumulation mechanism, calibrating stretch through Ability + alpha rather than cascading competency targets.
theme
3
Contractual Development Commitment
— writing executive development into remuneration and benefit structures as a joint investment commitment that survives budget cycles, leadership transitions, and organisational short-termism.
theme
4
Capability Flow Diagnosis
— mapping where knowledge about people’s actual capability resides, how it reaches assignment decision-makers, and where the management architecture inadvertently destroys capability accumulation through excessive rotation, misaligned promotion criteria, or planning systems that treat people as deployable resources.
theme
5
Culture as Architectural Output
— understanding that observable organisational behaviour is produced by the design of information flows, decision rights, and coordination routines, not by values statements, engagement surveys, or cultural change programmes.
theme
6
Leadership and Management System Design
— redesigning the Leadership and Management layers as the organisation’s primary developmental architecture, where coaching, escalation, problem-solving discipline, and knowledge transfer are built into management routines rather than delivered as separate HR initiatives.