Manager & Leader development is ONLY through developing Others & System.

The most reliable way leaders are made is not by being selected, but by being exercised. Across research and lived practice, one conclusion keeps returning: adults develop fastest acknowledges when growth is anchored in real work, shaped by meaningful challenge, and converted into learning through reflection and feedback. In organizations, this has a simple implication. Individual development does not happen in isolation. It happens by developing others and, through that act, developing the system that those others operate inside. That is why manager and leader development is best understood as an enabling loop. An enabling loop builds capacity by repeatedly turning experience into better perception, better decisions, and better outcomes that hold.

This is a strong moment for organizations because our learning infrastructure is maturing. Most enterprises can now capture knowledge at scale: codify playbooks, document SOPs, build academies, map skills, and track completions. This matters. It means Knowledge acquisition is no longer the primary constraint. The frontier has moved. The next leap is conversion: converting captured knowledge into proficiency that holds under variation, and then converting repeated proficiency into System Sense the organization’s capacity to notice patterns early, interpret weak signals, and redesign work without losing reliability. In other words, the evolution is from knowledge capture to performance stability to adaptive intelligence.

This is the same vein as Perception Shapes Performance: performance improves when perception improves, and system performance improves when shared perception improves. Experience-based growth strengthens when developmental challenge is real, learning orientation is active, and feedback is available. Structured reflection accelerates this because it turns experience into explicit learning rather than private intuition. Coaching strengthens the bridge between knowing and doing. Manager capability grows through the developmental quality of assignments and exposure, not only through “potential tags.” And system sense is not an attribute in one person it is a property the system earns as shared perception matures. Leadership identity also forms socially, through repeated interaction, so development happens in the stream of work, not only in classrooms.

Now, enterprise learning has a naming problem. We borrow heavily from education, psychology, philosophy, neuroscience, and social science. Borrowing is useful, but it becomes expensive when concepts remain intellectually sound and operationally distant. Borrowed language becomes valuable only when translated into managerial moves what to observe, what to ask, what to reinforce, and what to redesign.

A practical anchor is the performance architecture: Capability = Ability X Motivation X Environment and operationally: Ability X Task X Context = Outcome. Ability is what the performer brings knowledge, skill, and attitude. Task is what work requires ;inputs, process, activity, and output. Context is what shapes execution culture, social dynamics, legacy constraints, and the actors in the system. Outcome is what must hold over time impact on self, others, and the system.

But there is a missing layer: perception. Ability being present does not guarantee performance being present because performance is also a function of how a person sees reality. A useful way to make this visible is the distinction between Self, Self-Concept, and Synthesis. Self is what comes naturally default tendencies. Self-Concept is the belief about how one must adapt to succeed in the current environment. Synthesis is how one actually behaves at work the emergent result of Self meeting Self-Concept inside real task and context constraints.

This is why readiness is not only having knowledge and skill. Readiness is the ability to perceive and connect Self, task, output, and outcome. A learner is high readiness when they can see their own capability and limits, what the task is truly asking for, what good output looks like, and the difference between the outcome expected and the outcome produced when output meets real context. When perception becomes complete, choices become intentional rather than reactive, and performance stabilizes.

At any level of performance, two capacities matter. Cognition is the ability to perform—knowing what to do and how to do it. Metacognition is awareness of what, how, and why one is performing at that level especially awareness of the gap between Self, Self-Concept, and Synthesis, and how that gap shifts under pressure. As maturity increases, metacognition expands in horizon: from individual, to team, to system. That expansion is the mechanism of synthesis: the ability to re-cluster skills and judgments under variation so outcomes hold.

This lens becomes operational when we accept that learners exist in different readiness states. At the lowest levels, development need is high attitude and context are binding constraints. At the middle levels, self-concept and task perception become binding constraints. At the highest levels, the constraint is often system friction legacy rules, coordination design, decision rights, and process or tool drag.

Now we introduce a second lens that makes feedback easier to communicate without adding complexity: crystallized intelligence and fluid intelligence. Crystallized intelligence is accumulated knowledge and stabilized routines what the learner can recall and execute reliably because it is known, practiced, and structured. Fluid intelligence is reasoning under novelty pattern recognition, trade-off navigation, and adaptive judgment when the situation does not match what the learner already knows. In workplace terms, crystallized intelligence supports reliable output in stable conditions, while fluid intelligence protects outcome when context varies. Both matter, but they fail differently, and they require different feedback. If the gap is crystallized, the intervention is clearer standards, practice, and procedural stabilization. If the gap is fluid, the intervention is better sensing, better task framing, better trade-offs, and guided exposure to variation. If the gap is systemic, the intervention is redesign, not coaching.

