Telling someone something they don’t want to hear is never fun. When someone points out a problem causing them real pain, you likely want to do something about it – particularly if you’re their manager. Saying no to when someone asks you to fix something is often a necessary part of a manager’s job.
Addressing complaints is essential to a manager’s job but can quickly become overwhelming. Part One of this series shared a technique for sorting through people’s concerns. It also showed how to use your authority effectively to address some of them. But people often complain about things outside your control – and you need to deal with those as well.
Addressing complaints is an essential part of a manager’s job. By keeping their finger on the pulse of what’s bothering people, managers can act as an early warning system for higher levels of management. By addressing their people’s concerns, managers can improve both productivity and morale. At the same time, facing an endless stream of criticism – often about things you can’t control – can be one of the most frustrating parts of being a manager. As a manager, you need the ability to listen to and learn from complaints without drowning in them.
“One of the people I manage is underperforming. I need to give them feedback about how they aren’t meeting expectations.”
I hear this often from managers, and I get curious whenever I do. The instinct behind it is good: Managers need to address underperformance. In my experience, however, giving performance feedback about unmet expectations is unlikely to help if you haven’t done your homework first. One of my teachers says, “80% of employee problems are due to manager neglect.” Whether you are a manager or not, when someone isn’t meeting your expectations, start by looking at what you’re doing – and what you’re not.
Some of my most spectacular failures working with teams have come from going deeper than I needed to. One particularly memorable retrospective ended with a product manager declaring, “I’m done talking about my feelings.” (It was not my finest moment.) Yes, organizations are made of people. And yes, work happens inside a container of relationships. But that doesn’t mean every attempt to address a team or organizational problem must be super deep. Choosing the depth at which to intervene is critical for every manager, consultant, and coach.
“I don’t want to distract the team. They don’t need to worry about this.” That’s what my boss – the head of engineering at a rapidly growing startup – told me when I asked him how he would share information from top management about our revised expansion plans. His job, he said, was to protect the engineers from things like this and to let them focus on building the product.
“We want to know how aligned people are around the new product development strategy. How can we do that?”
A group of senior leaders at a software company asked me this question as I was helping them to prepare for their annual kickoff meeting. They’d just completed a challenging year of development on a new product initiative. While it had generated some impressive results, they recognized that they needed to approach the following year differently. They were bringing the core team of twenty-five or so key contributors – usually distributed across the United States – together for several days to roll out their plans for the new year. They’d brought me in to help plan and facilitate the event. I knew what I needed to do: help them create a shared understanding of the new strategy.