Imagine what kind of things show up on a manager’s performance review. They are likely rewarded for being responsive, decisive, aware of status, keeping teams on track, and removing obstacles. It all sounds great. Makes sense even, from a certain point of view.
But I sincerely believe that a manager who scores well on every one of those phrases may be quietly holding the organization back. The behaviors an adaptive organization actually needs look different, and some of them look like somebody not doing their job.
Here are five of them.
Strategy & Outcomes
Turn down work you have the capacity to do
We have room for it. It does not move the outcome we committed to. So what are we dropping?
Most of us were trained on capacity management. Somebody asks for work, you check whether the team can absorb it, and if the answer is yes then the answer is yes. That feels responsible. It feels protective, even. But capacity is the wrong test, and I think everyone in the room knows it the moment you say the sentence out loud. If the only question is whether the work fits, your roadmap becomes a function of headcount rather than strategy.
What makes this one hard is that saying no to work you could comfortably do looks like underperformance to everyone upstream of you. That is exactly why it belongs on the list. And the sentence is not the end of the conversation. The next move is a real one, with your product manager, about what the request is actually trying to achieve. Sometimes you find out the roadmap was wrong and the no turns into a change of direction. Sometimes you find out the request matters more than something already in flight, which is a fine outcome too, as long as somebody decides on purpose.
Product Thinking & Discovery
Let your team hear the customer complain about you
Do not summarize it for me. I want the team in the room when they say it.
Shielding the team from the angry customer is one of the kindest instincts a manager has. I have done it plenty. It feels like protection, and sometimes it genuinely is. The problem is what happens to the information on the way through you. You soften it, you generalize it, you translate it into something actionable, and by the time the team hears it they are building for the customer you described rather than the one who complained.
A team that only ever gets the filtered version stops doing discovery and starts doing requirements gathering, whatever they happen to call the meeting. So have the real conversations with customers, and put the delivery team in the room when you do. In my experience half an hour of that accomplishes more than any carefully constructed persona ever will, because a persona describes a type of person, and the customer in front of you describes what actually happened to them, with the frustration still in their voice. Teams come out of those conversations with an empathy you cannot manufacture in a workshop.
Putting people in front of unmediated criticism costs you something politically, particularly when some of that criticism is about you. In my experience, absorbing that cost is the job.
Flow of Work & Delivery
Stop being so good at unblocking
Stop telling me how you fixed it. Tell me why it keeps happening.
This is the one I think stings the most. Unblocking is the most visible competence a manager has. It is fast, it is tangible, people thank you for it, and it shows up in every skip-level as evidence that you are effective. But every single unblock is a manual workaround for something the system should have handled without you. You are the workaround. And because you are good at being the workaround, nobody upstream ever feels the pain that would have forced a fix.
I am not suggesting you unblock slower. Keep unblocking. But write them down, and once a month look at the list and ask what keeps generating them. Chris Argyris called this the difference between single-loop and double-loop learning. Fixing the instance is single-loop, and it is the loop that management training rewards. Asking why the instance keeps arriving is where flow improvements actually come from.
Team & Org Design
Ask who designed the team, not who is on it
Who decided the team should be split this way, and what were they solving for?
When a team is struggling, the reflex is to look at the people. Coach somebody, hire somebody, move somebody. What I notice again and again is that the shape of the team is the thing quietly doing the damage, and almost nobody looks at the shape, because it was not a decision anyone remembers making. It is just how things are. It is how things have always been.
So ask the question. Most of the time nobody can tell you who decided, and that silence is your finding. You have established that the structure was inherited rather than designed, and you did it without putting a single person on the defensive. Then comes the follow-up that matters: what would we have to break for this team to ship something without a handoff? Conway showed us that the architecture will mirror the communication structure whether anyone intended it or not. Team Topologies gives you the vocabulary to change that on purpose.
Leadership & Culture
Be visibly unsure in front of your own team
I do not know. What am I missing?
Decisiveness might be the single most rewarded trait in management. Have the answer, have it quickly, and never look uncertain in front of the team. And every time you do that, you teach the room that information travels toward you rather than the other way around, so the person who could have told you the thing you needed sits quietly instead. Edgar Schein made the case that asking is how a leader builds trust, not how a leader gives up authority.
Admitting you do not know reads as weakness in a hierarchical organization and as competence in an adaptive one. Which makes it a rather useful diagnostic. Try it once and watch what happens. If the room fills in, you have something to work with. If the room goes quiet, you have learned something more important about your culture than an engagement survey was ever going to tell you.
Where these five actually live
None of these five are about being better at the manager job as it is currently written. They are about the environment the team is working inside, and each one lives in a different part of that environment. Turning down good work is a strategy behavior. Unmediated customer contact is a product behavior. Chasing the generator instead of the blocker is a flow behavior. Asking who designed the team is org design. Admitting you do not know is culture.
That is the argument of Assembled. Aligned. Adaptive. in miniature. The five layers move together, and the leaders who ignore even one of the five are usually the ones who cannot figure out why nothing sticks.
Assembled. Aligned. Adaptive. is available now. The free Book Summary is a concise tour of the whole model.