The Architecture of Leadership
Exploring the systems that shape the practice of leadership
Who Is Responsible for Development?
Why growth stalls when ownership is assumed but never defined
Development is rarely missing from the conversation, but often missing from the work itself. Leaders are expected to support it, employees are expected to own it, and organizations position themselves as enabling it. This framing is directionally correct, but in practice, it often lacks clarity. When responsibility is shared without being defined, it becomes uneven. Over time, development is something everyone references and few people consistently drive.
Early in a career, development is more structured. Expectations are clearer, feedback is more frequent, and the path forward is easier to interpret. Individuals are told what to focus on, how they are progressing, and where improvement is needed. As responsibility increases, that structure begins to fade. Development becomes more ambiguous, and individuals are expected to navigate it with less explicit guidance.
From the organizational perspective, this shift often feels appropriate. As individuals grow, they are expected to take more ownership of their trajectory. The assumption is that capability includes the ability to self-direct development. In theory, this creates autonomy. In practice, it often creates a gap between expectation and support.
This gap becomes visible in how development conversations are experienced. In many environments, they remain high-level and recurring. Individuals are asked where they want to grow, what they are interested in, and how they see their future. These conversations create alignment at a surface level, but they do not always evolve into concrete changes in how work is assigned or how capability is built over time.
Within a group of mid-level employees, this dynamic became visible during a series of performance and development discussions. Employees consistently expressed interest in taking on more strategic work. Leaders were supportive of that direction and encouraged them to continue developing. Over the following months, however, the nature of the work remained largely unchanged. The same individuals continued to execute within their existing scope while being told they were on a path toward something broader.
Internally, this felt like stagnation. The conversations suggested growth, but the experience of the work did not reflect it as such. From the leadership perspective, the intention was positive with recognition of potential and a desire to support development. The missing piece was not intent, rather, the translation of intent into how work was structured and assigned.
Responsibility for development becomes unclear when individuals assume expressing interest is enough to prompt change. Leaders may assume that encouragement is sufficient to support growth. Organizations may assume that providing resources or programs creates development. Each of these assumptions contains part of the responsibility, but none of them are sufficient on their own.
Over time, this creates a pattern where development is discussed but not consistently experienced. Individuals continue to perform, but their growth becomes dependent on individual initiative rather than structured opportunity. Leaders support development in principle, but are constrained by immediate business needs that prioritize execution. The system begins to favor short-term delivery over long-term capability, often without explicitly acknowledging that tradeoff.
This dynamic is reinforced by how work is distributed. High performers are often given more of the same work because they can be relied upon to deliver. Opportunities that would stretch capability are either delayed or assigned based on immediate need rather than developmental value. As a result, individuals become more efficient within their current scope while remaining underexposed to the work that would expand it.
In another environment, this pattern showed up in how leadership roles were filled. Internal candidates were frequently encouraged to apply for open positions, with feedback that they were close but not yet ready. At the same time, external candidates were brought in with the experience that internal candidates had not yet been given the opportunity to develop. From the outside, this appeared to be a gap in readiness. From within the system, it reflected a lack of structured pathways to build that readiness.
Situations like this are not the result of individual failure. They are the result of how development is designed, or not designed, within the organization. When development is treated as an expectation rather than a system, it becomes dependent on timing, visibility, and individual advocacy. Those who are more comfortable navigating ambiguity or advocating for themselves may progress more quickly, while others remain in place despite strong performance.
This is where the question of responsibility becomes more practical. Individuals are responsible for engaging in their own development, but engagement requires visibility into what development actually looks like. Leaders are responsible for supporting development, but support requires translating intent into opportunity. Organizations are responsible for creating pathways, but pathways require alignment between development and how work is structured.
When any part of this system is unclear, development becomes uneven. It is experienced differently across teams, roles, and individuals. Some people are exposed to opportunities that accelerate growth, while others remain in roles that reinforce existing strengths without expanding them. Over time, this unevenness becomes more visible in how capability is distributed across the organization.
The impact is not immediate. In the short term, work continues to move forward. High performers remain productive, and teams meet their objectives. Over time, however, the absence of structured development begins to affect how the organization evolves. Leadership pipelines become thinner, internal mobility slows, and reliance on external hiring increases. The organization begins to solve for capability gaps reactively rather than building them intentionally.
Addressing this does not require removing individual ownership. It requires making responsibility explicit and connected to how work actually happens. Development is not separate from execution. It is embedded in the type of work individuals are given, the level of context they are exposed to, and the expectations placed on how they contribute.
For leaders, this often means making more deliberate decisions about how work is assigned. It involves identifying where opportunities exist to stretch capability and being intentional about who is exposed to them. It also requires being clearer about what readiness looks like and how individuals can move toward it through specific experiences rather than general guidance.
For individuals, it requires moving beyond expressing interest toward understanding how development is built through work. This includes seeking feedback that connects performance to capability, asking for exposure to different types of work, and recognizing that growth often requires engaging with discomfort and uncertainty rather than waiting for readiness to be confirmed.
The goal is not to create a perfect system where development is fully predictable. It is to reduce the ambiguity that makes development dependent on interpretation. When responsibility is clear and connected to how work is structured, development becomes more consistent. When it is not, it becomes uneven, and growth stalls in ways that are difficult to diagnose from within.
Questions Worth Sitting With
- How clearly is responsibility for development defined across individuals, leaders, and the organization?
- Where are development conversations happening without corresponding changes in how work is assigned?
- What experiences are required for growth that are not currently being made available?
- How often is readiness evaluated without first creating the conditions to build it?