How a KPI differs from an OKR
A KPI (Key Performance Indicator) tracks progress against a goal that's already been set, like hitting a set revenue target this month. An OKR (Objectives and Key Results) is a goal-setting method where the ambitious objective itself is defined alongside the key results that indicate whether it was reached. In practice, many teams use OKRs to set the quarter's direction and KPIs as the day-to-day dashboard that shows whether they're actually on track to get there.
Design KPIs using the SMART framework
SMART stands for Specific, Measurable, Achievable, Relevant, and Time-bound. Improve customer satisfaction is a goal statement, not a KPI -- raise the average customer satisfaction score from 4.2 to 4.5 by the end of the quarter is an actual KPI, because it states how it's measured, the target number, and the deadline. Whenever you draft a new KPI, checking it against all five letters catches most of the vague ones before they go live.
Pair leading indicators with lagging indicators
Metrics like revenue, profit, or churn only show up after the fact -- these are lagging indicators, and relying on them alone means you find out about a problem only once it's already happened. Leading indicators, like sales calls booked or new website visitors, move before the lagging outcome does. Tracking new consultations this week alongside monthly revenue lets a team spot a coming revenue dip early enough to actually respond to it.
What good KPIs look like by department
Sales teams commonly track new contracts signed, pipeline conversion rate, and average deal size. Marketing tracks new leads, customer acquisition cost, and conversion rate by channel. Customer support tracks first-response time, resolution time, and repeat-contact rate. Engineering tracks deployment frequency, incident count, and code review turnaround. Rather than copying another department's KPIs wholesale, it's more effective to first define how a given department contributes to the company's overall goal, then work backward to the metrics that reflect that contribution.
Cascade company goals down to individual KPIs
Setting KPIs independently at every department and individual level risks a situation where everyone hits their own number while the company goal still isn't met -- or worse, individual KPIs actively conflict with each other. A classic example: a sales KPI based purely on deal count can push a team to close low-margin deals that directly undercut a company-wide profit-margin target. Cascading -- company goal, then department goal, then team and individual KPIs, each explicitly derived from the level above -- keeps every KPI pointed at the same outcome.
Common mistakes when setting KPIs
Frequent problems include tracking so many KPIs, ten or more, that a team can't actually focus on what matters; picking a headline KPI that's driven mostly by factors the team can't control, like macroeconomic conditions; optimizing the number itself through gaming rather than the underlying behavior it was meant to represent, such as inflating call counts with pointless calls; and never revisiting a KPI even after the market conditions that justified it have clearly changed. A quarterly or half-yearly review of whether each KPI is still actually informing decisions is worth the time.