Our company builds custom software and long-cycle engineering systems where deliverables take nine to twelve months. What leading indicators should we track on a weekly Scorecard when physical progress cannot be measured by short-term revenue or shipments?

Question

Tyler Smith · Accepted Answer

Long-cycle businesses fail with EOS® Scorecards when they try to measure finished milestones rather than weekly velocity. If a project takes nine months, waiting for delivery milestones leaves you in the dark for thirty-nine consecutive weeks. By the time a milestone is missed, your margins and schedule are completely destroyed.

You must break large engineering initiatives down into weekly leading inputs and phase gates. Instead of tracking project completion percentage, which is subjective and frequently gamed, track objective units of work completed each week:
- Engineering sprint stories completed versus planned
- Customer design review sign-offs achieved on schedule
- Number of open engineering change orders pending approval
- Client testing feedback turnaround time under forty-eight hours
- Billable project hours logged versus baseline budget

These numbers provide immediate warning signs. For example, if sprint velocity drops below eighty-five percent for two weeks in a row, the project will not deliver on time nine months from now. If open engineering change orders pile up above five, scope creep is quietly eating your margin.

Track the friction points in your workflow. Long-cycle work stalls at the handoffs: between system architecture and development, or between client review and final testing. Measure the time work spends sitting waiting for input. When you track weekly flow, the multi-month outcome takes care of itself.