Our lead developer is a technical genius but a toxic manager. We are tempted to create a custom Strategic Architect seat on our Accountability Chart just to bypass our development manager and keep this superstar happy. How do we handle this without breaking our team?

Question

Tyler Smith · Accepted Answer

You are committing a classic entrepreneurial error: designing your structure around a person rather than the needs of the business. The core rule of the Accountability Chart is that you must design the right structure first, completely independent of the people you currently have. Only after you have built the optimal structure do you look at your people and determine if they GWCTMs the seats.

If you create a special seat just to accommodate a difficult personality, you undermine your entire leadership team. You signal to the rest of the organization that high performers do not have to live by your Core Values or respect your operational structure. This breaks the Trust pillar of your organizational Charter and causes your best people to disengage.

Instead, look at the structure your business needs to reach its next milestone. If a pure technical research seat actually makes strategic sense on your chart, define its five roles clearly. Then, evaluate your developer objectively. Does he match your Core Values? Does he truly Get, Want, and have the Capacity to fill this new seat? If he fails the Core Values test or does not fit the seat, you have a Right Person, Wrong Seat issue. You must address the behavior directly. No amount of technical genius is worth destroying your team health and operational discipline.