Better outcomes begin with the decisions that produce them.
Organizations are adaptive systems. Their results emerge from thousands of decisions shaped by information, incentives, constraints, workflows, skills, and feedback. Our work starts there.
A pragmatic approach to complex problems.
The framework is deliberately practical. It is not a rigid methodology. It is a way to structure analysis, surface the variables that matter, and build a system that can learn.
Define the desired state
Separate the immediate issue from the outcome that actually matters. If fixing the symptom does not move the system toward the goal, it is not the right problem.
Model the system
Map the decisions, people, information, incentives, constraints, dependencies, and time scales that shape the current outcome.
Design the mechanism
Change the surrounding system—workflow, decision support, measures, incentives, or governance—so the desired action becomes easier and more reliable.
Fit the context
A technically elegant design that cannot be implemented is not a good design. Resources, skills, values, workload, and administrative support matter.
Measure and update
Treat the intervention as a hypothesis. Observe what happens, update the model, and revise the system as new information emerges.
The decision is the unit of design.
Before building a dashboard, workflow, policy, model, or AI tool, define the decision it exists to improve.
Who makes the decision? What information do they need? How frequently do they make it? What uncertainty remains? What constraints matter? What action follows? What happens when the outcome is different than expected?
Those questions turn analytics into decision support, strategy into an operating system, and feedback into organizational learning.
Use the scale that matches the problem.
The same outcome can look very different depending on where you stand.
A frontline performance problem may be a training issue. It may also be a workflow problem, an incentive problem, a resource constraint, a policy artifact, or the predictable result of a payment model. Good analysis moves between levels rather than assuming the nearest cause is the most important cause.
TRL uses multiple models and levels of analysis to avoid solving the wrong problem well.
No model is final.
Complex organizations change while we are trying to change them.
We therefore treat assessment, strategy, and implementation as iterative. Good systems create regular feedback about performance, implementation, and context so leaders can update decisions rather than defend yesterday's plan.
Have a problem that refuses to stay inside one box?
Those are usually the problems worth mapping.