When pilots first encounter the Core Competency framework — whether at a type rating, a CRM refresher, or a command course — it is almost always presented as a list. Nine competencies, each with its own definition, its own set of observable behaviours, its own column on the assessment form. The implication is that each can be developed, assessed, and improved in isolation.
That implication is wrong. And the gap between the list view and the systems view is one of the most consequential gaps in pilot professional development.
The nine competencies are not independent domains. They are deeply interconnected. A behaviour in one competency creates conditions in another. A failure in one propagates through the system. A pilot who develops only within individual competencies will plateau in ways they cannot easily diagnose — because the ceiling isn't within any single competency. It's in the connections between them.
You cannot lead effectively without communicating well. You cannot communicate well without SA. You cannot maintain SA without managing workload. The framework is not a list — it is a web.
The Nine Competencies
Before examining the connections, it helps to be precise about what each competency represents in operational terms.
Each one has its own observable behaviours — 77 in total across the framework. But when you map every behaviour to the behaviours in other competencies it supports or depends on, 231 distinct connections emerge. That is not a web of minor overlaps. It is a deeply integrated system where almost nothing operates in isolation.
The Core Relationships
Some connections are so fundamental that they operate as load-bearing architecture for the whole framework. Understanding them reframes how you think about your own development.
Leadership depends on Communication
Leadership is often framed as a quality of character — presence, authority, decisiveness. In the context of the flight deck, it is more usefully understood as a set of behaviours, and most of those behaviours are expressed through communication. A Captain who influences the crew's decision-making does so through how they communicate options, not through rank. A pilot who maintains assertiveness under pressure does so through the quality of their challenge, not through volume or seniority.
The connection runs both ways. Communication without leadership context is transmission without purpose. The briefing that simply recites the procedure, the callout that comes without clear intent, the update that no one acts on — these are communication failures that are actually leadership failures. The two competencies are functionally inseparable.
SA depends on Workload Management
Situational awareness is not a passive state that exists until something disrupts it. It is an active cognitive process that requires bandwidth — attentional resource — to sustain. When workload exceeds capacity, SA is the first casualty. The scan narrows. Peripheral information drops out. The mental model stops updating.
This means that workload management is not just an efficiency competency — it is an SA protection strategy. A pilot who plans and prioritises effectively before demanding phases, who manages tasks to preserve spare capacity, and who recognises and responds to workload saturation is actively protecting their situational awareness. The two competencies are not adjacent on a list. They are mechanistically linked.
Workload management is SA protection. Every task you defer or delegate during a high-workload phase is attentional bandwidth you are preserving for the picture.
Decision Making depends on SA and Knowledge
Sound decisions require two inputs: an accurate mental model of the current situation (SA) and the knowledge to evaluate options within it (Application of Knowledge). Remove either and the decision degrades. A pilot with excellent SA but insufficient systems knowledge may correctly perceive a problem and fail to identify the right solution. A pilot with deep knowledge but degraded SA may apply the correct procedure to the wrong diagnosis.
This is why the post-incident question "why did they make that decision?" so rarely has a simple answer. Decision failures almost always trace back to an upstream failure — in perception, in comprehension, in knowledge application — rather than a failure of judgement in isolation. The decision is the output. The inputs are what failed.
Professionalism underlies everything
Professionalism sits in a different relationship to the other competencies than they hold to each other. It is less a parallel domain and more a foundation. Self-awareness, integrity, commitment to standards, stress resilience — these aren't behaviours that operate alongside leadership or communication. They are the conditions under which all other competencies function reliably under pressure.
A pilot with strong technical SA and poor self-awareness will consistently overestimate the quality of their own picture. A pilot with good communication skills and low integrity will use them selectively. Professionalism is the substrate on which everything else is built, which is precisely why it is the hardest competency to develop through instruction alone.
Three Connections in Practice
Abstract connections become meaningful when you see them play out in real operational scenarios. Here are three chains drawn directly from the 231 connections in the HPP framework — each showing how a behaviour in one competency activates, enables, or depends on behaviours in others.
What This Means for Development
If the competencies are a system, then developing them as a list is structurally inefficient. Improving your communication in isolation will plateau when the constraint is actually your SA — because without an accurate picture, there is nothing useful to communicate. Improving your SA will plateau when the constraint is workload management — because without spare capacity, SA cannot be sustained.
Effective development means practising behaviours at the points where they connect. A briefing practice session that simultaneously works communication clarity, role clarity, and threat identification is building three competencies at once because the behaviours genuinely co-occur. A debrief habit that combines honest self-assessment (Professionalism), error acknowledgement (Leadership), and post-flight review (Decision Making) is not doing three things — it is doing one thing that happens to develop three competencies.
This is the insight behind the Connections feature in the HPP app — the ability to build practice chains across competencies based on the real connections in the framework, rather than developing each competency in the isolation that the list format implies. The 231 connections aren't a theoretical construct. They are the actual dependency map of high performance on the flight deck.
The pilots who develop most rapidly are not those who work hardest on their weakest competency. They are those who understand where their competencies connect — and practise at the junctions.