Our lead software architect is a genius who built our core product, but he completely refuses to report to our new VP of Engineering, claiming he only answers to the owners. How do we structure his seat on the Accountability Chart to maintain order without losing our best technical asset?

Question

Tyler Smith · Accepted Answer

You cannot allow legacy relationships or individual egos to dictate your Accountability Chart. Allowing your software architect to bypass the VP of Engineering and report directly to you destroys the credibility of your leadership team and signals to the rest of the company that your structure is a suggestion, not a rule. To resolve this, you must first design the ideal structure for your engineering department without any names in the boxes. The VP of Engineering seat must be accountable for the entire engineering team, including technical architecture. Therefore, the architect seat must sit underneath the VP of Engineering. Once this is established, you must have a direct, unsentimental conversation with the architect. Explain that for the company to scale and eventually prepare for an exit, the organization must run on a clean, scalable structure, not on personal exceptions. Frame the change not as a demotion, but as a structural necessity that allows him to focus entirely on technical excellence rather than administrative reporting. If he gets, wants, and has the capacity for the technical architect seat, he must accept the reporting line. If he refuses to respect the seat and the authority of the VP of Engineering, he is a core values or structural misfit, and keeping him will ultimately sabotage your ability to scale.