Brett Lloyd Leonard (@bretttechcoach) header
Brett Lloyd Leonard (@bretttechcoach) profile picture

Unspoken Patterns of Technical Leadership. I help senior engineers make the shift from execution to influence.

Cincinnati, Ohio
Joined October 2022
Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)Photo by Brett Lloyd Leonard (@bretttechcoach)
I write about the patterns that separate senior engineers from trusted technical leaders. Systems thinking. Delegation. Judgment. Ownership. Clarity. No frameworks. No hype. Just the stuff nobody handed you. Grab the guide: Unspoken Patterns of Technical Leadership. Link below. guide.bretttechtrain.com/
1
26
You're in a meeting with other teams. You know the answer. You know they're wrong.
2
18
The best engineers get passed up this way. Not because they don't know. Because nobody sees what they know.
1
8
Pick one thing you understand and someone else doesn't. Make it visible this week.
Mapping a system isn't a gift, it's a skill you can build.
2
79
Not because I'm wired differently. Because I did the boring thing long enough that it became automatic.
1
5
The most important part is naming the outcome, the reason the system exists.
2
Five shifts that make regular engineers trusted technical leaders: From: Tasks to outcomes Answering questions to asking better ones Protecting your work to making your work visible Being right to being useful Waiting for direction to owning direction Leaders do not receive clarity. They create it.
1
Most engineers plateau because they refuse to trade a bronco for a surfboard They keep wrestling. > More hours > More logic > More force. Leadership isn't about overpowering anything. It is reading the waves. Adjusting your stance. Riding the chaos instead of fighting it.
4
Jay is an excellent developer (now PO) who wants a leadership role. In a staff meeting, our boss asked him if his team had a plan to support another team on a crucial weekend. Jay said: "I will be available if they need it." I said: "You need your team handle it. If they get stuck, you can guide them" My boss nodded. Jay said: "I like that. I promise I will not write a line of code." That gap is an unspoken pattern. Nobody teaches it. You learn it from people who lead, or you stay one writing the code.
6
Leadership is creativity When there is no road map
2
If you think leadership is a title you've already lost. The best leaders I have worked with never waited for permission.
5
You were trained to control complexity. Capture it. Contain it. Wrangle it to the ground. That works w systems. It fails w people. Leadership is not a bucking bronco. It is the ocean. You do not control the waves. You learn to read them. The sooner you accept it, the sooner you lead.
1
11
I spent 20 years watching engineers fight the waves when they could have been riding them. The difference comes down to a handful of patterns nobody teaches. I wrote them down: Unspoken Patterns of Tech Leadership guide.bretttechtrain.com/
9
The dictionary says leadership is guiding a group. Here is what it is left out: <1> Creativity <2> Pro-activeness <3> Emotional intelligence <4> Communication <5> Accountability <6> Technical intuition None in the definition. Every IT leader I've known has them.
13