Skip to content

That's just a taste — their profile full of gems!

Visit profile
User avatar
Billy Morgan
November 160

Working Genius at Work

I’ve spent enough years leading teams to know this simple truth:

Most performance problems are not performance problems.

They’re fit problems. Role problems. Clarity problems. Energy problems.

That’s why the Working Genius framework resonates. It gives operators a practical language for something we’ve all seen but often fail to name: two capable people can look wildly different at work, not because one cares more, but because different stages of work give them energy and different stages drain them.

That distinction matters.

Too many leaders still make the same mistake: they assume if someone is competent at a task, they should keep doing more of it. That’s lazy management. A person can be very good at something and still be slowly burning out doing it.

I’ve seen this firsthand. In operating roles, people get rewarded for reliability, and before long they’re trapped in work that the business needs but that quietly kills their joy. Then the leader says, “I don’t understand, they’re great at the job, why are they disengaged?”

Because competence is not genius.

And if you miss that, you’ll misread the signal. You’ll call someone unmotivated when they’re actually misused.

What I like about this model is that it’s not another abstract personality exercise you do at an offsite and forget by Monday. It’s tangible. It answers a very practical question:

What kind of work actually gives this person energy?

That’s useful.

Not just for hiring.
Not just for team design.
Not just for meetings.

For retention.

One story that stuck with me was the idea that some people were heading toward the door—or toward being pushed out—not because they were wrong for the company, but because they were sitting in the wrong seat. Drucker said culture eats strategy for breakfast. I’d add this: role design eats a lot of culture before lunch.

If you have a good operator in the wrong kind of work, don’t be surprised when they get “cranky,” checked out, or flat. The problem may not be attitude. It may be sustained friction between what the work requires and how they’re wired to contribute.

That’s also why this lands so well in environments where leaders are dealing with burnout, turnover, and foggy accountability.

When teams don’t know what stage of work they’re actually in, they create avoidable friction. One person is trying to explore. Another is trying to decide. Another is trying to mobilize. Another is trying to finish. Then everybody gets frustrated with everybody else.

That’s not a personality clash.

That’s a workflow clarity issue.

Lencioni has always been strong at this. He doesn’t romanticize teamwork. He operationalizes it. Very The Five Dysfunctions of a Team: name the thing, remove the ambiguity, give people a shared language, and let the team function like adults.

The shared language here is the real unlock.

When a team can say, “We’re wondering right now,” or “This meeting is for invention,” or “We need tenacity in this stage,” the work gets cleaner. Expectations get cleaner. Meetings get shorter. Judgment goes down. Throughput goes up.

That’s the part many leaders miss.

The value isn’t just self-awareness.
The value is coordination.

And operators should care about that.

I also think there’s a leadership lesson here that has nothing to do with assessments and everything to do with humility. A good leader should be willing to say, plainly:

Here’s where I’m strong. Here’s where I’m not. Here’s the kind of work that drains me. Here’s where I need help.

That’s not weakness. That’s maturity.

In my experience, teams trust you more when you stop pretending to be universally gifted. Nobody believes that anyway. The minute a leader names their frustrations honestly, the team gets permission to be honest too. That’s when you stop managing theater and start managing reality.

And reality is where good operating happens.

One more point that matters: this framework doesn’t just reduce guilt; it reduces misplaced judgment.

A lot of tension on teams comes from people morally evaluating what is actually just a difference in genius. The person who loves brainstorming thinks the finisher is rigid. The finisher thinks the brainstormer is exhausting. The discerner sounds hesitant. The galvanizer sounds overly certain. Same team, same mission, different contribution pattern.

Once you understand that, you can stop pathologizing each other.

Lencioni’s work has always pushed leaders toward healthier teams, but this one is especially useful because it gets concrete fast. That’s why operators will use it. It doesn’t live in theory. It lives in calendars, meeting design, role design, and day-to-day collaboration.

If I were advising a leadership team on where to start, I’d keep it simple:

Don’t begin by rolling out another company-wide initiative.

Start with your own work.

Share where you do your best work. Share where you get drained. Then look at your team and ask one hard, operational question:

Do we have good people doing too much work outside their genius?

If the answer is yes—and on most teams it is—you probably just found a root cause of burnout, drag, and unnecessary turnover.

That’s worth fixing.

Because the goal isn’t to make work easy. Operators know better than that.

The goal is to align people to the kind of contribution where they can create disproportionate value without paying for it every day in frustration.

#leadership#productivity#teamwork#management#burnout#patricklencioni#workinggenius#operatingteams
Like
Dislike

Add a comment...