Our engineering lead has been here since day one and says he wants the new technical VP seat, but his Kolbe shows he is a high Fact Finder and low Follow Thru, and he is completely ignoring our new structured code review system. How do we make the GWC call when he insists he has the capacity?
When a long-tenured leader insists they want a seat but fails to execute the required processes, you have a classic GWC issue. GWC stands for Get It, Want It, and have the Capacity to do it. While this leader may understand the technical requirements and genuinely want the status of the seat, their actions prove they lack the conative capacity to build and maintain the systems your scaled company now needs.
A Kolbe profile showing high Fact Finder and low Follow Thru means this person is wired to investigate and solve complex technical problems, not to build repeatable, structured systems. They are a natural builder of software, not a builder of operational processes.
To make this call objectively, you must separate their historical loyalty from the objective requirements of the seat. Ask yourself if they have shown the behavioral discipline to Lead, Manage, and hold people Accountable. If they are actively ignoring the new code review system, they do not get it, and they do not have the capacity to enforce it with their team.
You must have a candid conversation. Explain that the VP seat requires systemic oversight, which is draining their natural energy. Offer them a technical specialist seat where their brilliant Fact Finder instincts can shine without the burden of system management. This protects their dignity while keeping your Accountability Chart structurally sound.
Category: Accountability Chart & Seats