![\"Hierarchical](\"/article-assets/okr-metodo/okr-metodo-gerarchico-cima-piano.jpg\")
OKRs (Objectives and Key Results) are a method for setting and reviewing goals that ties a qualitative objective to a small number of measurable key results, usually over quarterly windows. They are not the same as KPIs (which measure current health) and they do not replace the strategic plan (which sets the underlying direction over 1-3 years). Nor are they the same as the Management by Objectives (MBO) of the 1950s: unlike MBO, OKRs run on a quarterly cadence, keep goal setting sharply separate from performance appraisal and openly allow for ambition. The method has a documented history in the international tech ecosystem, but applying it to smaller organizations requires scaling it down and simplifying it.
\nFormal goal-based planning is still uncommon among Italian companies: among those engaged in innovation, only 18.3% tie their projects to a predefined budget [1]. The sections below explain what OKRs are, how to write them, how to review them and the most common mistakes.
\nOKRs are a method for translating strategy into measurable goals over short windows, where each qualitative goal (Objective) is paired with three to five quantitative key results (Key Results). The Italian Permanent Census of Enterprises shows how rarely ownership of goals is assigned: only 20.8% of Italian companies engaged in innovation have designated an internal unit or person responsible for their projects [1]. The operational distinction from KPIs is the first thing to settle, so you don't confuse tools that measure health with tools that drive a leap forward.
\nFor a company with 30 employees, are OKRs more useful than KPIs, or complementary to them? KPIs and OKRs answer different questions — treating them as synonyms weakens both.
\nThe line between the two tools is clear. KPIs (Key Performance Indicators) measure the current health of a process or result: operating margin, on-time delivery rate, customer satisfaction. They answer the question \"how are we doing?\". OKRs describe the change of state the company wants to achieve within a defined horizon: they don't measure current health, but the distance from the desired destination. They answer the question \"where do we want to be in the next 90 days?\". They are complementary, not alternatives: KPIs measure the engine, OKRs point to the destination.
\nThe third category to keep separate is individual performance goals, typical of annual appraisal systems. OKRs are not a tool for evaluating people: when they are used to measure individual performance, people stop setting ambitious goals and pick the ones that are easiest to reach. A clean separation between team/company OKRs and individual appraisal is one of the founding principles of the method, as documented in the reference literature [4].
\nTo integrate OKRs with the health indicators that run alongside them, see how to choose company KPIs and the guide to business strategy.
\nA useful objective is a qualitative sentence that describes a desired state of the company at the end of the quarter, phrased so that it is memorable and verifiable. A generic objective (\"improve service quality\") doesn't guide choices, because any activity can be linked to it. A useful objective lets you answer the question \"if we do X, does it bring us closer to this objective or further from it?\".
\nHow many objectives can a company reasonably keep active at the same time? A quarter with ten objectives is a quarter without priorities.
\nA well-written objective meets three operational criteria. The first is memorability: people must be able to remember the objective without reading the document. Sentences of 10-15 words, in plain language, phrased as a desired state (\"be the preferred supplier for customers in segment X in Northern Italy\") work better than abstract wording. The second criterion is ambition: an objective that describes what the organization would do anyway, without effort, is not a strategic objective — it is routine. Ambition doesn't mean being unreasonable: it means that achieving it requires a real change in behavior or priorities. The third criterion is alignment: every objective must connect to an annual goal or a priority in the strategic plan. If an objective doesn't connect to anything larger, it is an operational goal, not a strategic one.
\nA few examples of turning a generic objective into a useful one: \"improve customer service\" becomes \"cut the average response time to support requests from 48 to 12 hours this quarter\"; \"grow sales\" becomes \"win 3 new customers in the manufacturing segment in Northeast Italy with signed contracts by the end of the quarter\"; \"optimize internal processes\" becomes \"eliminate manual reconciliation between the order system and invoicing\". For the link between quarterly goals and the strategic plan upstream, read the guide to strategic planning.
\nA reasonable number of objectives active at the same time is 2-4 per quarter per functional area. Going beyond that has a paradoxical effect: the more goals you declare, the less real attention each one gets.
\n\n\n
Key results are the measurable results that, once reached, show that the objective has been achieved. They must be outcome indicators, not activity indicators: \"customer renewal rate at 75%\" is an outcome, \"make 50 calls a month\" is an activity. Research on goal setting shows that specific, challenging goals lead to higher performance than vague \"do your best\" goals [3]: that is why a key result should be written with an explicit baseline and target.
\nHow many key results per objective is reasonable? More than five key results per objective create confusion; fewer than three leave you with a single line of verification.
\nThe main test of whether a key result is well written is the outcome vs. activity test. An outcome describes an observable change in the outside world (in customer behavior, in process data, in the company's results): \"the activation rate of new contracts rises from 30% to 45%\", \"average delivery time drops from 7 to 4 working days\". An activity describes what the organization does internally: \"run 3 training workshops\", \"write 5 procedures\". Activities can be KRs only if completing them is the only way to reach the outcome, and even then it is better to state the expected outcome.
\nThe concept of a stretch goal is central to understanding how ambitious KRs should be. The OKR method treats a key result reached at 70% as a good result: this is because KRs are set at a level of ambition that requires real change to reach 100%. A KR that hits 100% every quarter is not ambitious enough — or the review processes aren't working well. This logic must be communicated explicitly before adopting the method; otherwise the team reads 70% as a failure [4].
\nEvery key result needs a starting value (baseline), a target value and a person responsible for measuring it. Without a baseline, it is impossible to measure progress objectively. To integrate the health KPIs that accompany OKR measurement, see how to choose company KPIs.
\nAligning OKRs across levels (company, function, individual) is one of the most delicate parts of the method: a cascade that is too rigid creates bureaucracy, one that is too loose leaves goals disconnected from each other. The operating rule is that lower-level OKRs must \"contribute to\" those of the level above, not duplicate them. In a company with 15-100 employees, two or three levels of OKRs are usually enough.
\nHow many levels of OKRs make sense in a smaller company? A four-level OKR cascade is administration, not an alignment method.
\nThe practical setup for a mid-sized company has two main levels. The company level holds the OKRs that express the priorities of the whole organization for the quarter: 2-4 objectives with their key results, approved by senior leadership. The function level (or team level) holds the OKRs of individual departments or areas: each contributes to one or more company objectives without duplicating them. In some smaller companies (under 20 employees), the function level can coincide with the company level, and there is no need to add an individual level.
\nThe operating principle is \"contribute to, not copy\": function OKRs are not the company OKRs rewritten in different words, but a statement of how that function contributes to the shared result. A company objective such as \"improve customer satisfaction\" can be supported by a sales OKR (\"cut response times to requests\"), a production OKR (\"reduce the share of late deliveries\") and an administration OKR (\"complete invoicing within 24 hours of delivery\"): three different contributions, one shared objective.
\nThe difference from Management by Objectives (MBO) matters here: MBO builds the cascade from the top down, with goals handed down level by level and tied to individual appraisal. OKRs combine goals set from the top with goals proposed from the bottom, with no link to performance appraisal. This difference changes the way people relate to their goals.
\nThe review cadence is the practice that separates living OKRs from OKRs on paper. In goal-setting theory, feedback on progress is one of the moderators that make goals effective: without information coming back, even a well-written goal has no effect on performance [3]. A light quarterly review (2 hours) closes the cycle; a weekly or biweekly check-in (15 minutes) keeps it alive.
\nIs a monthly OKR review excessive or necessary? Reviews that are too frequent dissolve the quarterly nature of the method, but the external picture changes quickly: Bank of Italy surveys show Italian companies stepping up investment one year and planning to cut it the next, especially in manufacturing and among smaller firms [2].
\nThe quarterly ritual has three moments. The end-of-quarter review (2 hours, structured format) closes the cycle: for each KR you record the actual value, assess progress (usually on a 0-1 or 0-100% scale), identify the main cause of the result (positive or negative) and decide whether the objective is closed or carried over to the next quarter. The weekly check-in (15 minutes, fixed agenda) maintains visibility: each KR owner updates it with the current figure, blockers are flagged and actions for the week are identified. The planning session for the next quarter (2-3 hours, held 2 weeks before the quarter ends) sets the new OKRs: you don't wait for the end of the quarter to plan the next one. For the specific ritual of running reviews efficiently, read effective business meetings.
\nThe sign that the system is working is the team's ability to answer the question \"which KR are we behind on, and why?\" in under 5 minutes during the weekly check-in. If the answer requires digging through spreadsheets, the monitoring system is not visible enough.
\nThe most common mistakes companies make with OKRs are not about wording: they are about the system (tying OKRs to individual appraisal), about numbers (too many at once) and about discipline (skipping reviews). Adoptions that fizzle out within a few quarters almost always stop for process reasons — skipped reviews, too many open goals, overlap with performance appraisal — not because of flaws in the method. Recognizing these mistakes before adopting the method lowers the chance of abandoning it.
\nWhich of these mistakes does more damage: tying OKRs to individual appraisal or keeping too many active? Both lead to the same result — a method people put up with instead of using.
\nThe six most frequent mistakes, each with a small operational fix:
\nTying OKRs to individual appraisal. When reaching OKRs determines rewards or penalties, people stop setting ambitious goals. Fix: keep the OKR system completely separate from the individual performance appraisal system. OKRs measure progress toward team goals, not individual performance.
\nToo many OKRs active at the same time. More than 4-5 active objectives in a quarter spread effort thin and make useful reviews impossible. Fix: limit company objectives to 3-4 and KRs per objective to 3-5. Choosing what not to do is an integral part of the process.
\nKRs written as activities instead of outcomes. \"Run 3 workshops\" is not a key result: it is an activity. If the workshop doesn't produce the desired change, the KR is met but the objective doesn't move. Fix: write every KR as an observable outcome, applying the test \"does this KR measure what changes in the world, not what we do internally?\".
\nA cascade that is too rigid. OKRs are assigned top-down with no room for teams to contribute to writing them. Fix: apply the \"contribute to, not copy\" principle: the company level sets the company objectives, and teams propose their own OKRs, stating how they intend to contribute.
\nSkipping reviews. The weekly check-in is seen as one more meeting and is gradually dropped. Fix: fold the OKR update into an existing meeting (e.g., the 30-minute weekly briefing) rather than creating a separate ritual. Fifteen minutes of KR updates are enough if the monitoring system is visible.
\nOngoing confusion with KPIs. The team uses OKRs to track current health KPIs (margin, revenue, on-time rate) instead of describing the desired changes of state. Fix: draw an explicit line between the \"health dashboard\" (KPIs, updated monthly) and the \"improvement plan\" (OKRs, by quarter). The two tools live in separate spaces and answer different questions.
\nOKRs work best in organizations with at least two or three levels of goals (company and function), where aligning different people is a real challenge. For companies with fewer than 10 employees, where everyone works on the same goals with direct visibility, formalizing OKRs can be out of proportion to the benefit: in these cases it is better to start from a shared quarterly priority list (3-5 goals, with outcome indicators) without the formal objective/key results structure.
\nThe ISTAT data cited [1] come from the Italian Permanent Census of Enterprises with at least 3 employees, reference year 2022. Whether the conclusions carry over to specific sectors (crafts, professional services, early-stage startups) should be assessed against your own context.
\nJohn Doerr's book \"Measure What Matters\" [4] is treated as a source for framing the method, not as a source of empirical data on its effectiveness. Evidence on the impact of OKRs on company performance in small and mid-sized Italian companies is still limited and does not support causal conclusions. This is an operational approach with a documented history in large tech companies and high-growth startups, and transferring it to smaller organizations requires adaptation.
\nThe method does not suit every phase of a company's life: during acute crises or restructuring, quarterly planning may not keep pace with events. In these situations it is better to use priority management tools with a shorter horizon (weekly or monthly).
\nWhat is the difference between OKRs and KPIs?\nKPIs measure current health (how are we doing?): margin, on-time performance, customer satisfaction. OKRs describe the desired changes of state (where do we want to be in the next 90 days?): they are complementary, not alternatives. Treating them as synonyms weakens both.
\nHow many OKRs is it reasonable to have in a smaller company?\nAt company level, 2-4 quarterly objectives with 3-5 key results each. At function level, 1-2 objectives that contribute to the company ones. Going beyond these numbers spreads effort thin without raising ambition.
\nCan OKRs be used to evaluate people?\nNo — this is one of the fundamental distinctions of the method. Linking OKRs to individual appraisal leads people to set easily reachable goals to secure a positive review, removing the ambition that is the method's whole reason for being.
\nHow do you handle a quarter in which the situation changes radically halfway through?\nIf a significant change emerges (loss of a major customer, an unexpected opportunity, an operational crisis), you can update or suspend an OKR during the quarter, documenting the reason. OKRs are not immutable contracts: they are commitments to a direction. The rule is to document every change and discuss it at the final review.
\nWhat is the right frequency for reviews?\nWeekly 15-minute check-ins to maintain visibility; a 2-hour quarterly review to close the cycle and plan the next one. In-depth monthly reviews are optional and mainly useful in the first quarters of adoption, while the method is still settling in.
\nFor a smaller company, useful OKRs are a tool for alignment and review, not a control system. Three elements determine their quality: qualitative objectives written as memorable, ambitious desired states; measurable outcome key results (not activity ones), with explicit baselines and targets; a disciplined quarterly cadence with short weekly check-ins and structured closing reviews.
\nThe boundary with KPIs must stay sharp: KPIs measure the current health of the system (updated monthly), OKRs describe the desired changes of state within the quarter. The two tools coexist and complement each other; overlapping them creates confusion and reduces the usefulness of both.
\nThe sign that the method works is when, at the end of the quarter, the team can answer three questions: what we achieved, what we didn't achieve and why, and what we change next quarter. If finding the answers takes more than an hour, the monitoring system is not visible enough.
\n[1] ISTAT, \"Censimento permanente delle imprese 2023 — primi risultati\", Istituto Nazionale di Statistica, November 2023. Available at: https://www.istat.it/it/files/2023/11/REPORTCensimprese.pdf
\n[2] Banca d'Italia, \"Indagine sulle imprese industriali e dei servizi nell'anno 2025\", Banca d'Italia — Statistiche, July 2026. Available at: https://www.bancaditalia.it/pubblicazioni/indagine-imprese/2025-indagini-imprese/index.html
\n[3] Locke, E. A., Latham, G. P., \"Building a practically useful theory of goal setting and task motivation: A 35-year odyssey\", American Psychologist, 57(9), 705-717, 2002. Available at: https://doi.org/10.1037/0003-066X.57.9.705
\n[4] Doerr, J., \"Measure What Matters\", Penguin Random House, Italian edition 2019. (classic operational reference for framing the method; not a source of empirical data on its effectiveness in small and mid-sized Italian companies)
\nFor a smaller company, useful OKRs are not an exercise in importing a method: they are a tool for alignment and review that ties memorable qualitative objectives to measurable outcome key results over quarterly windows. Light alignment across levels, a disciplined review cadence and a clean separation from individual appraisal are the three elements that separate living OKRs from OKRs on paper.
\nThe thread that ties these elements together is consistency across horizons: the strategic plan sets the course over 1-3 years, OKRs translate that course into measurable 90-day leaps, and KPIs measure the current health of the system. For the strategic level upstream, also read the guide to strategic planning; for the operational distinction between health indicators and leap indicators, see how to choose company KPIs.
\nA company that uses OKRs as a living tool aligns people and functions without bureaucracy, knows what to push forward and what to postpone, and closes each quarter with an honest reading of what worked and what didn't. It is a calmer, less scattered way of working — open to organizations of any size, as long as the method remains a tool for alignment, not a control system.
","headings":[{"level":2,"text":"Tell OKRs and KPIs apart before choosing company goals","id":"tell-okrs-and-kpis-apart-before-choosing-company-goals"},{"level":2,"text":"Write objectives that actually guide the company's choices","id":"write-objectives-that-actually-guide-the-companys-choices"},{"level":2,"text":"Build measurable key results that give a signal, not a verdict","id":"build-measurable-key-results-that-give-a-signal-not-a-verdict"},{"level":2,"text":"Align OKRs across levels without creating a bureaucratic cascade","id":"align-okrs-across-levels-without-creating-a-bureaucratic-cascade"},{"level":2,"text":"Set a quarterly review cadence that doesn't turn into an endless meeting","id":"set-a-quarterly-review-cadence-that-doesnt-turn-into-an-endless-meeting"},{"level":2,"text":"Common mistakes when companies use OKRs","id":"common-mistakes-when-companies-use-okrs"},{"level":2,"text":"Limits and conditions of applicability","id":"limits-and-conditions-of-applicability"},{"level":2,"text":"FAQ — Frequently asked questions","id":"faq--frequently-asked-questions"},{"level":2,"text":"Operational summary","id":"operational-summary"},{"level":2,"text":"Sources and references","id":"sources-and-references"}],"tldr":"Is it worth introducing a formal method like OKRs, or should you keep managing goals through meetings and shared spreadsheets updated from memory? The answer depends on how many people need to align on the same goals, how fast priorities change and how much review discipline the organization can sustain.","tldrItems":null}