Leadership Development Systems and the Project Manager Pipeline

Practice note: In one sentence Leadership development is the deliberate, systems-level process by which organisations grow the competencies, judgement, and self-awareness their project managers need to lead progressively larger and more complex endeavours — achieved through a blended portfolio of formal training, experiential assignments, mentoring, coaching, and self-directed learning.

In major delivery organisations, the project manager pipeline is not an HR nicety — it is a capability on the balance sheet. When you commit to a programme like complex naval-platform programmes, complex capability programme (armoured-vehicle capability), or complex subsystem programme — running across decades, billions of dollars, and thousands of staff — you cannot hire your way out of a leadership shortfall. You must grow leaders deliberately. The supplied source material is the engine room of that growth.

The "Why" — Leadership Is a Capability You Build, Not a Role You Fill

Consider a structural reality of the long-term industrial programme at an Australian shipbuilding site. The complex naval-platform programme will run from design finalisation through to the final ship's in-service withdrawal — comfortably across 40+ years. In that window, the Associate Project Manager hired onto a small subsystem integration package today may well become the Programme Director leading the delivery of Ship 9 in the late 2040s. You cannot wait until you need that leader to begin growing them.

This is why mature programme environments — and their governing frameworks like a principles-based project framework's guidance on team performance, formal project method's "Organisation" theme, and applicable contract framework's competency requirements — treat leadership development as a continuous obligation rather than an event. The supplied research is blunt on the point: organisational project management maturity is impossible without a deliberate leadership pipeline, because processes without capable humans to lead them produce only compliance theatre.

Practice note: The business value in one line Every dollar invested in leadership development compounds across the remaining career of the leader — and in heavy engineering and defence, careers are long and programmes are longer.

The supplied learning material frames the outcome starkly: competencies must be developed. They do not arrive with the graduate certificate, and they do not accrete automatically with tenure. They must be built — through a structured blend of interventions that we will dissect below.

The "What" — Defining Leadership Development

Practice note: Working definition Leadership development is the systematic expansion of an individual's capacity to perform leadership roles and processes effectively — encompassing knowledge (what to do), skills (how to do it), self-awareness (who one is as a leader), and behavioural repertoire (the range of responses available in novel situations).

The supplied source distinguishes between leader development (growing the individual's human capital — traits, skills, self-knowledge) and leadership development (growing the organisation's social capital — the networks, shared norms, and collective capacity through which leadership happens). A mature defence prime invests in both simultaneously; investing in only one produces either brilliant individuals with no system to support them, or a polished system with no one capable of animating it.

The three channels of competence acquisition

The supplied source material identify three channels through which leadership competencies are built:

These three channels map neatly — though not identically — onto the widely cited 70-20-10 model of leadership development, which The supplied source material "Acquiring leadership competencies" explicitly flags.

The 70-20-10 Model — The Architecture of Competence Acquisition

The 70-20-10 framework, as presented in the supplied source, proposes that the typical leader's capability growth is distributed roughly as follows:

• 70% from challenging on-the-job experiences (stretch assignments, novel problems, high-visibility deliverables)
• 20% from developmental relationships (mentoring, coaching, feedback from bosses and peers)
• 10% from formal coursework and training (classroom learning, workshops, certifications)

Practice note: The 70-20-10 ratios are descriptive, not prescriptive The numbers are a useful orientation device, not a budgeting rule. Organisations that take them as a literal spending target — e.g., "therefore we will only spend 10% of L&D budget on formal training" — have misread the model. The point is that experience dominates, not that training is optional. In defence contracting, applicable contract framework-mandated competency evidence and export-control authorised-constrained programme access often make formal certification the gating mechanism that unlocks the experiential 70%.

The practical implication for an aspiring project manager in a prime contractor, a major contractor, or a prime contractor environment is this: stop chasing only the certifications. A formal project method and a formal project credential look impressive on a professional profile banner but account for roughly 10% of the leader you will become. Most of your development — the hard-won, irreducible part — will come from being trusted with a stretch assignment and then being supported through it by a good mentor.

The "How" — Applying Leadership Development in a Heavy Engineering Programme

Let us now walk through the full applied architecture. The supplied source material identifies six core modalities; we will take each one in turn and situate it in a realistic defence / heavy engineering context.

1. Formal Leadership Training Programmes

Formal training remains ubiquitous. Almost every large organisation runs one — often badged as a "Leadership Academy", "Management Development Programme", or "PM Pipeline". The supplied source material observes that the historical practice of selecting only "fast-track" managers for leadership training, once or twice per career, is being replaced by tiered programmes available to any manager at appropriate points in their career.

Practice note: Design considerations for formal training Per the supplied research, the effectiveness of a formal programme depends on how well it accounts for:

