The leaders who build the most confident, fastest-moving teams are rarely the ones with the highest standards. They are the ones whose standards are the most clearly understood by the people around them.
For clarification, high standards and clearly communicated standards are not the same thing. The gap between them is where a surprising amount of organizational capability stalls.
Most experienced leaders have spent years developing a finely calibrated sense of what good looks like. They can feel when work is ready and when it is not. What is rarer, and significantly more valuable at an organizational level, is the ability to translate that calibration into something legible to the people around them, so that the team begins operating with the same sense of what is required without being told each time.
That transfer of standard is where the real leverage lives.
The distinction that tends to get missed
Feedback inside most teams falls into 1 of 2 categories, and being deliberate about which one you are offering changes the downstream impact considerably.
- Functional feedback materially improves the outcome. It reduces risk, sharpens a decision, or closes a gap between what was delivered and what the situation actually required. When this kind of correction is offered with the reasoning made visible, the standard transfers. The person receiving it does not just improve the work in front of them. They internalize the logic and begin applying it without prompting. Over time, that is what builds a team that moves with both speed and genuine quality.
- Preferential feedback makes the work more aligned to how a particular leader thinks, communicates, or operates. When it arrives with the same weight as functional feedback, it creates noise around what is truly essential. Teams that cannot easily distinguish between the two tend to treat everything as equally important, which slows execution and erodes the independent judgment that strong teams are built on. People stop trusting their own read on the work and start managing the preferences of the people above them instead.
The goal is not to have less feedback. It is feedback precise enough that it builds capability rather than dependence.
Over the past 8 years I've seen many versions of this same scenario. The team's capabilities are strong, strategy is solid, but what's missing is the kind of organizational fluency where good work moves forward without unnecessary friction and where the people closest to execution feel genuinely trusted to make decisions within their scope.
Through our work with them and in their S.P.A.R.K. Assessment data, patterns become visible. Different leaders apply different standards at different points in the process, and the team has no shared way of distinguishing between what's functionally required and what's stylistically preferred.
The result is rework that doesn't actually impact the overall output, just a leader's desire for it to be done the way they're used to. Yeah...I checked myself with this one the other day...
For anyone leading at or across levels, there are 2 shifts that tend to have the most impact.
1. Make your non-negotiables explicit and shared.
Every leader carries a set of standards that are genuinely important, around risk, quality, decision-making thresholds, and stakeholder involvement. When those live only in your head, the people around you cannot apply them independently.
- Write the short list down and share it directly with the people who need it
- Revisit it when you find yourself correcting the same type of work more than once — repeated correction is almost always a signal that the standard was never fully articulated
- Bring your leadership team to a shared version of it, identifying where you need to be consistent across all of you and where individual style can vary
Teams that have this in place execute with a noticeably different quality of coherence.
2. Build the habit of distinguishing feedback in real time.
Before offering a correction, it is worth a brief pause to consider whether the adjustment improves the outcome or simply brings the work closer to how you would have done it.
- If it is functional, make the reasoning explicit so the standard can be internalized and applied without you
- If it is preferential, consider whether it needs to be introduced at all
- If you are on the receiving end, get comfortable surfacing the distinction upward: Is this about the outcome or the approach? is a question that sharpens the feedback culture over time for everyone involved
The teams where this language exists, where people can name the difference between a functional and a preferential correction, tend to move with a quality of confidence that is difficult to manufacture any other way.
If any of this reflects something you are working through in your organization, reach out. The conversation tends to be useful earlier than most people expect!
Finally, a few announcements for our community:
- This newsletter is moving into something slightly different in the weeks ahead. The ideas we've been exploring around how expectations travel across levels, where precision breaks down, and what genuine organizational alignment actually requires are beginning to take a clearer shape. This space is getting it's own identity and I cannot wait to share it with you!
-
If you're looking for a good book read through Q2 with your team, I'd recommend Amanda Schneider's Work for What's Next is a must-read when it launches this coming May!
Unsubscribe · Preferences
