\n
<\/p>\n
Anyone who has spent time in a workplace knows the \u201cgo-to\u201d person. They are the colleague who can figure things out when others cannot, and who steps in when something complicated needs to get done.<\/p>\n<\/div>\n
Early in your career, becoming that person feels like success. In many ways, it is. Being capable accelerates opportunity. Leaders notice you, people trust you, and your reputation grows.<\/p>\n
But over time, something subtle happens. The more capable you prove yourself to be, the more people rely on you.<\/p>\n
I call this the capability curse.<\/p>\n<\/div>\n The capability curse occurs when someone\u2019s proven ability to solve problems leads others to depend on them for nearly every challenge. With each success, expectations rise. What once impressed becomes the standard, and when something falls short, the disappointment is sharper because the bar became so high.<\/p>\n Ironically, the people who can do the most often end up carrying the heaviest burden.<\/p>\n Early in my career, I was asked to build a database for people analytics. I was a recruiter, not a programmer. My manager handed me a book, recommended a consultant, and said, \u201cFigure it out.\u201d<\/p>\n<\/div>\n So I did. I spent nights learning the system and building something that worked. But because I was not a trained developer, it was not perfect. Eventually errors surfaced, and the same people who praised the initiative began to question the system when it did not perform like enterprise software.<\/p>\n It was my first real encounter with the capability trap. If I had refused the assignment, it might have been viewed as a lack of initiative. But once I said yes, the expectation became perfection.<\/p>\n This pattern appears everywhere in organizations. The more capable you are, the more complex problems land on your desk.<\/p>\n<\/div>\n There is another dynamic at play that capable people eventually notice. I think of it as the expectation gap.<\/p>\n When someone not known for solving complex problems manages to fix something, the reaction is often admiration. People say, \u201cWow, look what they pulled off.\u201d When a highly capable person solves the same problem, the reaction is very different. It is simply expected.<\/p>\n And if the outcome is not perfect, the criticism can be sharper.<\/p>\n<\/div>\n I once stepped in to handle a complicated operational issue that belonged to another department. No one else volunteered, so I took it on. Despite raising risks and asking for support, things did not unfold as planned.<\/p>\n When it was over, I was criticized for the outcome. The reason was simple: The expectation for me was higher.<\/p>\n Capability raises the bar and pressure.<\/p>\n<\/div>\n So why do capable people keep saying yes?<\/p>\n Part of the answer is practical. They know they can figure things out. When you have a track record of solving problems, it becomes almost instinctive to step in.<\/p>\n But another part is cultural. Many high-performing professionals, especially women, are often expected to be helpers and problem solvers. At work, that can mean filling gaps others avoid. At home, it can mean becoming the unofficial chief logistics officer for everything.<\/p>\n<\/div>\n Later in my career, a founder shared a story that reframed the way I think about capability. He told me his girlfriend once asked him to bring home a salad. Instead, he came back with a head of lettuce. She asked, \u201cWhat\u2019s this?\u201d<\/p>\n \u201cLettuce,\u201d he said. \u201cIt\u2019s salad.\u201d<\/p>\n She paused, then said, \u201cIf I wanted lettuce, I would have asked for lettuce. Never mind. I\u2019ll just buy the salad myself.\u201d And that was the end of it. She never asked him again.<\/p>\n<\/div>\n What struck me wasn\u2019t the misunderstanding. It was the expectation that was set. By bringing the lettuce, he defined what he would own and what he wouldn\u2019t. And everything adjusted around that.<\/p>\n We often think expectations are assigned. But more often, they\u2019re set by what we consistently deliver.<\/p>\n Sometimes the most important move is to just bring the lettuce and create space for others to make the salad.<\/p>\n<\/div>\n Another mentor once explained it to me differently.<\/p>\n \u201cImagine you have one wheelbarrow,\u201d he said. \u201cEvery task you accept goes into it. Eventually it becomes so full that it tips over.\u201d<\/p>\n It is a simple image, but an accurate one. Your capacity is finite. If you keep adding without limits, it will eventually topple.<\/p>\n<\/div>\n Capability often encourages people to keep adding more to the wheelbarrow. The solution is not to stop being capable. Instead, become more intentional about what you choose to carry.<\/p>\n Highly capable professionals do not need to shrink their ambition. They do need to manage it strategically. Start by deciding where your capability matters most. Before saying yes, ask:<\/p>\n Not every problem requires your full involvement.<\/p>\n<\/div>\n Another shift is moving from doing to advising. Instead of saying, \u201cI will take care of it,\u201d try, \u201cI can help advise the person who owns this.\u201d You still contribute, but you are no longer carrying the full weight.<\/p>\n And if you do step in, clarity matters. One of the most powerful things you can say is: \u201cI\u2019m happy to help, but this is outside my core role and the solution will not be perfect. If it fails, I expect shared responsibility or you will take the responsibility and give me air cover.\u201d That kind of clarity prevents resentment later.<\/p>\n None of this means capable people should stop being capable. Capability is what makes someone a versatile leader. It reflects resilience, judgment, and the ability to navigate ambiguity.<\/p>\n<\/div>\n But without boundaries, that same strength can quietly become a liability. Being capable should expand your opportunities and not exhaust your capacity. It can also get in the way of doing fewer things better. Leadership is often about focus.<\/p>\nWHEN COMPETENCE BECOMES A LIABILITY<\/strong><\/h2>\n
THE EXPECTATION GAP<\/strong><\/h2>\n
WHY CAPABLE PEOPLE STRUGGLE TO SAY NO<\/strong><\/h2>\n
THE LETTUCE VERSUS SALAD LESSON<\/strong><\/h2>\n
THE WHEELBARROW PROBLEM<\/strong><\/h2>\n
HOW TO AVOID THE CAPABILITY CURSE<\/strong><\/h2>\n
\n
CAPABILITY IS STILL A STRENGTH<\/strong><\/h2>\n