Our CFO insists that lagging financial metrics like weekly revenue and cash flow are the only real numbers we can trust, while our Integrator wants purely activity-based leading indicators on our EOS Scorecard. How do we resolve this internal tug of war and construct a weekly Scorecard that satisfies both financial reality and operational foresight?

Question

Tyler Smith · Accepted Answer

The conflict between a finance-driven CFO and an operations-driven Integrator is common. Your CFO is trained to look at backward-looking GAAP compliance, which is critical for exit readiness but useless for daily management. Your Integrator needs to know what is happening today to prevent a train wreck next month. To resolve this, you must separate your lagging financial outcomes from your weekly operational activities.

Your weekly EOS® Scorecard should not be a mini profit and loss statement. Out of your five to fifteen numbers, keep only two or three lagging financial metrics, such as cash on hand and accounts receivable over thirty days. The remaining metrics must be leading indicators owned by your operational seats.

For example, instead of tracking weekly revenue, which is a lagging metric, track billable hours completed or project milestones achieved. Instead of tracking sales closed, track outbound discovery calls made or proposals submitted. These activity-based numbers predict your future revenue.

When your weekly leading indicators are green, your lagging financial numbers will follow. If your CFO insists on only tracking lagging numbers, they do not yet understand that the Scorecard is an operational steering wheel, not a rearview mirror. Use the Level 10 Meeting™ to IDS® this misalignment and establish that the Scorecard exists to drive action, not just document history.