Examples from the Work

A seasonal surge required bringing dozens of new staff on board in a short window. The default expectation was that the leader would simply work harder — absorb the hours, move faster, make it happen. No one was naming that the role's standard scope was already full before the surge hit.

The role assumed a steady-state workload. The business was producing a non-steady-state moment. The gap between those two was landing on one person as personal effort — not on the structure as a capacity question. "Work harder" was treating a design problem as a willpower problem.

• Built a plan that named the real scope and the real constraint out loud — not as a complaint, as a working document.
• Communicated the tradeoffs laterally to peer leaders so the load was visible, not absorbed inside one role.
• Delegated specific workstreams to other leaders with explicit ownership — not ad-hoc help.
• Kept a single source of truth so nothing dropped when things moved fast.

The surge was delivered on schedule. The outcome got attributed externally to "effort under a tight deadline." What I understood internally was different: the result came from naming the structural constraint and redesigning around it, not from heroism. That distinction is the diagnostic KCG carries into every engagement now.

The senior leadership team kept shrinking — time off, leaves, transitions. Strategy changes from above were continuous. From the outside, the narrative was individual: who would step up and "be resilient" to hold it together. The word resilience was doing a lot of work.

The team wasn't fragmented because of people. It was fragmented because the staffing structure didn't have redundancy for the conditions the business was operating in. A structure designed for stability was being asked to absorb volatility without redesign. What was being called resilience was actually one person absorbing a structural gap that no amount of individual strength could close.

• Named the gap honestly to my own leadership — not as complaint, as information. The team wasn't failing; the structure was understaffed for what it was being asked to do.
• Focused my coverage on what couldn't be delegated — team morale, direct observation, pulse-checking where people were quietly struggling.
• Built the remaining leaders up fast with weekly coaching focused on decision-making, so they could hold authority I couldn't be everywhere to hold.
• Kept communicating laterally so what was happening wasn't invisible to the system above.

The operation held through the year. More importantly — for me — I started explicitly looking for the structural question underneath any problem that showed up as "we need someone to step up." That question became KCG's diagnostic.

I stepped into a leadership role over a team that had operated under settled norms for a long time. The team wasn't broken — they were performing on most measures — but the culture had hardened around a particular way of doing things. The expected playbook was authority-based: move fast, set expectations, push change.

The team's entrenchment wasn't resistance. It was coherence. They had built internal agreements and unwritten rules that let them function for extended periods without active leadership. Any change pushed top-down would be re-litigated against those unwritten rules, and I'd lose. The structural question was: how do I make the unwritten rules visible so we can decide together which ones to keep?

• Resisted the pull toward "good enough" and accepted the short-term discomfort of holding a higher standard.
• Had the direct conversations — including ones about accountability gaps that had been tolerated because no one wanted to name them.
• Developed specific coaching cadences with the team's existing leaders so changes had legitimacy through them, not just through me.
• Slowed my timing when a message wasn't landing — recognizing that the issue was channel and context, not intent.

Leaders on the team developed into their next roles through the coaching work. The outcome externally was about results. The lesson internally was about entrenched systems: they don't resist leadership — they resist leadership that doesn't name their existing structure before asking them to change.

A review cycle came around. Feedback from above rated the work as "meeting expectations." My own instinct was to rate higher — I knew what the work had cost to produce. But when I sat with the rubric, I rated myself lower than I felt I deserved.

I wrote something like this in my self-assessment: the reason I couldn't consistently meet the expectations wasn't a skill or effort gap. It was system limitations, staffing constraints, and accountability issues in the broader team that I'd been navigating around. I was rating myself down because the structure had been rating me down.

That moment — naming in writing that the gap between personal performance and systemic conditions was real, measurable, and unacknowledged — became the seed of the KCG diagnostic. Strong performers absorb that gap and rate themselves down. The structure gets to stay invisible.

• Named it. On the record, in the system designed to evaluate me.
• Didn't dress it up. Didn't soften it into professional language. Wrote the actual thing.
• Later, when I started building KCG, went back and recognized that paragraph was the methodology before I knew I was writing a methodology.

Internally, everything. I stopped looking at "performance" as a measure of a person and started looking at it as a measure of the fit between a person and a system. That lens became the work. It's why KCG's first question, in every engagement, is not "what is wrong with this person?" but "what is the system producing, and what cost is landing on the people inside it?"