• Learning theory — adult learners need relevance, not lectures
• Specific learning objectives — vague goals produce vague outcomes
• Trainee characteristics — a programme for engineers promoted to team lead is not the same as one for senior programme directors
• Practical constraints — cost, release time, geographic dispersion, security clearance levels

In the Australian defence ecosystem, the tiered architecture typically looks something like this:

2. Training Methods — Matching the Method to the Competency

Not all content is best delivered the same way. The supplied source lists five headline methods: lecture and discussion, role playing, behavioural role modelling, case analysis, and simulations. The supplied research both stress that method selection must match the type of learning required:

Practice note — method-to-competency mismatch: Sending a new package manager to a two-day lecture on "conflict resolution" and expecting them to hold a hard line with a Tier-2 subcontractor the following Monday is a category error. Interpersonal skill under pressure is built by rehearsal with feedback, not by exposition. If you cannot role-play the behaviour, you have not learned it.

3. Learning from Experience — The 70% in Action

The supplied source material states plainly that much more is learned from experience than from formal programmes. The question then becomes: which experiences are developmentally potent, and how do you engineer them deliberately?

Research cited in the supplied source identified that developmental assignments share several features:

1. Unfamiliar responsibilities — the leader is pushed beyond their current capability envelope
2. High visibility — consequences of success and failure are seen by senior stakeholders
3. Strategic ambiguity — right answers are not pre-specified; judgement is required
4. Diverse stakeholder management — multiple interests must be balanced
5. Adversity exposure — the assignment includes real risk of visible failure

In a defence prime, these assignments are not accidental — they are curated. A good Capability Lead at a prime contractor or a major contractor keeps a mental map of the stretch opportunities in their portfolio and deliberately positions high-potential PMs into them.

4. Mentoring — The Informal Edge

The supplied source distinguishes mentoring sharply from coaching. Mentoring is a relationship in which a more experienced manager helps a less experienced protégé over an extended horizon. The supplied research identified two distinct functions that good mentoring performs:

Practice note: The two functions of mentoring

• Psycho-social function — acceptance, encouragement, counselling, role modelling; helps the protégé develop identity as a leader
• Career-facilitation function — sponsorship, protection, challenging assignments, exposure and visibility; helps the protégé progress in the organisation

Research consistently finds that mentoring correlates with faster career advancement and higher compensation. But a crucial nuance appears on the slide: informal mentoring is usually more successful than formal mentoring programmes. Forced pairings, calendar-driven catch-ups, and HR-templated conversations tend to produce low-trust, low-value interactions. The best mentoring happens when a senior leader chooses to invest in a junior leader because they see something in them.

Practice note: Demographic friction in mentoring the supplied research note that age, gender, and race differences between mentor and protégé can create friction — particularly in industries (like heavy engineering and defence) that are historically homogeneous. A strong mentoring programme actively addresses this by widening the pool of available mentors and training mentors in cross-cultural and cross-generational mentoring competencies.

5. Executive Coaching — The Targeted Intervention

Where mentoring is broad and relational, executive coaching is narrow and transactional. Coaching is typically:

• Short-to-medium horizon (3–12 months)
• Focused on specific behavioural or performance goals
• Delivered by a paid external professional (not a colleague)
• Oriented toward current or imminent leadership responsibilities

The supplied source material identifies several advantages over formal training: convenience, confidentiality, flexibility, and personal attention.

In a major defence environment, executive coaches are most commonly engaged at two transition points:

Practice note: Evidence base the supplied research is careful to note that the empirical research on executive coaching effectiveness remains thin. Much of the reported benefit is self-reported by participants; rigorous controlled studies are rare. Coaching is useful — but it is not magic, and it is not a substitute for genuine experience.

6. Simulations — Safe Rehearsal for Dangerous Decisions

Simulations force trainees to analyse complex, ambiguous problems and commit to decisions — then experience the consequences. In heavy engineering and defence, simulations range from:

• Tabletop wargames — stakeholders role-play a schedule-slippage scenario
• Integrated system rehearsals — full test-and-acceptance dry runs before a platform delivery milestone
• Digital twin exercises — programme schedule stress-tested in a simulation environment
• Leadership assessment centres — multi-day scenarios used as both development and selection tool

The value of simulation lies in its psychological safety: you can get a decision badly wrong and nobody dies, no schedule slips, no penalty clauses trigger. Mistakes in simulation are cheap; mistakes on a live complex subsystem programme integration milestone are catastrophic.

Supporting the Training — Before and After

One of the most reliably ignored findings in adult learning research is that the training event itself is the smallest part of the intervention. What happens before and after determines whether the learning transfers to job performance. The supplied source material breaks these into two lists:

Before training — preparing the ground

After training — cementing the transfer

