You can lead a horse to water but you can't force it to drink

speckx1 pts0 comments

You can lead a horse to water but you can’t force it to drink | William Durand

You can lead a horse to water but you can't force it to drink

24 December 2025

Clermont-Fd Area, France

//

tech leadership,<br>thoughts

It’s an unpleasant pattern, one I’m deeply aware of: the tendency to use my<br>regular 1:1s with my manager as an outlet for pent-up frustration. While I<br>strive for constructive dialogue, the reality is that the various challenges my<br>team has faced over the past 3 years have created a reservoir of exasperation<br>that sometimes spills over. It doesn’t happen every time but I wouldn’t exclude<br>it happened more often than I am willing to concede…

One particularly vivid discussion centered on the acute challenge of driving a<br>project forward when the contributors appeared distracted, pulled in too many<br>directions, or simply disengaged. I don’t remember the specifics but, as a tech<br>lead, this is a recurring problem. I possess all the technical vision and<br>planning responsibility, but none of the formal “authority” of a manager. I am<br>tasked with orchestration, but lack the levers of performance reviews or task<br>assignment to enforce focus.

My manager, having listened patiently to my description of the sheer effort<br>required to maintain momentum, made the following comment:

You can lead a horse to water but you can’t force it to drink.

At the time, my sole obsession was the completion of the project. This singular<br>focus blinded me to a set of important leadership principles, which this saying<br>kinda illuminated.

First, there is a stark division between what I can control and what I cannot.<br>Since I am not a manager, I cannot mandate what tasks my teammates prioritize,<br>and I cannot force them to allocate their time optimally either. These are<br>management functions that reside elsewhere.

However, recognizing this limitation is liberating, as it directs my energy<br>toward my spheres of influence. I can absolutely control the clarity of the<br>project’s priority. I can ensure that every relevant stakeholder understands why<br>this work is a top-priority initiative. Furthermore, and critically, I can<br>control the environment for execution. I can be the first to identify and remove<br>blockers, to clarify ambiguities, and to ensure no one is “stuck” awaiting a<br>decision or a piece of information. My role shifts from pushing people to<br>clearing the path for them.

The second insight is about the nature of my intervention. I can generate far<br>greater impact by adopting a posture of “enablement” and opportunity creation<br>rather than rescue or takeover. It’s tempting, in the face of (likely) perceived<br>slowness, to simply get things done myself. This provides immediate, but<br>shallow, relief. The deeper, more structural impact comes from always creating<br>new opportunities.

This approach requires a profound acceptance of risk, though. It means accepting<br>that an opportunity provided might be fumbled, that a delegated task might not<br>be executed perfectly, or that a teammate might initially choose the wrong path.<br>If I take over every difficult or risky task, I rob my colleagues of the<br>opportunity to grow, to demonstrate ownership, and to ultimately drink the<br>water on their own terms.

And that’s why I find this saying pretty good and relevant. As a tech lead, I am<br>responsible for the water. I must ensure the goal is clear, the path is<br>accessible, the resources are available, and the environment is conducive to<br>success. I must exhaust every possible avenue to supercharge my teammates<br>through inspiration, clear communication, and strategic support.

But I am not, and cannot be, responsible for the drinking part. If, after all<br>my efforts, a team member consistently chooses a path of disengagement, lack of<br>focus, or resistance to the collective goal, that crosses the boundary of my<br>direct control. At that point, the issue moves into a different domain. It<br>becomes an issue for their own manager to address or for the individual<br>themselves.

Accepting this boundary helps me preserve my energy for where it can truly<br>effect change.

ℹ️ Feel free to fork and edit this post if you find a typo, thank you so much! This post is licensed under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

💟 Discuss on Mastodon.

Credits

Photo used on social media by Vito Natale.

Recent articles

Moziversary #8

01 May 2026

My process for pitching projects as an engineer

30 Dec 2025

Moziversary #7

05 May 2025

Firefox AI & WebExtensions

24 Mar 2025

Senior Staff.

01 Mar 2025

lead water force drink manager horse

Related Articles