🔒

Bob Manthy Hub

Private project workspace

Wrong password.

← Back to Bob Manthy Project Hub
Voice notes: These posts read like Bob sharing a private observation from inside his work. Specific. Non-clinical. A little disarming. Not tips. Not "here's how to fix it." Something a sharp person would forward to a colleague they respect.
Format reminders: Short paragraphs (2–3 lines max on LinkedIn) · Hook in first two lines before "see more" cut · Hashtags kept small (3–5), relevant, not performative.
Framework 1 The Capable Person's Trap
1 The Setup: How success installs the trap Tuesday 8–9 AM or 12 PM
Hook (first 2 lines)
The most capable people I work with have the hardest time asking for help. That's not a character flaw. It's almost logical.
Every time you've had a hard problem in your career, you've solved it. You built a track record of that. You got promoted because of it. So when something's wrong in your life, not a strategy problem, not a hiring problem, but something quieter and harder to name, the instinct is to apply the same approach. Analyze it. Research it. Optimize it. Or just stay so busy you don't have to look at it directly. That works for a while. Then it doesn't. The capability that built your career can become the thing that keeps you from addressing the most important problems you have. I call this the Capable Person's Trap, and I see it constantly. Not in weak people. In the ones who've figured out almost everything else. If you're reading this and something's landing, that recognition is actually useful information.
2 The Moment It Breaks: What it looks like when the strategy stops working Thursday 7–8 AM
Hook (first 2 lines)
Something I hear more than almost anything else in first sessions: "I don't know why I'm not okay. Nothing is actually wrong."
And they mean it. Objectively, things are fine. The career is successful. The family is together. They're healthy. By any external measure, it's working. But there's a flatness. A distance from the life they've built. A growing sense that the next achievement won't resolve whatever this is. What's usually happened is that they've been so effective at pushing through difficulty, and so good at reading environments that reward capability, that they've lost contact with the internal signals that were trying to tell them something. Not suddenly. Gradually, over years of being excellent at performing. This is what the Capable Person's Trap looks like from the inside. And it's why the most accomplished people sometimes end up being the most cut off from their own experience. The good news: that's recoverable. It just takes working with it differently than you've worked with everything else.
Framework 2 Achievement Identity
3 The Question: What it reveals when you sit with it Tuesday 8–9 AM
Hook (first 2 lines)
I ask almost every new client some version of this: If you couldn't work for a year, who would you be?
Most of them pause longer than they expected to. Some laugh. Some deflect with a joke. Some give me a technically complete answer that doesn't actually answer the question. I'm not asking it to be philosophical. I'm asking it because the answer (or the difficulty with the answer) tells you something real about where your identity is actually located. And for most high-achieving executives and founders, a significant portion of that identity is built around what they produce. That's not inherently a problem. Ambition isn't a problem. But identity built almost entirely on output creates a specific kind of fragility. Because careers plateau. Companies fold. Health changes. Titles change. And when the thing that's been defining you gets disrupted, as it will, eventually, the question becomes urgent. The work I do isn't about dismantling what you've built. It's about building the self that can hold it.
4 The Retirement Problem: Why "I'll deal with it later" has consequences Wednesday 12–1 PM
Hook (first 2 lines)
A lot of high achievers have a plan that goes: I'll figure out who I am when I slow down.
It's not a bad plan on the surface. You're in a demanding season. The demands are real. There'll be time later. The issue is that "figuring out who you are" isn't something you can defer until a less busy season and then pick up fresh. The patterns compound. The distance from your own interior grows. And then one day, retirement, transition, a forced pause, the space that was supposed to feel like freedom feels like disorientation. I've worked with executives who were genuinely blindsided by how disorienting leaving high-velocity careers was. Not because they'd done anything wrong. Because they hadn't maintained any relationship with who they were outside the role. This isn't inevitable. But it's very common among people who've been exceptionally good at performance for a very long time. Starting earlier, even a few years, even one honest conversation, makes a significant difference.
Framework 3 The Leadership Silence
5 Information Decay: How authority corrupts the data you receive Tuesday 8–9 AM
Hook (first 2 lines)
The higher you go, the less accurate the information you get. Not because people lie. Because they filter.
It's not cynical to say this. It's just how organizations work. People tell leaders what they think leaders need to hear, what they think leaders want to hear, and what keeps them safe. By the time information travels up several layers, it's been significantly curated. Most executives I work with understand this intellectually. The harder pattern to see is the internal version of the same thing. High performers are often remarkably good at filtering their own signals. Uncomfortable truths get routed around. Warning signs get noted and then buried under the next thing on the agenda. It's not avoidance in a simple sense, it's a very sophisticated, very functional form of management. The cost shows up later. In relationships that went quiet while you were busy. In health that got deferred. In a growing sense that you've been running a successful life that doesn't quite feel like yours.
6 The Room No One Tells the Truth In Thursday 7–8 AM
Hook (first 2 lines)
One thing I've noticed: the more senior someone is, the fewer people they have who will actually tell them the truth.
Not because the people around them are dishonest. Because authority changes what people are willing to say. The subordinate with a family and a mortgage isn't going to push back the way a peer would. The consultant wants the engagement to continue. The board member has their own interests. Everyone's being reasonable, and the net result is that the person at the top is often working with the most filtered version of reality in the organization. This isn't just an organizational problem. I see it in how leaders relate to themselves. The ability to keep moving, to stay effective, to manage your internal state well enough to function, those are real capacities. But they can also become a sophisticated system for not hearing things you need to hear. Sometimes what I offer isn't insight or frameworks. It's just a room where none of that filtering applies. Where someone can say what's actually true for them and have it received as information rather than as a problem to be managed. For a lot of executives, that's rarer than it should be.
Framework 4 The Capable Couple
7 When Both People Are the Problem-Solver Wednesday 8–9 AM
Hook (first 2 lines)
Two high-achieving people in a relationship face a specific problem: they both show up to hard conversations with the same toolkit.
You're both good at analyzing. Both used to performing under pressure. Both capable of staying composed in difficult situations. In a lot of ways, that's an asset. But there are moments in a relationship where the skill set that makes you excellent at work becomes a liability. You negotiate when your partner needs you to be vulnerable. You optimize when they need you to slow down. You stay in problem-solving mode when the most useful thing would be to simply be present. And because you're both doing versions of this, neither of you is getting what you need. But you're both too capable to say that clearly. So the distance grows, quietly and efficiently. This is a pattern I see often when both partners are high achievers. It's not about who's right. It's about a dynamic that two capable people can co-create without fully seeing it.
8 The Efficiency Trap in Relationships Thursday 12–1 PM
Hook (first 2 lines)
High-achieving couples often run their relationship the way they run their organizations. Very efficiently. And that's part of the problem.
You divide responsibilities. You solve problems as they arise. You communicate effectively about logistics. You're a good team. And somewhere in all of that competent partnership, the actual intimacy gets scheduled into a slot that's always getting bumped. It's not malice. It's just that the skills that make high performers excellent at running complex organizations are genuinely poorly suited for sustaining emotional closeness. Efficiency and vulnerability are in tension. Optimization and presence are in tension. The faster you move, the harder it is to actually be somewhere. I work with couples where both partners are accomplished, busy, and quietly confused about why a relationship that looks good on paper doesn't feel good in practice. It's a specific thing. And it responds to specific work.
Framework 5 The Engineer's Blind Spot
9 The System That's Running You Tuesday 8–9 AM
Hook (first 2 lines)
Engineers are very good at understanding systems. They're often not as good at recognizing when they're inside one.
I say this with direct experience. I spent years as a software engineer at Google. I understand the mindset. You learn to see the world in terms of inputs, outputs, variables, and optimization. It's genuinely useful. It's also a framework that doesn't map cleanly onto the parts of life that matter most. The relationship isn't a system you can optimize. The problem you're feeling isn't a bug you can patch. The discomfort you keep routing around isn't an inefficiency to be eliminated. One pattern I see often in engineers and technically-minded leaders: they're exceptionally good at understanding everything around them and much less practiced at understanding themselves. Not because they're not intelligent. Because the tools they've spent years developing weren't built for that work. Recognizing that the analytical toolkit has limits, especially for internal and relational problems, is usually the beginning of something useful.
10 Debugging the Self Wednesday 7–8 AM
Hook (first 2 lines)
The hardest thing I've found working with analytically-trained clients isn't getting them to think. It's getting them to stop.
Analysis is a superpower in the right contexts. But when you turn a highly developed analytical mind on your own interior, your feelings, your relationships, your sense of meaning, something predictable happens. You start generating explanations. Good ones. Internally consistent ones. And you can stay in that loop indefinitely without actually moving. Understanding why you feel a certain way is not the same as actually processing it. Mapping the dynamic in a relationship is not the same as changing anything in it. Knowing intellectually that you're burnt out is not the same as recovering. This is the Engineer's Blind Spot: a very capable analytical capacity that gets deployed in exactly the domain where it's least effective, and produces the experience of working on the problem while leaving the problem fully intact. I work with technical leaders and engineers who are used to being the smartest person in the room and are discovering that this particular room requires something different.
Framework 6 The Endurance Mentality
11 What It Gets Right and What It Costs Tuesday 8–9 AM
Hook (first 2 lines)
The capacity to keep going when everything in you says stop, that's real. I'm not going to tell you it's a problem.
I've run ultramarathons. I served on nuclear submarines. I know what that capacity feels like and what it makes possible. It's how you do things that most people won't. It's not something to give up. But I work with a lot of people for whom that same endurance mentality has become the primary way they relate to every difficulty in their life. And in that application, it has real costs. You can push through a deteriorating relationship for years, keeping things functional enough that nobody leaves, while the actual connection slowly disappears. You can endure a job that's making you miserable by just tolerating it better than anyone else would. You can override your own signals so effectively that by the time your body or your psychology forces you to pay attention, the problem is much larger than it needed to be. The mentality that makes endurance athletes and operators exceptional isn't neutral. Applied indiscriminately, it's a way of avoiding things that deserve attention.
12 The Different Skill: Knowing when to stop Thursday 8–9 AM
Hook (first 2 lines)
In an ultramarathon, there's a skill that doesn't get talked about much: knowing when to stop.
Finishing is a virtue. But so is dropping out of a race that's going to injure you in a way that ends your season. The athletes who last for decades learn to tell the difference. The ones who don't end up pushing through signals that were trying to protect them. I think about that a lot in my work with executives and leaders. The endurance capacity that makes you effective, the ability to keep functioning through difficulty, to not be derailed by discomfort, to stay composed when everything is chaotic, that's an asset. Genuinely. But it can also become a way of deferring things that deserve your attention now: a relationship that's going quiet, a health signal you've been noting and setting aside, an internal accumulation of pressure you've been managing by performing even harder. The most sophisticated move isn't always pushing through. Sometimes it's being willing to stop and look at what's actually there. That's a skill too. And for people who've spent their careers mastering endurance, it often takes the most deliberate work.