Practice note: The transfer-of-training rule Research consistently shows that without deliberate before-and-after reinforcement, roughly 70–80% of what is learned in a classroom is lost within weeks. The training event may cost $5,000 per head; the reinforcement costs almost nothing — yet most organisations invest in the expensive part and skip the cheap part.

The Systems Perspective — Why Isolated Programmes Fail

The supplied source material makes a subtle but critical point: leadership development succeeds only when top executives take a systems perspective. That is, development must be connected to — and reinforced by — the other human capital systems of the organisation:

An organisation that trains its project managers to be collaborative, coaching-oriented leaders but then promotes only the ones who hit cost and schedule numbers regardless of how they treat their teams has a broken system. The training is telling people one thing; the reward system is telling them the opposite. The reward system always wins.

In an acquisition authority-governed, applicable contract framework-contracted environment, this systems view becomes especially important because the external compliance regime imposes its own pressures — competency evidence requirements, security clearance cycles, export-control authorised constraints on who can work on what — and the leadership pipeline must be engineered to satisfy those external demands while still producing leaders who can actually lead.

Self-Development — The Part Only You Can Do

The final move in the supplied source material is a list of self-development guidelines, and it matters because no organisation will develop you as much as you can develop yourself. The supplied source — Drawing on the supplied research — offers the following guidelines:

Practice note: Self-development guidelines

• Develop a personal vision of career objectives
• Seek appropriate mentors
• Seek challenging assignments
• Use social networks to check developmental opportunities
• Improve self-monitoring
• Seek relevant feedback
• Learn from mistakes — analyse them rather than bury them
• Learn to view events from multiple perspectives
• Be sceptical of easy answers

The last point deserves emphasis. The discipline of project management is saturated with confident prescriptions — "adopt Agile", "kill the PMO", "use SAFe", "go full formal project method". The mature leader has learned to treat every such prescription as an hypothesis to be tested against the specific context, not a commandment to be obeyed.

Pitfalls — Common Mistakes in Leadership Development

Practice note: Pitfall 1 — Treating training as the deliverable Counting training hours or certifications as evidence of development. The deliverable is changed behaviour on the job, not seat time in a classroom.

Practice note: Pitfall 2 — Formal-only mentoring programmes Pairing mentors and protégés via an HR algorithm and expecting relational magic. Informal, chosen mentoring outperforms assigned mentoring almost every time — design programmes that enable self-selection, not mandate pairing.

Practice note: Pitfall 3 — The fast-track fallacy Identifying a small cohort of "high potentials" at age 28 and pouring development resources into them exclusively. This both demotivates the 90% excluded and assumes prescient judgement about 20-year career trajectories. Modern tiered programmes offer opportunities to anyone ready at the relevant career point.

Practice note — skipping transfer support: Running a polished three-day workshop and then doing nothing to reinforce the learning afterward. You may spend most of the budget on a small share of the transferable value.

Practice note: Pitfall 5 — Ignoring the system Training people in collaborative, servant-leadership behaviours while promoting only aggressive command-and-control types. The reward system is the real curriculum.

Practice note: Pitfall 6 — Outsourcing accountability to HR Treating leadership development as "an HR programme" rather than a core line-management accountability. In defence primes that do this well, every senior manager has a development portfolio of junior leaders they are personally accountable for growing.

Practice note: Pitfall 7 — Skipping self-development Waiting for the organisation to develop you. It will not — at least, not enough. The 70-20-10 model implies that even perfect organisational support accounts for only part of your growth. The rest is on you.

Key Takeaways

1. Leadership development is a systems-level capability investment, not an HR programme or a training budget line.
2. Competencies are built through three channels: formal training, developmental activities, and self-help — roughly mapping onto the 70-20-10 model of experience, relationships, and formal learning.
3. Training method must match the learning target: lectures for facts, cases for analysis, role-plays for interpersonal skill, simulations for judgement under uncertainty.
4. Experience dominates development — the deliberate curation of stretch assignments is the single most powerful intervention available to a capability lead.
5. Mentoring performs both psycho-social and career-facilitation functions; informal mentoring usually outperforms formal programmes.
6. Executive coaching is narrow, targeted, and most useful at key transition points — but the empirical evidence base remains thin.
7. Before-and-after reinforcement determines whether training transfers to the job; without it, 70–80% is lost within weeks.
8. Top-executive systems perspective is essential: development must align with selection, appraisal, succession, and strategy — or the reward system will override the training.
9. Self-development is non-negotiable — no organisation will develop you as much as you can develop yourself.
10. In heavy engineering and defence programmes with horizons measured in decades, the leadership pipeline is a capability asset — starve it, and you starve the programme.

Reflective Practice Prompts

The supplied source's guided review asks you to develop responses to the following — ideal for structured reflection in your a personal knowledge base:

Practice note: guided review prompts

