The problem
How does development become a system rather than a person-dependent responsibility?
When development depends on a person, it works exactly as well as that person's attention allows. What they notice gets addressed. What they do not notice does not exist. The knowledge lives in their memory, the standard lives in their judgment, and both leave when they do.
It also does not grow in the ordinary way. Adding people does not add capacity, because each new person develops their own way of doing the work. Quality then varies by who is present, and the organization has no way to tell the difference between someone doing the work well and someone simply doing it differently.
Organizations tolerate this for a long time, and reasonably so. It works. A capable person carrying the responsibility produces real results and the arrangement costs nothing to set up. The failure, when it comes, is sudden rather than gradual: the arrangement holds until that person is stretched past their limit or leaves, and then everything they were holding is gone at once.
Applied in competitive youth basketball
This was worked out in competitive youth basketball, which is a useful place to test the question rather than a limitation on it. The cycles are short, so a design either holds within a season or does not. Observation is continuous and outcomes are visible. Staff turnover is high and often arrives mid-season. The results are public, which removes the option of grading your own work.
Why it needed to exist
The breaking point.
The program had moved past installing systems and running practices toward individual development: understanding each player's strengths and gaps, building development plans, and aligning daily practice with long-term improvement. That intent ran into the operating reality of a season. Practices were roughly ninety minutes. Game schedules produced three-game weeks. Practice time was consumed by preparation, recovery, and whatever the next opponent required. The methodology was new to about twenty-four players and to coaches at multiple levels at the same time.
Then the varsity assistant left at the beginning of the season and two new JV coaches entered the program. Everything the system depended on was being held by one person: development plans, observations, practice priorities, individual interventions, team objectives, staff communication, coaching alignment. The issue was not commitment. It was capacity. The level of development the program wanted had exceeded what memory, conversation, and manual process could carry.
The environment
What conditions were created.
- Competition, training, feedback, and reflection connected rather than run separately
- Situations that require decisions, not only repetition
- Close and continuous observation while the work is happening
- Feedback that compounds across a season instead of resetting
What was deliberately avoided is as informative as what was built. Isolated skill instruction was not the answer, even though it is easier to run and easier to measure, because it does not produce people who can read a situation. Nothing was introduced that required a coach to do more during a session than they were already doing. A design that only functions in a calm week is not a design. It is a good intention with a schedule attached.
What was built
The system created.
- An observation practice the organization runs, not a person
- Evidence captured during the work rather than reconstructed after it
- Individual development planning tied to what was observed
- A cadence for adjusting when the evidence changes
These are things the program operates, not features that shipped. The distinction matters: an observation practice exists when coaches at three levels are using it during a week with three games, not when it has been explained to them. What the program gained was a shared way to see development and act on it, and that is what allowed the responsibility to move from one person to the organization.
Evidence
What demonstrates it works.
The environment is in operation. Development context is held by the program rather than by one coach, coaches across levels work from the same development framework, and observations recorded during the work connect to the decisions made about what happens next.
What is demonstrated
- Development context survives a change in coaching staff
- Coaches at multiple levels operate from one shared development framework
- Observation recorded during the work rather than reconstructed afterward
- Development decisions made from evidence rather than from recollection
What is not yet demonstrated
- Operation by an organization that did not build it
- Application outside youth sport
- An isolated effect on competitive results
- Replication across multiple independent organizations
Developed during the 2024–25 varsity season.
Transferability
Where else this problem lives.
Person-dependent development is the same condition wherever capability has to pass from one person to another. The domain supplies the vocabulary and the constraints. The structure of the problem does not change: one person holds the standard, the standard is invisible to everyone else, and the organization discovers what it was depending on only after it is gone.
- Teacher development across a district
- Staff development where quality varies by supervisor
- Coaching and apprenticeship pipelines
- Any organization where capability is transferred person to person
If you want to go further
The operating club, with its programs, teams, training, and registration. This link leaves the institutional site.
Where does your organization depend on a person?
The question is not whether you have capable people. It is what happens to what they know when they are not there.