Now we arrive at the manager’s role. The manager’s job is not only to direct execution but to enable synthesis helping the learner integrate ability with task demands and context so outcomes hold. The engine of this work is metacognition: helping the learner see what they are doing, why they are doing it that way, and what must change when context shifts. Practically, the manager runs four feedback loops.

Ability feedback: what the learner’s true strengths and gaps are, and how they perceive them. Task feedback: what the task truly requires, and how the learner is interpreting it. Output feedback: what good output looks like and whether the learner can deliver it reliably. and outcome feedback: what outcome was expected, what outcome occurred in reality, and why the gap exists ability limits, task misunderstanding, context constraints, coordination breakdown, or judgment trade-offs. This is where the manager must be sharp: output is the deliverable; outcome is the effect in context.

Here is the most important point. A manager’s people sense and system sense expand through the act of developing subordinates especially subordinates who are very different from them. If a manager only leads people who think like them, their leadership stays narrow. When they develop people with different strengths and different ways of sensing the task, they are forced to upgrade self-awareness, other-awareness, and system-awareness. Each enabling cycle becomes leadership formation. This is how managers become leaders: by repeatedly helping performance hold under variation, until they can see patterns and make meaning across the system.

If knowledge capture is the starting point, the system needs a conversion chain that upgrades perception at each stage. That is the enabler map. Learning Architects translate field signals into learnable structures. SMEs calibrate truth and edge cases. Trainers build schema. Facilitators build shared meaning. Coaches stabilize execution under pressure. Communities of practice stabilize competence socially. Workflow and performance support remove friction at the point of work. Managers stabilize outcomes in context. Appreciative enquiry reveals patterns without blame. Leaders turn insight into sensing and redesign discipline. When this chain is alive, learning stops being an event. It becomes a property of daily work.

Now we move from proficiency to capacity. Managers convert capability into outcomes. Leaders multiply capability by strengthening destination. Capacity = Capability (all functions) X (Destination-competence & System sense) leading to emergence. Capability remains ability times task times context. But leaders build destination. They build competence conditions—culture norms, social structure, legacy constraints, and where capability carriers sit in the system. And they build system sense metacognition, social sensing, pattern sensing, and system re-authoring. When destination strengthens, capability multiplies. Outcomes hold under variation, and emergence becomes possible.

At the team level, maturity moves through forming, storming, norming, and performing. Each stage demands a different kind of capacity, and building that capacity is simultaneously the leader’s own development because leadership is the craft of creating conditions under which a group can hold complexity while responding to the outside world. In forming, leaders create clarity and safety. In storming, they hold conflict and convert it into structure. In norming, they stabilize execution and shared meaning. In performing, they sustain performance under variation and scale learning through pattern sensing and redesign. Teams can move backward under disruption, so leadership capacity is the ability to diagnose the stage quickly and build what that stage requires, rather than applying one style everywhere.

And that brings us to the close. If we want to go from knowledge capture to system sense, we don’t need more labels. We need a conversion chain that upgrades perception schema, practice, coordination, outcomes, patterns, and redesign. Adding the language of crystallized and fluid intelligence helps communicate feedback because it makes the hidden difference visible: some gaps are about stabilizing what is known, others are about improving judgment under variation, and others are about redesigning the system so good performance becomes structurally possible. Development is the only reliable way to develop managers and leaders, because enabling others is the practice that builds pattern recognition, sensemaking, and system perception. A manager who does not develop subordinates may still deliver outputs, but their perception stays local. A manager who develops subordinates especially those unlike them builds the only capability that scales: people sense and system sense. And as leaders mature through building teams across forming, storming, norming, and performing in response to the outside world, they strengthen destination competence plus system sense so capacity multiplies and emergence becomes possible.

I’d love to hear your thoughts and perspectives feel free to share them in the comments or write to me. If there are any topics you’d like to explore further, I’m open to suggestions! selfnsystems@gmail.com.