1. What leadership development approaches exist in your organisation (or one known to you)? Map them onto the 70-20-10 framework — where is the investment concentrated?
2. Draft a personal development plan for the next 24 months. What stretch assignment are you targeting? Who is your intended mentor? What single formal qualification would unlock access to the stretch assignment?
3. Which of the seven pitfalls above does your organisation most suffer from — and what single change would begin to address it?

Integrated Insights from the Supplied Source Set

The archive contains several overlapping treatments of this subject. The following sections retain the most distinct practical material while avoiding a second article that teaches the same core topic.

The "Why": Leadership Development as a Strategic Capability

Integrated source perspective — Source 49: This section preserves distinct material from an overlapping source treatment.

In the 2020s, the Australian defence industry is facing what the sector strategy review 2023 and the subsequent 2024 National Defence Strategy both flagged as the single largest constraint on sovereign capability: not steel, not silicon, but people capable of leading complex programmes.

Consider the scale of what is coming:

• The complex naval-platform programme at major shipyard requires thousands of skilled workers and hundreds of project leaders across a 30-year build cycle
• multinational defence partnership Pillar 1 (nuclear-powered submarines) is projected to need a multi-generational workforce that does not yet exist
• major delivery organisations are competing for the same small pool of project management plan-certified, security-cleared, engineering-literate project leaders

Practice note: Core principle Leadership development is not about producing "more leaders." It is about building a sustainable pipeline of capability that matches the complexity of the work the organisation has committed to delivering.

The business case writes itself. The national management capability review flagged Australia's management capability gap three decades ago. The gap has not closed; it has migrated into defence, where the consequences of weak project leadership are measured in billions of dollars of write-offs and years of schedule slip.

Conceptual Knowledge programmes

Integrated source perspective — Source 53: This section preserves distinct material from an overlapping source treatment.

A standard approach to leadership development is to learn useful concepts about leadership. Conceptual knowledge is very important because it alerts the leader to information that will make a difference in leadership.

Practice note: Why concepts still matter in the age of "just do it" A leader without conceptual frameworks cannot name what is happening in front of them. The difference between a rising PM and a stuck one is often the ability to recognise "this is a distributive negotiation becoming integrative" — and act accordingly. You cannot act on what you cannot see, and you cannot see what you cannot name.

The supplied five-practice leadership programme is cited as an exemplar — it is essentially a structured way of teaching five useful concepts (Model the Way, Inspire a Shared Vision, Challenge the Process, Enable Others to Act, Encourage the Heart) and then asking leaders to apply them.

For project managers, conceptual knowledge also maps directly onto:

• Contingency theories (Contingency Theories of Leadership) — leader-situation fit model, readiness-based situational leadership model, Path-Goal
• Transformational leadership (Charismatic and Transformational Leadership) — the supplied research
• Power and influence bases (Power and Influence) — power-bases framework
• Team development models — five-stage team-development model, the supplied research

Applying the Guidance as a Controlled Practice

Use this subject as a decision aid, not as a label applied after the event. Start by defining the delivery problem, the people affected, the authority available and the consequences of a poor decision. Record assumptions before selecting an intervention. That simple discipline makes later review possible and prevents a preferred leadership style from being treated as the answer to every situation.

Six-Step Application Cycle

1. Define the trigger. State the decision, behaviour, team condition or delivery risk that requires attention. Separate observation from interpretation.
2. Map the context. Identify the project phase, task uncertainty, dependencies, stakeholder interests, time pressure, team capability and formal authority.
3. Choose a proportionate response. Select the smallest intervention capable of improving the condition. Explain why it fits the evidence and what alternatives were rejected.
4. Agree ownership and boundaries. Make decision rights, escalation points, review dates and non-negotiable safety or ethical limits visible to the people involved.
5. Act and observe. Monitor both delivery indicators and human signals such as challenge, information sharing, participation, trust and follow-through.
6. Review and adapt. Compare the result with the original intent. Retain, adjust or stop the intervention, and capture the learning for the next phase.

Evidence and Verification

Evidence should be proportionate to the project's risk and governance needs. A short decision note may be sufficient for a routine team adjustment; a high-consequence change may require sponsor approval, formal consultation, controlled records and a scheduled assurance review. Documentation must support judgement rather than replace it.

Review Questions

• What observable condition are we trying to change, and how will we know if it improves?
• Whose perspective is missing from the diagnosis or decision?
• Are authority, accountability and capability aligned, or are we asking someone to own an outcome they cannot control?
• Could the intervention suppress challenge, conceal risk or create dependency on one individual?
• What evidence will trigger escalation, adaptation or closure?

Practice boundary: Frameworks in this article organise thinking; they do not guarantee performance. Project context, contractual obligations, safety duties, workplace requirements and approved governance remain controlling.