A weekly KPI earns its place only when a team can name the decision it changes before the next review. “Track revenue” is too broad. “If qualified enquiries fall below twelve this week, the marketing owner will inspect channel mix and response time on Monday” is a usable operating rule. The number, owner, timing, and action belong together.
Begin with one recurring decision that currently depends on instinct or late surprises. It might be staffing a support queue, following up sales leads, protecting delivery capacity, or checking whether a campaign is producing conversations rather than clicks. Write that decision as a question that can be answered every seven days.
Start with the weekly decision, not the dashboard
Then choose the narrowest measure that answers it. A small service team worried about pipeline may learn more from qualified enquiries than total website sessions. A tutoring business may need completed lessons rather than bookings if cancellations create the real cash-flow problem. The best KPI reflects the constraint the team can influence now.
Name a single owner for the definition and follow-up. Other people may supply data or act on the result, but one person must resolve disputes about inclusion, timing, and corrections. Without that ownership, a weekly meeting can spend more time negotiating the number than responding to it.
Give the number one owner and one source
Document the source precisely: CRM report name, spreadsheet tab, accounting export, support view, or analytics event. Include the cut-off time and treatment of late entries. A number that silently changes after the meeting weakens trust. The SBA business guide offers useful context for keeping financial records, but the team still needs its own operational definition.
Set three zones before seeing the result: normal, investigate, and act. Thresholds do not need false precision. They need a pre-agreed response. If enquiries are normally between twelve and eighteen, eleven might trigger a source check while eight triggers a channel and follow-up review. Writing the rule first reduces storytelling after the fact.
Authoritative reference: U.S. Small Business Administration business guide.
Set an action threshold before the meeting
Suppose a three-person studio chooses “qualified enquiries received by Friday 17:00.” The owner is the sales lead, the source is a filtered CRM view, and the action threshold is fewer than ten. Week one records fourteen, week two twelve, week three nine, and week four eight. The important moment is not drawing a downward line; it is performing the agreed investigation in week three.
During that investigation, the team separates volume from response quality. It finds that total enquiries are stable but first replies now take thirty hours instead of six. The weekly KPI did its job by exposing a decision: restore same-day triage before spending more on traffic. A broad dashboard might have hidden that sequence behind averages.
Work through a four-week example
Keep a short note beside each result: what changed, what was checked, what action was assigned, and when the effect will be reviewed. This turns the series into operating memory. It also prevents the same explanation from being rediscovered every Monday.
Do not promote every useful measure to weekly KPI status. Some metrics belong monthly because their signal is slow or noisy. Others are diagnostic measures opened only after the main KPI crosses a threshold. Limiting the weekly set protects attention and makes ownership visible.
Remove the KPI when it stops earning attention
Review the KPI definition after four to six cycles. Ask whether it changed a decision, whether the source stayed reliable, whether the threshold produced useful action, and whether people could influence the outcome. If the answer is repeatedly no, revise or remove it rather than keeping a ceremonial chart.
The next step is simple: write one weekly decision, select one measure, name one owner and source, and define the action threshold before collecting the next result. A small, enforceable measurement habit is more valuable than a crowded dashboard nobody uses.
Weekly Kpi KPI Decision Table: use the worked scenario above to record the evidence, decision, owner, boundary, and review point.
For the adjacent question, continue with Customer Support KPIs Without Dashboard Noise; it covers a different part of the same-site topic cluster.