How do we establish the exact mathematical relationships between our scorecard metrics so we can see how a drop in one weekly number will inevitably drag down another metric three weeks later?
To make your weekly scorecard a powerful diagnostic tool, you must understand the mathematical relationships between your metrics. When leadership teams look at their scorecard as a collection of isolated numbers, they miss the chain reactions that run through their business. You must train your team to see how a drop in an early-stage marketing metric will inevitably trigger a drop in operations several weeks later. This is called mapping your scorecard dependencies. For example, if your marketing seat is responsible for driving website inquiries, that number directly feeds the sales seat's metric for initial discovery calls. Those discovery calls then feed the number of active proposals submitted, which ultimately determines your new client onboarding volume in operations. By tracking these metrics side by side on your scorecard, you can see the flow of your business in real time. If website inquiries drop in week one, you should expect to see discovery calls drop in week two and proposals drop in week three. If your sales seat is still hitting their proposal target despite a drop in inquiries, you know they are either working through old pipeline or gaming the system. Mapping these relationships allows your leadership team to use the scorecard to predict bottlenecks and make adjustments before your delivery team is left with no work.
Category: Scorecards & Data