Universal Weekly Scorecard Template

Yes. It is a plain .docx with no macros and no email gate. Download it, open it in Word, Google Docs or Pages, and use it however you like.

Most teams land between 5 and 15. Below five you cannot see the shape of the business. Above fifteen the review stops fitting in five minutes, and a scorecard nobody reads is worse than no scorecard.

Yes. A weekly scorecard is framework-neutral. In OKRs the metrics often map to Key Results, in Scaling Up to the weekly meeting numbers, and in 4DX the same grid works as a scoreboard for lead and lag measures.

Weekly, in the same meeting, at the same point in the agenda. The rhythm matters more than the format: a scorecard reviewed monthly tells you about a problem four weeks after it started, which is usually four weeks too late to do anything cheap about it.

Both, but a scorecard made only of lagging indicators reports history. Revenue, churn and profit tell you what already happened. Pair each with something upstream you can still act on this week, like qualified conversations booked or onboarding calls completed.

Nothing, the first week. One red week is usually noise. The rule most teams use is three consecutive weeks off target, at which point it stops being a metric discussion and becomes an open issue with a named owner and a root cause to find.

One person, by name, who can actually influence the number. Not a team, not a department, and not the person who happens to produce the report. Shared ownership of a metric reliably produces no ownership of it.

A scorecard is a fixed, short list of numbers with owners and targets, reviewed on a set rhythm. A dashboard is usually a broader, exploratory view. The scorecard is the one you read out loud in a meeting.