September 2026
HFE™: how to synchronize a team that decides autonomously
Carlos Ocampo · Published: · Updated:
English translation of the original Spanish publication. Original dates, authorship and documentary images are preserved.
When more people can make decisions, the need to understand how their decisions affect others also grows.
Carlos Ocampo · Field Notes D31 · September 2026
When more people can make decisions, the need to understand how their decisions affect others also grows.
A priority changes. A commitment moves forward. Someone finds an opportunity. Someone else detects a constraint that requires reviewing the plan.
How do we keep that movement connected?
At D31, we propose HFE™ —High Frequency Execution™— as a practice of frequent execution connecting decisions, actions, evidence and adjustments.
Autonomy needs a rhythm of synchronization.
The starting point is a shared reference: the “1 piece clear board” that leadership helps prepare and keep understandable. Its function is to provide clarity about the purpose, priorities, commitments and limits guiding the work.
That reference needs updating as reality changes.
A team can start the week with clear agreements and encounter different conditions a few hours later. Execution requires those changes to reach the people who need to interpret them and act.
Turning what happens into the next decision
In our proposal, an HFE™ review should allow concrete questions to be answered:
What did we commit to do? What happened? What evidence do we have? What changed? What decision is appropriate now?
Frequency becomes meaningful when it helps resolve dependencies and make corrections in time. The rhythm must respond to the speed of change in the work and to its consequences.
Consider a delivery requiring participation from sales, operations and administration. The customer requests an adjustment. Sales can negotiate within its mandate but needs to know how that change affects available capacity and agreed conditions.
A brief review can make that interdependence visible. The team identifies the effect, agrees on a response and assigns the next move.
The result of synchronization must be a usable decision.
Who will do what. By when. Under what conditions. What signal will indicate that another review is needed.
Evidence enables learning
A task marked complete leaves open the question of its outcome. Was the expected result delivered? Could the other person continue? Did a difficulty arise that we need to address?
That is why we propose linking commitments with enough evidence to evaluate their fulfillment.
The form may vary: a reviewed delivery, a customer response, a completed test or a confirmed agreement. What matters is that it allows us to understand what happened and guide the next decision.
This practice also requires preserving the distinction between an observed fact, an interpretation and something we still do not know.
The leader supports where judgment is needed
HFE™ offers leadership an opportunity to recognize where to intervene.
One person needs context. Another needs to develop a capability. Two decisions conflict. A risk exceeds the team's mandate.
Intervention may take the form of a question, a clarification, a coaching session or a decision about priorities.
The aim is for the team to continue with greater clarity and capability of its own.
Every review allows us to observe both the progress of the work and the development of those doing it.
The principle “Your decisions, your consequences” connects here. Each participant explains their choices and answers for their next action. The leader also reviews the conditions they enabled, the limits they established and the support they need to provide.
Learning to respond together
HFE™ connects autonomy with shared responsibility for interdependencies.
Each person retains a space for decision. The team needs to recognize when that decision changes someone else's working conditions.
The 51/49 rule remains a reference when introducing agents: people retain authority over purposes, mandates and exceptions. Information produced by technology must be reviewable and open to challenge during execution.
To evaluate this proposal, we need to observe concrete changes: how long a dependency takes to resolve, how many decisions unnecessarily await the leader and which problems reappear after review.
That evidence will allow the method to be adjusted to each organization.
The autonomous company needs people capable of deciding and a way to keep their decisions connected.
If an important condition in your operation changed today, how long would the team take to understand it, coordinate and act?
© 2026 D31. All rights reserved.
Before adding another layer of technology, it helps to see how ready the organization is to decide, coordinate and execute.
Take the Organizational Self Check-Up™ →