Our lead developer is a brilliant technical mind who single-handedly built our core software platform, but he is incredibly disorganized, misses deadlines, and is a terrible manager for his direct reports. How do we handle this Right Person, Wrong Seat situation on our Accountability Chart?

Question

Tyler Smith · Accepted Answer

This is a classic Right Person, Wrong Seat dilemma that many growing businesses face. Your developer aligns with your core values, making him the right person, but he is in a seat that requires management and organizational skills that he simply does not possess or want to use. Keeping him in a leadership seat is a recipe for team dysfunction, missed deadlines, and eventual departures. To solve this, you must separate technical expertise from management accountability on your Accountability Chart. Do not force your brilliant individual contributors to become managers just to get a promotion or a raise. Instead, create a dual-career path structure. Redraw your technology department on the Accountability Chart to have a Tech Management seat, responsible for project deadlines, people management, and resource allocation, and a separate Individual Contributor seat, such as Principal Architect or Lead Developer, which has zero direct reports and focuses entirely on writing code. Move your developer into the Individual Contributor seat where his GWC is a perfect three-for-three match. Then, hire or promote someone who excels at project management and people leadership to fill the Tech Management seat. This structural change respects his unique talents, protects your team from poor management, and ensures your software development actually stays on track.