The discipline
Approach
What we mean by environment
An environment is the set of conditions people operate inside: expectations, roles, resources, constraints, feedback loops, decision rhythms, development pathways, and access to useful information.
At the level of an organization, the environment is what makes some behavior easy and other behavior expensive. It governs who sees what, how quickly feedback arrives, who is permitted to decide, and whether what was learned last month is still available this month.
At the level of one person's week it is narrower and more concrete. It is the conversation that does or does not happen, the observation that is or is not written down, the priority that is clear on Monday and unclear by Thursday, and whether anyone will notice the difference.
None of this replaces ability, effort, or talent. It determines whether ability, effort, and talent can be expressed consistently. Environment is also not culture, morale, or facilities. Culture is one of its outputs, morale is a reading taken from it, and facilities are a resource inside it. The word gets used loosely enough that most people assume they already know it, which is why the definition has to be stated before the method makes sense.
The work begins with one question:
What is the environment allowing, reinforcing, or preventing?
The argument
Why environments shape outcomes.
The quality of decisions determines the quality of outcomes. Better decisions come from better environments.
Performance is expressed through decisions. Recognizing a situation, understanding what it requires, and choosing a response is where ability turns into outcome. Those decisions are never made in isolation. They are made inside conditions that determine what information is available, how much time there is, what the person has seen before, and what happens to them if they are wrong.
This is why changing the person, the process, or the tool so often disappoints. Each is real work, and each treats a symptom of something none of them control. A capable person inside conditions that limit them will produce limited results, and replacing them produces the same results with a different name attached.
The method
How the work proceeds.
- 01
See the current environment
Understand what exists today.
- what exists
- what is working
- where friction exists
- what constraints shape behavior
The goal is not to judge the environment from outside. It is to see it clearly enough to understand why the current outcomes are the ones happening. That means talking to the people inside it, watching how decisions actually get made rather than how they are described, and reviewing what has already been tried and what became of it.
- 02
Design what comes next
Clarify the next meaningful step.
- desired outcomes
- required capabilities
- priorities
Not every problem is the most important problem, and not every improvement calls for the same kind of change. This stage produces clarity rather than a plan: what the actual constraint is, why it exists, what meaningful progress would look like, and what capability needs to exist next.
- 03
Design the environment
Create the conditions that support success.
- structures
- expectations
- rhythms
- feedback loops
- development pathways
The answer is usually different conditions rather than more effort. That might mean clearer expectations, stronger feedback loops, better operating rhythms, development pathways, or removing a constraint that no longer serves anything. The point is not to add complexity. It is to make better performance repeatable.
- 04
Put it into practice
Translate the design into daily reality.
- behaviors
- routines
- systems
- action
A design that stays a document changes nothing. It has to become behaviors, routines, tools, coaching, communication, and measurement before it is real. Practice is also where the design gets tested, and where the parts that looked right on paper get corrected.
- 05
Continue growing
Keep improving the environment from what it reveals.
- reflection
- evidence
- learning
- adaptation
No environment is finished. People grow, circumstances change, and better information arrives. This stage builds the organization's own capacity to keep improving the environment, so that improvement does not depend on the engagement continuing.
The stages are sequential. The work inside them is iterative.
The mechanism
Intention → Action → Reflection → Decision → Direction
The five stages build the environment. This loop is what happens inside it once built, wherever people are trying to get better at something.
- 01
Intention
What are we trying to improve, become, or accomplish?
- 02
Action
What do we actually do, practice, test, or attempt?
- 03
Reflection
What happened? What worked? What did not?
- 04
Decision
What adjustment do we make?
- 05
Direction
Where do we go next?
Reflection creates awareness. Decision creates movement.
Without decision, reflection is only observation. Organizations that reflect well and decide poorly produce a great deal of insight and very little change, which is a failure mode that looks like health from the inside. Decision is where awareness turns into movement, and it is the step most often left implicit.
Transferability
Why this applies across domains.
The approach operates on conditions, not on content. It carries no domain knowledge of its own. It does not know how to teach a jump shot, run a district, or design a curriculum, and it does not need to: that expertise already exists inside the organization. What the method supplies is the sequence of questions that turns existing expertise into an environment where it can be applied consistently.
So the domain changes and the questions do not. What is the environment allowing, reinforcing, or preventing? What is the actual constraint? What conditions would make the next stage possible? Those questions are as legible in a school system as on a court.
This is a property of the method rather than a hedge about its limits. A method carrying its own domain content has to be adapted, diluted, or argued about before it can be used anywhere new. One that operates on conditions transfers intact, and the organization keeps ownership of what it knows.
Boundaries
What this is not.
- Not a framework you purchase
- Not a training curriculum
- Not a culture program
- Not software
- Not one methodology applied identically everywhere
Applied
Where this has been put to work.
Two environments have been designed with this method and are being operated today. Each is documented as the problem it solved first, and the domain it happened to occur in second.
What is your environment allowing?
A first conversation is about your environment: what it currently allows, what it prevents, and what has already been tried. Nothing is proposed until that is understood.