Wise Counsel vs the Corporate Leaf Blower: Why One Note Leadership Fails
One note leadership fails because it repeats a single fixed message regardless of context, like a leaf blower droning through every situation with the same noise. Wise counsel instead listens, adapts, and asks unpredictable questions that reveal blind spots. Leaders who tune out nuance for repetition lose credibility, trust, and the insight needed to make sound decisions.
There is a sound most of us have learned to tune out, the drone of a leaf blower a few gardens over. It never surprises you and it never says anything new. It just moves the same pile of leaves from one lawn to the next, burns through its fuel doing it, and drones on until it eventually stops, which you almost don’t notice when it does.
Every organisation has two recurring characters, and learning to tell them apart shapes what kind of leader you become.
1. The person you lean in for
The first is the person whose next sentence you genuinely cannot predict. They might ask about your customer, your margin, your team’s morale, or the technical debt you have been quietly ignoring, and you do not always like what they say. But you lean in anyway, because you sense you are about to learn something you did not know you needed to know.
What makes them valuable is not a job title or a framework. It is that they hold the whole problem in their head at once, the money and the people and the risk and the experience and the timeline together, and they are willing to change their mind when the evidence changes. They ask questions before they hand you an answer, and being around them feels like growth, even when growth is uncomfortable.
It is worth being precise about what this is not. Holding several considerations at once is not the same as failing to decide. The wise counsel still reaches a call, often a firm one, but the call is built by weighing the cost against the customer against the risk against the timing, rather than by reciting whichever one of those happens to be their specialty. Indecision is the absence of a call. Judgment is a call that has actually accounted for everything in the room before it is made.
2. The sound in the background
Picture a steering committee a few weeks before launch. Someone raises a new idea, a partnership, a pricing change, a way to serve a segment nobody has served well before. Before they have finished describing it, the same voice in the corner says the same thing it said last quarter, and the quarter before that, and the room’s energy visibly drops, because everyone already knows how this goes.
The second character says the same thing, in the same order, in every meeting you have ever sat in with them. You know their line before they open their mouth, because it is always the same line, and over time it stops being counsel and starts being background noise, the thing you have learned to nod through rather than actually listen to.
That is the corporate leaf blower, and three things define it. It is predictable, because you already know the line before it is said. It is low value, because it rarely adds anything the room did not already have. And it is noise, because what it produces is volume rather than resolution. The metaphor holds up better than it should. A leaf blower does not really get rid of anything. It relocates the leaves to the neighbour’s yard, burns a disproportionate amount of fuel doing it, and produces a lot of noise for very little resolution. That is close to what a one note voice does inside a business. The finance objection may genuinely remove a visible cost, while creating a much larger invisible one through delayed delivery, lost revenue, weaker capability, or customer attrition. The security “no” may genuinely reduce one class of risk, while quietly increasing another: strategic risk, customer risk, execution risk, or the risk of letting a competitor move first. Nothing gets fully solved. It just moves somewhere less visible, at a real cost, with a lot of noise attached along the way.
3. Why the narrow view feels so right and does so much damage
There is a well known idea in operations thinking, developed by Eliyahu Goldratt through his Theory of Constraints, that explains why this pattern is so persistent and so hard to see from inside it (Goldratt, The Goal; see also the Goldratt Research Labs introduction to Theory of Constraints). Goldratt drew a distinction between a local optimum, which is what looks best for one part of a system, and a global optimum, which is what is actually best for the system as a whole, and judged any local change by its effect on the organisation overall rather than on the part being changed. His argument, developed through manufacturing and later applied well beyond it, was that pushing every part of a system toward its own local optimum tends to make the whole system worse, not better. A factory can run every machine at full utilisation and still lose money, because the constraint on overall output was never in the machines that were being optimised in the first place. Improving a part of the system that is not the actual constraint may make that part look better without improving the performance of the system as a whole, and in some cases it creates excess work, inventory, or pressure elsewhere that leaves the whole system worse off.
This is exactly the trap the finance voice, the UX purist, and the cyber gatekeeper fall into, each in their own function. The finance voice can account for every rand of cost and none of the revenue that never arrived because the “expensive resource” never got hired, and it is optimising its own local metric while the business misses a global opportunity worth many multiples of the saving. The UX purist has such a strong and consistent opinion about design that the client’s actual feedback gets talked over rather than heard, and consistency, a real and valuable discipline on its own terms, becomes a local optimum pursued at the expense of the product actually working for the people who use it. The cyber gatekeeper whose entire vocabulary is “no,” never followed by “and here is how we get to yes,” is optimising for a risk register that looks clean in isolation while the business loses ground it can never recover. Each of them can point to a number that went the right way in their own corner of the system, even as the system as a whole quietly loses.
None of these people are villains, and each of them is protecting something real. The problem is not the concern itself. It is that the concern has become the only note they play on every song, regardless of what the song actually needs, and regardless of whether that note is even the constraint worth optimising for.
4. Why the organisation keeps producing them
None of this happens by accident, and it rarely happens because the people involved are careless. It happens because most organisations measure people on their part of the system rather than on the system as a whole. The finance voice is measured on cost variance, so a cost avoided looks like a win regardless of what it costs the business elsewhere. The cyber gatekeeper is measured on incidents avoided, so a risk declined looks like a win even if it costs the business a market window. The UX purist is measured on design consistency scores, so a consistent screen looks like a win even if the client never asked for it. Each of these measures is reasonable on its own terms, and each one quietly trains the person holding it to defend their own local optimum rather than the result the whole business actually needs.
This is the part of Theory of Constraints that gets left out of most retellings of it. Goldratt’s argument was not only that local optimisation is common, but that it is manufactured by the measurement system itself, and that fixing the behaviour without fixing what gets measured rarely works for long. A leader who wants fewer leaf blowers on their team should look as hard at what gets measured and rewarded as at who is doing the talking.
5. Why the noise wins by default
The leaf blower is often easier to listen to than the wise counsel, and that is part of why the pattern survives so well inside organisations. A narrow, repeated concern is simple to model, simple to escalate up the chain, and simple to defend afterwards in a post mortem. “I told you the cost was too high” is a much easier sentence to say in hindsight than “I weighed the cost against the revenue and the risk and the team and the timing, and I got the balance wrong.” One of those is a script that can be recited the same way every time. The other is judgment, and judgment is harder to defend precisely because it is the entire job.
There is a deeper cost buried in this too. When the same voice always plays the same note, there is no room left to learn, because learning requires admitting that you do not yet know something, and a one note voice can never say that without contradicting its own authority. The wise counsel is comfortable saying “I am not sure yet, let us find out.” The leaf blower cannot say that sentence, because its authority depends on already having the answer, every time, before the question has even finished being asked.
6. What this asks of leaders
If you are running a product, a workstream, or a team, the job is not to pick a lens and defend it well. It is to hold all the lenses at once, the cost and the experience and the risk and the people and the timing, and to let each one inform the others instead of letting one drown out the rest. Theory of Constraints offers a useful discipline here, which is to keep asking what the actual constraint on the whole system is, rather than assuming that whichever concern is loudest in the room, or whichever concern happens to be your own specialty, is automatically the one worth optimising. Sometimes the constraint really is cost, and sometimes it really is security, and sometimes it is neither, and the leader’s job is to find out which, again and again, rather than to already know.
Goldratt’s own method for doing this is a useful shape to borrow, even outside a factory. Identify the actual constraint before debating solutions. Get everything possible out of that constraint before asking for new investment. Line up every other decision, cost, design, and risk choice, behind whatever the constraint actually needs, rather than behind whichever function happens to be loudest. Only then invest to lift the constraint itself. And once it moves, which it eventually will, start again, because the same constraint rarely holds for long, and the leader who stops checking becomes exactly the predictable voice this piece has been describing.
This is genuinely harder than being the finance voice, or the UX purist, or the cyber gatekeeper, because it means sitting with tension instead of resolving it too early with a single familiar answer. It also means noticing when you have started to become the sound in the background yourself. A useful check is this: if you can predict your own next sentence in a meeting before you say it, so can everyone else in the room. If your answer to a new problem is the same answer you gave to the last five problems, you have stopped counselling and started droning.
The wise counsel earns attention by remaining curious as the evidence changes, and the leaf blower loses it by remaining certain regardless of the evidence. Only one of them is actually still learning, and only one of them is worth leaning in for.