Advisory

The starting condition

What leaders describe when they get in touch.

Almost nobody calls to say their environment needs designing. They call because something specific has stopped working and the usual responses have not fixed it. Underneath the particulars, the same short list keeps appearing.

• Knowledge lives with individuals
• Processes are inconsistent
• Expectations are unclear
• Feedback is incomplete
• Decisions depend too heavily on memory or personality
• Improvement is difficult to measure

What makes these worth an engagement rather than an internal fix is that they tend to resist the obvious remedy. Hiring a stronger person into an environment that produced the problem usually reproduces it with a different name attached, which is expensive to learn twice.

How we work

The method, applied to an organization.

No predetermined answer is brought into the room. The design follows the diagnosis, which means the first stage is the one that determines whether any of the rest is worth doing.

1. 01 See the current environment
2. 02 Design what comes next
3. 03 Design the environment
4. 04 Put it into practice
5. 05 Continue growing

What the first stage consists of

• Conversation with leaders, with teams, and with the people doing the work
• Observation of how decisions actually get made, rather than how they are described
• Review of what has already been attempted and what became of it
• Pattern recognition across roles, functions, and recurring problems

The method itself

A worked example

What an assessment looks like when it is finished.

This is the assessment that produced MPBC's development environment, and it was run on our own organization rather than a client's. It is published because it is the one that can be documented completely, and because the shape of it is the same regardless of whose environment is being read.

1. 01

   Situation

   A varsity basketball 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. The intent was not in question. The capacity to execute it was.

2. 02

   Observation

   Practices ran about ninety minutes. Game schedules produced three-game weeks, and practice time went to preparation, recovery, and whatever the next opponent required. The methodology was new to roughly twenty-four players and to coaches at several levels at once. Then the varsity assistant left at the start of the season and two new JV coaches arrived. Development plans, observations, practice priorities, individual interventions, team objectives, staff communication, and coaching alignment were all being held by one person.

3. 03

   Assessment

   The constraint was not commitment, and it was not coaching quality. The level of development the program wanted had exceeded what memory, conversation, and manual process could carry. That is an environment condition rather than a personnel one, which matters because it changes what a fix looks like: no amount of additional effort from the head coach would have resolved it, and replacing anyone would have reproduced it.

4. 04

   Design response

   Development had to become something the organization ran rather than something a person carried. That meant preserving development context outside anyone's memory, connecting season objectives through to individual practice, building feedback loops that could answer whether a player had actually advanced, and giving coaches at every level one shared development framework instead of several private ones.

5. 05

   Evidence

   The program operates the environment today. Development context is held by the program rather than by one coach, coaches across levels work from the same framework, and observations recorded during the work connect to the decisions made about what happens next. What it has not yet shown is operation by an organization that did not build it.

Developed during the 2024–25 varsity season. The case study in full

Outputs

The output is an operating environment.

What the work produces depends on what the environment needs, so this is a description of the kind of thing rather than a package. None of it is a recommendation to consider at a later date. It is what the organization then runs on.

1. A record of how decisions actually get made

   Who decides, on what information, and how long it takes for the result to come back to them. Most organizations have never written this down, and the gap between the described process and the observed one is usually where the constraint sits.

2. The places where knowledge depends on individuals

   Named specifically: which judgments live in one person's head, what would be lost if they left, and which of those are worth making institutional rather than tolerating.

3. Development that repeats without supervision

   A way for people to be developed that produces similar quality regardless of who is running it, so that adding staff adds capacity instead of adding variation.

4. Feedback that arrives while it can still change something

   Mechanisms that tell someone whether what they did worked, close enough to the work that the answer is still useful. Late feedback is a record. Timely feedback is a decision.

5. Ownership that is clear enough to act on

   Who is responsible for what, and who has the authority to change it. Ambiguity here is usually mistaken for a motivation problem.

Not a report. Not a deck.

Engagement models

Three ways the work proceeds.

1. 01

   Assessment

   Stage 01

   The normal first step.

   A clear reading of the current environment: what is working, where the constraint actually sits, and which opportunities would create the most change.

   Organizations that need clarity before deciding what to build or change.

   Bounded, with a defined scope and a defined end. Time with leaders, teams, and the people doing the work, followed by a written reading of the environment the organization keeps.

2. 02

   Design

   Stages 02 and 03

   The frameworks, pathways, rhythms, and decision structures the next stage of performance requires.

   Organizations that already know improvement is needed and are ready to build the conditions for it.

   Project-based and scoped to what the assessment identified. Built collaboratively rather than delivered, because an organization that did not build its environment cannot maintain it.

3. 03

   Partnership

   Stages 04 and 05

   Implementation support, measurement, and continuous refinement as the environment reveals more.

   Organizations pursuing meaningful change across people, teams, or programs.

   Ongoing. The work depends on presence and direct observation, which is not something that can be delegated or run at volume, so the number of these that can exist at once is small.

How it begins

Three steps, in order.

1. 01 A conversation about the environment
2. 02 A scoped assessment proposal
3. 03 The assessment

Nothing here commits an organization to the stage after it. An assessment is designed to be worth its own cost, so ending there is a legitimate outcome rather than a failed sale. An organization that understands its own environment clearly may not need anything further, and it is better for everyone that this is decided after the reading rather than before it.

Start with your environment.

A first conversation is about what is happening in your organization, not about a proposal. If there is a fit, the next step is an assessment with a defined scope, a defined end, and a written reading of the environment you keep whether or not the work continues.

Begin a conversation