The CEO of a garment manufacturer in the Vale do Ave told us two years ago: "OKRs are a Vale fad. We have objectives — we sell X per month." Six months later, when his largest client asked for overtime traceability and deadline compliance, he realised that his "objectives" weren't talking to the operation. Overtime kept rising. Deadlines kept being missed by 3-5 days. Nobody knew why.
This is the real problem with OKRs in Portuguese industrial SMEs: it's not that the strategic objectives are bad. It's that they don't talk to the shop floor, the warehouse or the back office. And when they don't, all the OKR bureaucracy turns into paper that nobody reads. Worse: the company keeps losing money without knowing where.
OKRs are not an HR process — they are an operational device
We see many companies confuse OKRs with "individual employee objectives" or "sales targets". They are not. OKRs are a method for linking strategy to daily operations — and that means they have to touch the shop floor, the warehouse, the checkout line. They have to generate visibility about what is stopping the objective from being achieved.
In a typical textile factory with 120 employees, the strategic objective may be "grow gross margin by 15%". But the operation doesn't see "gross margin" — it sees "output per shift", "rework", "setup time", "absenteeism", "energy consumption per kg processed". If the OKR doesn't translate "gross margin" into at least 3-4 operational metrics that the shop floor can control and measure daily, the objective is left hanging in the air.
An OKR without operations is a document. Operations without an OKR is well-intentioned chaos.
This is contrary to what many consultancies say — that OKRs are a top-down strategic alignment exercise. We believe that OKRs in industrial SMEs have to be bidirectional: strategy sets the destination, but operations say what is possible and what will get in the way.
The Portuguese mistake: confusing OKRs with the annual plan
In Portugal, the business ritual is the annual plan. A meeting in September, objectives for the year, distribution of targets by department, review in December. Done. Then, for 12 months, nobody looks at that paper again — unless the audit asks for it.
OKRs are not that. OKRs are a continuous 90-day cycle, with weekly or fortnightly review. This may seem like too much bureaucracy — and it is, if done wrong. But in industrial SMEs, this short cycle is what makes OKRs useful: it allows you to anticipate deviations, adjust priorities and, above all, give the CEO and COO visibility over what is happening in the operation in real time.
Five years ago, we believed OKRs in SMEs should be simplified to an annual cycle. We were wrong. What makes OKRs viable in SMEs isn't making them less rigorous — it's linking them to the data the operation already produces. A distribution company working with stock cycle counting already has daily visibility over inventory accuracy. An OKR of "reduce stock discrepancies from 3.2% to 1.8% in 12 weeks" isn't new work — it's giving meaning and urgency to work that already exists. The weekly OKR review then becomes a conversation: "We're at 2.1%. Why are we still above 1.8%? Wrong picking or counting?" And from that come actions, not reports.
The truth about 90-day cycles in SMEs
90-day cycles work in industrial SMEs because the decision horizon is naturally short. The CEO of a footwear factory in Felgueiras knows they have 60-90 days to respond to an international buyer. The operations director of a garment manufacturer in Guimarães knows the delivery lead time of an order: 4-6 weeks. Ninety days is the time between a major decision (launching a new product, negotiating with a new supplier, investing in equipment) and the effect of that decision on the operation.
This means a 90-day OKR in an industrial SME is realistic. It's not "chasing an abstract metric" — it's an objective the CEO can monitor in the Tuesday meeting with the COO and the production manager. But this requires one thing: data. If you don't have real-time visibility over OEE, cycle time, stock accuracy, overtime, or raw material cost, you can't do 90-day OKRs. You'll be left with OKRs like "sell more", "improve quality" — objectives nobody can control.
Three mistakes we see every week
Mistake 1: OKRs only for the top team. The CEO defines OKRs. The COO cascades them to their team. The warehouse manager never hears about them. Result: the warehouse keeps optimising for "fast picking" (its old KPI) while the strategic OKR asks to "reduce customer returns due to picking errors by 40%". There's no conflict — there's ignorance. The solution is simple: each team has its own OKR, but it has to be derived from the OKR of the team above. The warehouse manager has to be able to explain in half a page how their OKR contributes to the COO's OKR.
Mistake 2: Confusing OKRs with KPIs. A KPI is a metric you monitor continuously — OEE, cycle time, gross margin, turnover. An OKR is an objective you want to achieve within a specific timeframe (90 days). A KPI is "we're at 67% OEE". An OKR is "take OEE from 67% to 75% in 12 weeks". The difference is small but crucial: an OKR requires action, change. A KPI merely tells you where you are. If you mix the two, you end up with 15 "objectives" that are actually passive monitorings of metrics nobody can control.
Mistake 3: OKRs without an owner. Is "improve quality by 15%" an OKR? No. Because nobody is responsible. Is it production? Is it quality control? Is it the supplier? An OKR has to have a name — "João, production manager, will reduce the rework rate from 4.2% to 2.8% in 12 weeks". Does this seem harsher? It is. But it's what makes an OKR actionable.
How to start without bureaucracy
You don't need special software. You don't need consultancy. You need three things: a spreadsheet, a 90-minute meeting with the top team, and the discipline to review the OKR every week. Week 1: the CEO, COO and head of operations (or production/warehouse manager, depending on the company) sit down and define 3-5 OKRs for the next 90 days. Each OKR has a clear metric (a number), an owner (a name), and an initial state (where we are today). This takes 90 minutes if the company already has data on what it wants to change. Weeks 2-13: a 20-minute meeting every Tuesday (or the day they choose). Each OKR owner reports the status. Green, amber or red. If it's red, there's a conversation: what's stopping it? What action to take? What support is needed? Week 13: a 90-day retrospective. Which OKRs were achieved? Which weren't? Why? What did we learn? And then they define the next 3-5 OKRs.
That's all. It's not bureaucracy. It's discipline. And in Portuguese industrial SMEs, where the CEO knows what's going on in the warehouse because they go there every week, this works.
What makes OKRs viable: operational data that already exists
Here's the secret nobody tells you: you don't need new data to start OKRs. You need access to the data the operation already produces. If you have a real-time production capture system, you already have OEE, cycle time, stoppages. If you have an ERP, you already have stock accuracy, raw material cost, delivery lead times. If you have an HR system (even if it's a spreadsheet), you already have absenteeism, overtime, turnover.
The problem is that this data is scattered. The production manager sees OEE on the machine's screen. The CFO sees cost in the ERP. The HR manager sees overtime in an Excel file. Nobody sees the whole picture. OKRs require someone (often the COO or an IT Director) to centralise this data into a single view — a dashboard, a spreadsheet that pulls data from various sources, or a lightweight BI system. This is not a heavy technology investment — it's connecting what already exists.
Most industrial SMEs have enough data to start OKRs. What's missing is the courage to admit that the data they have is imperfect — and to start anyway.
The question nobody asks: how much does your unmeasured OKR cost?
Imagine a garment factory with 80 employees. The objective is "deliver every order on time". But nobody measures this. The production manager knows, from experience, that "most orders go out on time". The CEO believes it. Done. But when the biggest client threatens to leave because 18% of orders arrive 2-3 days late, the company discovers that the "objective" was an illusion. Nobody had measured. Nobody had an OKR. Nobody had action.
According to ManpowerGroup, in 2024, 65% of employers in Portugal had difficulty finding professionals with the required profile — one of the highest talent shortage figures in the world. But this is a symptom of a bigger problem: without clear, measured OKRs, companies can't prioritise what to train, what to recruit, or what to retain. Result: an average voluntary turnover of 10.6% in 2023 (Mercer), with 52% of companies admitting difficulty in retaining talent. This is not an HR problem — it's a problem of lack of operational visibility.
A measured OKR of "reduce turnover from 12% to 8% in 90 days" forces the company to ask questions: who is leaving? Why? Which departments? What is the cost of replacement? What concrete actions reduce departures? Without an OKR, the company spends energy on "improving the climate" (generic) instead of "reducing the departure of shift supervisors because the salary is 8% below market" (specific and actionable).
OKRs and talent retention: the link nobody sees
Most industrial SMEs think talent retention is an HR problem — salary, benefits, climate. Partly true. But the real driver of retention in industrial SMEs is operational clarity. An employee wants to know: where are we going? Does what I'm doing contribute? How does my work change things?
Without OKRs, the answer is "work, do your task, get your salary". With OKRs, the answer is "in 90 days, we want to reduce rework from 4% to 2%. You, as quality manager, are responsible. Here's the data. Here's the plan. We'll review every week. If we succeed, the company grows, and you have visibility that you made a difference".
This is retention. It's not a benefit — it's meaning.
Why OKRs fail in many SMEs (and how to avoid it)
OKRs fail when: (1) the CEO defines OKRs alone, without listening to the operation — result: unrealistic OKRs that nobody can achieve; (2) there's no data to measure — result: OKRs become estimates, not facts; (3) there's no weekly review — result: OKRs are forgotten until the end of the quarter; (4) there are too many OKRs (more than 5 per team) — result: dispersion, lack of priority; (5) OKRs have no named owner — result: diluted responsibility.
To avoid this, start small. One team. One 90-day cycle. 3 OKRs. Data you already have. A 20-minute weekly review. If this works, expand. If it doesn't work, adjust — but don't give up in month 1.
What comes next: OKRs as an operational language
When OKRs work, they change the company's language. It stops being "the CEO wants this" and becomes "our OKR is this, and here's the progress". There stop being "departments that don't talk to each other" and there start being "teams that see how their OKR depends on the OKR of another". There stop being "status meetings" and there start being "action conversations".
This is what makes Portuguese industrial SMEs competitive. It's not expensive technology. It's not management consultancy. It's operational discipline. It's measurement. It's ownership. It's a weekly conversation about what matters.
Frequently asked questions
What distinguishes an OKR from a traditional objective in SMEs?
An OKR is an operational device that links strategy to the shop floor, whereas traditional objectives are left hanging in the air. An OKR requires action and change within a specific timeframe (90 days), with metrics the operation can control daily. Without this link, the objective turns into paper that nobody reads.
Why do 90-day cycles work in industrial SMEs?
The decision horizon in industrial SMEs is naturally short. A CEO knows they have 60-90 days to respond to a buyer. An operations director knows delivery lead times: 4-6 weeks. Ninety days is the time between a major decision and its effect on the operation, making the OKR realistic and monitorable.
How do you translate a strategic objective into operational metrics?
If the objective is "grow gross margin by 15%", the shop floor doesn't see this. You have to translate it into 3-4 metrics the operation controls: output per shift, rework, setup time, absenteeism, energy consumption. Without this translation, the OKR is useless.
What is the most common mistake in Portuguese SMEs with OKRs?
Confusing OKRs with the annual plan. In Portugal, there's a meeting in September, targets are distributed by department, and nobody looks at it again. OKRs are a continuous 90-day cycle with weekly or fortnightly review, which allows you to anticipate deviations and give real-time visibility.
What is an OKR without an owner?
"Improve quality by 15%" is not an OKR — it's vague. An OKR has to have a name: "João, production manager, will reduce the rework rate from 4.2% to 2.8% in 12 weeks". This makes the objective actionable and accountable.
How do you distinguish an OKR from a KPI?
A KPI is a metric you monitor continuously — OEE at 67%, cycle time, gross margin. An OKR is an objective you want to achieve within a timeframe: take OEE from 67% to 75% in 12 weeks. A KPI tells you where you are; an OKR requires action and change.
What resources are needed to start with OKRs?
You don't need special software or consultancy. You need a spreadsheet, a 90-minute meeting with the top team, and the discipline to review the OKR every week. The essential thing is to link the OKR to the data the operation already produces.