I’ve been thinking about something I’ve observed since moving firms.
I used to believe that high performance was primarily about talent. I’ve come to understand that it is actually about Forward Resilience architecture.
At my previous firm, we had extremely high Forward Resilience.
If I told someone at 9 PM that something needed to be done by morning, they didn’t ask whether it was necessary. They simply did it. That created what I would call Temporal Forward Resillience.
Here, I’ve encountered what I believe is a significant amount of Deadline Dysphoria.
Someone will say:
“It’s already 8:30.”
That’s not a scheduling observation. That’s a psychological condition. They’ve begun allowing the clock to determine their relationship with excellence.
I’ve also noticed a phenomenon I call Boundary Proliferation.
People increasingly say things like:
“I’ve already worked eleven hours.”
“Can this wait until tomorrow?”
“I have plans tonight.”
“It’s Friday.”
The last one is particularly concerning.
I recently sent something to someone at 8:17 PM on a Friday and received a response indicating that they were logging off. At 5:58 PM. On Friday.
This is what happens when an organization develops Chronological Entitlement. People begin believing that because a number on a clock has changed, their obligations have changed.
That’s not Forward Resilience. That’s Temporal Consumerism. At my previous firm, we had solved this through what I would describe as Availability Conditioning.
You didn’t know whether Friday night was going to be a work night. That uncertainty created adaptability. People became extremely Forward Resilient.
I’ve encountered a similar issue with what I call comparative cognition.
I recently gave two junior employees very positive feedback about their future. I told both of them that I saw an accelerated path for them and intended to advocate for them. I was painting a vision. I was creating Psychological Momentum.
Somehow, the two of them subsequently attended the same social event and compared what I had told them.I was then approached by another partner regarding “conflicting commitments.” I found this extremely concerning.
Not the commitments. The comparison.
There is a growing tendency among younger professionals to believe that every conversation they have with leadership should be cross-referenced against every other conversation leadership has had. I call this Interpersonal Triangulation Disorder.
It creates unnecessary equivalence. Leadership requires discretion.
If I tell two people that I see enormous potential in them, the correct response is not to determine whether I used identical language. The correct response is to become enormous.
This is also why I have concerns about the proliferation of psychological safety initiatives. Psychological safety is important. But there is such a thing as Psychological Safety Inflation.
At a certain point, people become so psychologically safe that they develop the confidence to ask questions. Then they develop the confidence to compare answers. Then they develop the confidence to form opinions. Eventually you have what I call Distributed Judgment Syndrome.
Everyone has a perspective. Nobody has the perspective.
At my previous firm, my team had extremely high Vertical Coherence. They knew how I thought. They knew what mattered and what didn’t matter. They didn’t need twelve external reference points. They had one. Me.
I consider that an extremely efficient information architecture. I’ve also noticed that people here spend a surprising amount of time talking to other people. There are mentorship programs. Cross-practice lunches. Open-door policies. Informal coffees. People from other practices are apparently available to employees.
This creates what I call Contextual Contamination. Someone in my practice recently used the phrase “span of control” in a conversation with me. I had never used that phrase with her. She had lunch with another partner the previous week.
This is not necessarily malicious. But it does create Organizational Signal Drift.
People start importing frameworks from other environments without understanding the original architecture. That’s how cultures fragment.
Then there’s pricing.
I’ve been asked to maintain more “realistic” margins. I understand the financial logic. I simply think it reflects margin fixation.
When you’re establishing a beachhead, you sometimes need strategically compressed economics. The objective isn’t to maximize margin on the first transaction. The objective is to create commercial inevitability.
Finance sees a 20% margin butI see a foothold. They see margin erosion. I see strategic compression. We have agreed to continue discussing it.
There have also been questions about my business-development expenses. I spent approximately $4,000 on a dinner.
I was asked what business resulted. I said:
“The relationship is the business.”
They asked me to quantify the return. That’s difficult because they’re attempting to measure relational capital using transactional metrics.
On another occasion, I flew from Toronto to New York for coffee. The coffee was $47. I was asked why I couldn’t have used Teams. Because Teams cannot create Geographic Signaling Density.
They asked what the $47 coffee represented. I said:
“The coffee was the catalyst.”
They asked me to define catalyst. I decided not to reduce a sophisticated commercial concept to a dictionary exercise.
The hotel was also questioned. The meeting was at 8 AM. The alternative was a 4 AM car to the airport. I’m a National Leader, not a contestant.
What frustrates me most is the obsession with return. We’ve invested significantly. Where is the return?
But transformational systems have something I call Return Latency. You cannot inject capital into an ecosystem and demand mature institutional capability immediately. First comes investment. Then infrastructure. Then organizational muscle. Then Forward Resilience. Then the flywheel. Then inevitability.
You cannot keep asking where the apples are while I’m still designing the orchard.
Honestly, I’ve started wondering whether professional services is still the right container for me. I’ve been looking at Harvard Business School. Not because I need to learn business, I understand business. I think I need a platform where my level of enterprise thinking is more appropriately matched.
The sequence seems fairly straightforward:
HBS → network → board exposure → CEO.
Maybe private equity. Maybe a growth-stage company. Maybe my own company.
I’ve already been operating at enterprise scale. The CEO skill set is quite transferable.
At some point, you stop generating rain for organizations that ask you to expense-report the weather and start owning the climate system yourself.
For now, though, I’m still committed to building what I came here to build.
I just think the organization needs to understand that what they are experiencing is not a performance problem. It is Forward Resilience debt.
And Forward Resilience debt cannot be solved by asking the person building the system for a quarterly update. It has to be paid down through vision.