We have team members who commit to Rocks with high enthusiasm but consistently stall out around week seven because they hit technical or operational hurdles they do not know how to solve. How do we structure mid-quarter check-ins to unblock these Rocks before they fail?

Question

Tyler Smith · Accepted Answer

Stalling out in week seven is a predictable pattern, often caused by a lack of early visibility or conative misalignment. To prevent this, you must change how you monitor Rock progress during your weekly Level 10 Meeting™.

First, enforce a strict rule that Rocks are only reported as on track or off track. There is no such thing as ninety percent done. If a team member says a Rock is off track, it must immediately be dropped down to the IDS® list. Do not let them explain or defend it during the review portion of the meeting. Solve the roadblock during IDS®.

Second, use conative screening tools like the Kolbe Index to understand how your team members naturally solve problems. A team member with high Quick Start instincts will jump into a Rock with high energy but may lack the Follow Thru instincts required to finish the detailed execution phase. When you identify this gap, pair them with a colleague who has strong Follow Thru strengths to help them map out the final stages of the project.

Third, introduce a formal mid-quarter review in week six. Have every Rock owner present their current progress and identify any dependencies or technical hurdles they foresee. This structured check-in provides a safe space to ask for help before the quarter ends, ensuring that operational fires do not derail your goals.