tyler-smith.com · Questions & Answers

Our Head of Estimating understands his seat and claims he wants it, but our project volume doubled and he works eighty hours a week manually building spreadsheets instead of adopting automated estimating software. Is this an effort-versus-capacity issue, or does he not actually GWC the seat?

This is a failure of both Capacity and Getting it. Working eighty hours a week is not evidence of capacity; it is proof of a structural bottleneck. In EOS, Capacity does not mean physical endurance or a willingness to sleep under your desk. Capacity means having the emotional, intellectual, and technical bandwidth to execute the seat at the scale the business requires today.

He may claim he understands the role, but if he insists on using manual spreadsheets while your revenue demands automated digital takeoffs, he does not actually understand the modern requirements of the seat. He understands how the job used to be done five years ago, but he is refusing to grasp what the seat requires now. When an employee clings to slow, manual habits because modern tools feel uncomfortable, that resistance proves they do not GWC the future evolution of the role.

Have a blunt, caring conversation. Define the seat based on the future needs of the company: five roles, including digital workflow adoption, accurate margin modeling, and bid turnaround velocity. Give him thirty days to embrace the new software, complete training, and transition his workflow. Offer coaching and outside support.

If he continues to rely on brute-force manual hours rather than adopting scalable systems, you have your answer. He does not have the capacity to scale with your company. Move him to an individual contributor role or replace him with an estimator who can leverage modern automation.

Category: Accountability Chart & Seats

← All questions