The scorecard tracks input metrics which are the activities and outputs you can see moving week to week. Conversion rates are too slow-moving for weekly tracking. If you only get 20 leads a week, your activation rate will swing between 10% and 50% based on random variation. Input metrics show you whether the machine is running.
Demand generation metrics
- Ad spend: Are we investing the planned budget?
- Impressions: Are ads actually running and reaching people?
- Clicks or sessions: Is traffic arriving?
- Cost per click: Is efficiency within an acceptable range?
Marketing funnel metrics
- New leads captured: Is volume on track?
- Leads contacted or nurture emails sent: Is follow-up happening?
- Meetings booked: Are leads converting to conversations?
Sales pipeline metrics
- Discovery calls held: Is sales activity happening?
- Proposals sent: Are deals progressing?
- Deals moved to next stage: Is the pipeline flowing?
- Pipeline value created: Is enough new opportunity entering?
Customer value metrics typically do not belong on the weekly scorecard. Retention and expansion move on longer timeframes. Track those monthly or quarterly instead. Each metric must have one owner. Ownership means accountability. Even if multiple people contribute to a channel, one leader reports the total number and carries the responsibility for its health.
To make decisions fast, every metric on your scorecard needs a status. This is not about blame; it is about visibility.
- Green: You are on track. No discussion is needed.
- Orange: You are behind but you have a plan. For example, a campaign was paused for a creative refresh but is now back online. This goes on the issues list briefly to confirm the fix is in motion.
- Red: You are behind and stuck. You do not know why the numbers are down or you do not have the resources to fix it.
Red items are the absolute priority. For instance, if your "proposals sent" metric is red for two weeks, the team needs to investigate why. You might find that the sales team is bogged down by poor-quality leads from a new campaign. The course correction might involve tightening lead qualification criteria immediately to protect the win rate.
The issues discussion is the meat of the weekly meeting. While reporting numbers is necessary, the actual growth happens during these forty five minutes. To ensure this time does not devolve into a series of aimless updates or circular debates, we use the Identify, Discuss, and Solve (IDS) method inspired by the Entrepreneurial Operating System. The goal is to move beyond symptoms and fix the root causes of why a metric is red.
Identify the root cause
The first step is to identify the real problem. Often, what is raised on the scorecard is merely a symptom. If a sales rep reports that meetings booked is red, the initial instinct might be to tell them to work harder. However, when you dig deeper, you might find that the real issue is a broken calendar integration or a sudden influx of spam leads from a new marketing campaign.
You must stay in the identify phase until everyone is clear on the actual problem. A useful technique here is to ask why several times. Why are meetings down? Because the lead quality is poor. Why is the quality poor? Because we changed our targeting on LinkedIn. Now you have identified the root cause that needs a solution.
Discuss with focus
Once the issue is clearly identified, the team enters the discuss phase. This is the space for everyone to offer their perspective, data, and potential solutions. The rule for this section is simple: you only say it once. Once everyone has had their say, further discussion becomes repetitive and wastes time.
The facilitator’s job is to keep the conversation focused on the root cause identified in the first step. If the discussion starts to drift into other topics or general complaints, it must be pulled back. The objective is not for everyone to be heard for the sake of talking, but to surface the most efficient way to turn that red metric back to green.
Solve with clear actions
An issue is only solved when a specific action is assigned to a specific person with a specific deadline. You are not looking for a perfect, permanent solution every time; you are looking for the next right move to course correct.
In a B2B environment, the solution might be to pause a failing ad set, rewrite a landing page headline, or schedule a training session for the sales team on a new product feature. The solution is recorded as a task for the coming week. If the issue is so large that it requires a strategic shift, the solution is to move it to a separate breakout meeting or flag it for the monthly review.
The meeting only moves to the next issue once the current one has a documented resolution. By the time the forty five minutes are up, the most critical risks to your monthly plan should have clear, actionable paths to recovery.
The weekly scorecard runs in parallel to your monthly initiatives. While your team is busy executing the growth bets you placed during monthly planning, the scorecard acts as a diagnostic tool for the existing engine. This parallel structure allows you to maintain the "run" part of the business while simultaneously building the "grow" part. Without this distinction, teams often find that their new initiatives succeed, but their baseline performance collapses because nobody was watching the pulse.
Avoiding the end of month scramble
A significant advantage of this weekly rhythm is the elimination of the end of month panic. In many B2B organisations, the final week of the month is a chaotic attempt to "save" the numbers. This usually involves high-pressure sales tactics or vanity marketing spend that hurts the business in the long term.
When you course correct weekly, these spikes in stress are replaced by small, manageable adjustments. If you are ten per cent behind on your lead target in week one, a minor tweak to your ad copy can fix it. If you wait until week four to realise you are forty per cent behind, no amount of effort can recover that lost ground.
- The bad journey: A team ignores their low "discovery calls held" metric for three weeks. On day twenty five, they realise they will miss their revenue target. They start spamming their database with "urgent" demo offers, which damages their brand reputation and leads to high unsubscribe rates.
- The good journey: The team sees the red status in week one. They identify that the automated booking link was broken for forty eight hours. They fix the link and send a personal apology note to the affected leads by week two. By week four, the numbers are back on track with zero brand damage.
Cultivating a culture of radical honesty
The weekly scorecard eventually changes the culture of the growth team. It moves people away from defensive reporting and toward proactive problem solving. In a high performing team, people are not afraid to report a red metric. In fact, they take pride in spotting it early.
A red status is not a personal failure; it is a request for the team's brainpower. When you remove the stigma of "missing the target" and replace it with a system that rewards early detection, you gain a level of transparency that most companies never achieve. You stop arguing about whose fault it is and start arguing about how to fix the machine.
The transition from pulse to review
By the time you reach the end of the month, you should already have a very clear idea of what the results will be. The monthly review then becomes a formalised version of the data you have been looking at every seven days. You are not discovering your performance for the first time; you are simply confirming the trends you have been managing all month.
This weekly discipline ensures that your monthly review is spent on high-level strategy and learning, rather than basic data entry and damage control. You have watched the data move every single week, and you have tweaked the machine in real-time. With the engine now humming at a consistent pace, you are ready to zoom out and conduct a formal monthly review.
%2520(1).webp)
