Our custom software development agency has grown rapidly, and our two senior technical leads are currently sharing the Lead Architect seat on our Accountability Chart because they refuse to report to one another. How do we resolve this without losing one of our top engineers?

Question

Tyler Smith · Accepted Answer

Having two names in a single seat is a recipe for operational disaster. When two people are accountable for the same seat, nobody is actually accountable. It leads to finger-pointing, missed deadlines, and complete confusion for the rest of the team who do not know which leader to approach for decisions.

You must untangle this shared seat immediately. Start by reviewing the five major roles of the Lead Architect seat. If the work is truly too vast for one person, you may actually have two distinct seats that need to be defined on your Accountability Chart.

For example, you might need one seat focused on internal technical standards and code quality, and another seat focused on client-facing solution architecture and scoping. Each seat must have its own unique set of five roles and its own separate measurables.

If the seat cannot be split logically, then only one person can occupy it. You must have a candid conversation with both technical leads. Determine which of the two truly gets, wants, and has the capacity for the leadership and management aspects of the seat.

The other engineer must transition into a senior individual contributor seat with zero management responsibilities but equal professional prestige. If their egos prevent them from accepting this structure, you have a deeper core value issue that will eventually poison your culture.