Framework
The MAX Potential Approach
The five stages, the development loop that runs inside them, and the relationship between the two.
Purpose
Why this document exists.
MAX Potential exists to design environments where people and organizations perform better.
Performance is too often treated as a matter of individual effort, talent, or willpower. Those things matter, and they are not enough. People perform inside environments, and organizations perform through them. The conditions around people shape what they can see, what they can practice, what feedback they receive, what decisions they make, and what improvement they are able to sustain.
The practical question is:
What is the environment allowing, reinforcing, or preventing?
This document defines the approach used to answer that question and to translate the answer into better conditions for development and performance.
Core belief
Performance is shaped by environment.
The environment includes:
- expectations
- roles
- resources
- constraints
- feedback loops
- decision rhythms
- development pathways
- access to useful information
None of these replace ability, effort, or talent. They determine whether ability, effort, and talent can be expressed consistently.
How we work
The five stages.
- 01
See the current environment
Understand what exists today.
This includes what is working, where friction exists, what people experience, how decisions are made, and what constraints shape behavior. The goal is not to judge the environment from the outside. The goal is to see it clearly enough to understand why current outcomes are happening.
- 02
Design what comes next
Clarify the next meaningful step.
This means identifying the desired outcome, the capabilities required, the priorities that would create the most useful progress, and the opportunities for improvement. Not every problem is the most important problem. Not every improvement requires the same kind of change.
- 03
Design the environment
Create the conditions that support success.
This may include clearer expectations, better roles, stronger rhythms, shared frameworks, improved feedback loops, development pathways, decision tools, or new ways of organizing work. The point is not to add complexity. The point is to make better performance more repeatable.
- 04
Put it into practice
Translate the design into daily reality.
An environment is not changed by a document alone. The design has to become behaviors, routines, tools, coaching, communication, and measurement. This is where the work moves from idea to operating practice.
- 05
Continue growing
Use evidence and reflection to keep improving the environment.
No environment is finished. People grow, circumstances change, and new information appears. Improvement is treated as an ongoing process of learning, deciding, and adapting rather than as a project with an end.
The development loop
Intention → Action → Reflection → Decision → Direction
Inside every environment, improvement depends on a human development loop. The five stages build the environment. This is what happens inside it once built.
- 01
Intention
What are we trying to improve, become, or accomplish?
The step most often assumed rather than stated. An intention that only exists in someone's head cannot be acted on by anyone else.
- 02
Action
What do we actually do, practice, test, or attempt?
The distance between what an organization intends and what it does is usually where the environment is exerting its influence.
- 03
Reflection
What happened? What did we notice? What worked? What did not?
Reflection requires that something was observed closely enough to be reflected on. Environments that do not capture what happened cannot perform this step, however much they value it.
- 04
Decision
What adjustment do we make?
The critical step. Reflection creates awareness. Decision creates movement. Without decision, reflection becomes observation. With decision, reflection becomes change.
- 05
Direction
Where do we go next?
Direction turns the decision into the next priority, the next behavior, the next practice, or the next design choice.
The relationship between the two
One creates the conditions for the other.
The approach creates the environment where the internal development loop can happen more effectively. A poorly designed environment prevents useful reflection and decision-making. A well-designed one makes clear intent, meaningful action, useful feedback, better decisions, and improved direction more likely.
The approach creates the environment. The loop is what happens inside it. Neither works without the other.
How it is applied
One institution, expressed through environments.
MPBC
The applied environment. Development is practiced directly, with real players, coaches, teams, and competitive constraints.
MPPD
The development intelligence system. It captures observations, preserves context, organizes evidence, supports decisions, and makes development more repeatable.
The Library
The accumulated knowledge. It preserves the ideas, frameworks, lessons, and evidence that come out of the work.
Advisory
The approach applied to external organizations, helping leaders see their current environment, design what comes next, build better conditions, put those conditions into practice, and continue growing.
What this document is not
Boundaries.
This is not a pitch, a pricing model, or a technical specification. It is the canonical methodology document: the approach behind MPBC, MPPD, the Library, and Advisory. Where an implementation and this document disagree, this document is the one that is correct.