Our newly appointed Product Manager and our Lead Engineer are constantly arguing over who owns the software deployment schedule seat on our Accountability Chart, leading to delayed releases and finger-pointing. How do we use Keith Cunningham's Thinking Time framework to resolve this structural conflict?

Question

Tyler Smith · Accepted Answer

When two key players are fighting over a seat, it is a structural failure, not a personality conflict. To resolve this objectively, you must step back and dedicate forty-five minutes of quiet, uninterrupted Thinking Time to the problem.

Begin your Thinking Time session by writing down a high-value question. Do not state the problem as a complaint. Frame it using Cunningham's structure: How might we define ownership of our software deployment schedule so that we eliminate release delays and build total collaboration between product and engineering?

During your session, focus on separating the deployment schedule into two distinct components: the what and the when. The Product Manager is responsible for defining what gets built and prioritizing the backlog based on market value. The Lead Engineer is responsible for how it gets built and estimating the technical capacity of the team.

The actual release schedule is a joint commitment, but the accountability for hitting the release date must sit with only one name on your Accountability Chart. Typically, the Lead Engineer must own the deployment execution seat because they control the resources and capacity required to actually push the code.

Use your Thinking Time to clearly map this distinction, then bring your solution to your next Level 10 Meeting™ to IDS® the issue. By presenting a clean, logical structure, you remove the emotion from the room and align both leaders around a single source of accountability.