Our tenured engineering director gave himself straight Yeses on GWC during our People Analyzer quarterly review, but as his Integrator, I know he fails Gets It for modern cloud architecture. How do I bridge a massive self-awareness gap when a legacy leader cannot see their own GWC failure?

Question

Tyler Smith · Accepted Answer

When a long-tenured leader rates themselves a Yes on Gets It while you see a No, you are facing a definition problem, not an attitude problem. Tenured employees evaluate Gets It based on their historical contribution. They think: I built this system fifteen years ago, so of course I get it. You are evaluating Gets It based on what the business requires for the next phase of growth.

Do not debate opinions or abstract technical philosophy. Anchor the conversation directly into the five roles defined for their seat on the Accountability Chart.

Take the specific role in question, such as Technical Architecture and Modernization. Lay out objective, observable outcomes that define getting it at your current scale. Show the gap between the modern architectural standards your roadmap requires and the outdated solutions the department is currently delivering.

Use specific examples from recent quarters: architectural bottlenecks, delayed deployments, or critical technical debt that the team failed to anticipate. Explain clearly: Getting it does not mean you lack intelligence. It means your natural aptitude and current technical depth no longer match the elevated complexity of this seat at our current revenue tier.

Give them a defined timeline, typically thirty to ninety days, to demonstrate genuine grasp of the modern requirements, or work with them to transition into a specialized technical individual contributor seat where their deep institutional knowledge remains an asset without holding the architecture hostage.