My leadership team understands that lagging financials do not belong on our weekly Scorecard, but now they are stuffing it with project status updates like 'Phase 1 complete.' How do we draw a hard line between leading activity-based indicators and project milestones?

Question

Tyler Smith · Accepted Answer

Project milestones and scorecard metrics are entirely different tools. Milestones are binary: they are either done or not done, and they belong on your Rocks list, not on your weekly Scorecard. Your weekly Scorecard is designed to measure the raw, repeatable, activity-based engine that drives those outcomes. To draw a hard line, ask yourself if the number can be counted every single week. 'Phase 1 complete' is a one-time event. Instead, you must measure the weekly inputs that make that milestone possible. For example, if you are building a new software integration, do not track project milestones on your weekly Scorecard. Track the number of development hours logged, the number of bugs identified, or the weekly code commits. If you are rolling out a new training program, track the number of employees trained each week. Your weekly metrics must be numbers that can go up or down every seven days, providing a continuous pulse. When you mix project milestones into your Scorecard, you dilute its predictive power. You end up with a static list that fails to highlight operational friction until it is too late. Keep your project milestones in your weekly Rock reviews and keep your Scorecard strictly focused on high-frequency, repeatable activities. If a metric cannot be measured as a weekly count, percentage, or dollar amount every single week, pull it off the Scorecard. This discipline keeps your Level 10 Meeting™ focused on running the daily operational engine, while your Rock review handles the strategic projects.