Three weeks ago, a COO of a textile factory in the Vale do Ave asked me to count how many "OKR alignment" meetings he had scheduled for the month. Seventeen. Seventeen meetings to establish three production targets and two quality targets. None had begun, and he was already losing 34 hours of management time. This is not management by objectives. It is bureaucracy with an English-language acronym.

OKR works in industrial SMEs because it solves a real problem — dispersed teams, vague targets, lack of operational visibility. But the way most companies implement it kills what makes it useful: it creates more meetings, more slides, more "syncs" than before. The uncomfortable truth is that there is no trade-off between clarity and agility. There is only a choice: continuous operational transparency, or deliberation bureaucracy.

The confusion between OKR and management democracy

OKR was born in technology companies with cultures of open debate. Google, Spotify and Airbnb use it because they have teams of engineers who think in parallel, discuss trade-offs, and need clarity about priorities. It makes sense in that context.

An industrial SME is not a start-up. The production manager does not need to "co-create" the OEE target with the entire factory. They need to know, clearly, what the target is — and then the job is to make it a reality. There is a radical difference between participation in the discussion (a luxury) and understanding of the decision (an obligation).

We see Portuguese companies that imported the framework without questioning the premise: "OKR means that everyone participates in the definition." No. OKR means that everyone understands what was defined and why. Communication is not synonymous with meetings. An email with context, a dashboard showing the objective, a 10-minute conversation — this is communication. A room with 12 people "co-creating priorities" is consultancy, not management.

Clarity of objectives does not require prior consensus. It requires continuous transparency and individual accountability.

When meetings become the metric of success

Five years ago, we argued that a good OKR implementation required "definition workshops", "vertical and horizontal alignment", "weekly progress reviews". We were wrong. Or rather: we were confusing the consultancy process (which needs meetings to sell hours) with the operational reality (which needs clarity and action).

In a garment factory with 60 employees, the pattern that works is this: the CEO defines three OKRs for the company (volume, quality, deadline) in a 45-minute conversation with the CFO. The production manager translates one of them into three operational KRs (machine efficiency, defect rate, meeting deadlines). The warehouse manager translates another. Done. This takes two hours, three at most, with IT loading the numbers into KORA Productivity or the Qlik Sense dashboard. Then? No weekly "OKR sync" meetings. What there is: the production manager sees the dashboard in real time, knows whether they are on-track or off-track, acts. If they need help, they call the CEO. If the CEO wants to confirm the strategy is working, they ask for the monthly report — they do not schedule a "checkpoint" meeting.

The difference is brutal: zero recurring meetings, maximum operational clarity.

The role of the system: transparency, not deliberation

This is where most OKR processes fail in SMEs. They do not fail in the definition — they fail in continuous visibility. Teams do not see progress. They see quarterly slides. So, to know whether they are on track, they schedule meetings.

An ERP with integrated BI solves this. If your Qlik Sense or your production dashboard shows in real time whether OEE is at 71% or 58%, whether the average delivery lead time has risen by 1.2 days or fallen, whether the defect rate has evened out — then the production manager does not need a meeting to "confirm status". They see it. They act. It is the difference between management by information (transparency, individual accountability, less bureaucracy) and management by report (structure, deliberation, more meetings).

If you need a meeting to know whether an OKR is being met, your visibility system has failed.

Honesty: where we failed

We have implemented OKR projects in which the client ended up with more meetings than they had before. Not because OKR is to blame — because the implementation process was designed to generate consensus. Workshops with 12 people. Priority votes. "Alignment cascade". The mistake was ours: we confused "involvement" with "democratic participation". A CEO who defines OKRs is making decisions. Full stop. Then they communicate. The team executes and reports. If there is misalignment, there is a conversation — not a scheduled meeting.

Industrial SMEs do not have the luxury of prolonged consensus. They have client deadlines. They have an ageing workforce and high turnover — in 2023, the average voluntary turnover in Portugal was 10.6%, with 52% of companies admitting difficulty in retaining talent (Mercer, 2023). They have tight margins. OKR has to be fast, clear, executable. When the team changes every 18 months, there is no time for a "culture of open debate". There is only time for clarity and action.

The pattern that works

This is what we see working in factories and distributors that do not get lost in bureaucracy:

  • Definition: CEO + CFO + CTO define 3-5 OKRs for the company in half an hour, based on market pressures and known capacity. No workshops.
  • Translation: Each department head (production, sales, logistics) has a week to translate an OKR into 2-3 measurable operational KRs. An email with context is enough.
  • Visibility: The KRs go into a single dashboard (ERP + BI). Everyone sees them. Daily, if necessary.
  • Action: If a KR deviates by more than 5%, the person responsible acts — contacting the CEO if they need support. No scheduled meeting.
  • Review: A 20-minute conversation per month between the CEO and department head. Not an "OKR checkpoint" meeting.

This cuts meetings by 70%. It increases clarity by 200%.

The invisible cost of confusion

Do you know what nobody calculates? The cost of an "OKR alignment" meeting that should not exist. If you have 8 people in the room, 1.5 hours, an average employee cost of 25 euros/hour (gross salary + charges), this costs 300 euros. Seventeen of those meetings? 5,100 euros per month. And the OKR still has not started working. Now calculate the cost of the lack of clarity if you had no OKR at all: undetected deviations, delayed corrective actions, demotivated teams because they do not know whether they are on track. This costs more. But it is invisible, so nobody accounts for it. OKR done well is the cheapest option. OKR with bureaucracy is the most expensive.

A question for the next management meeting

How many meetings has your CEO scheduled this month for "alignment", "syncing", "checkpoint", "status update" or "review"? Now, how many of those could be replaced by a dashboard he consulted in the morning, in 3 minutes, from his computer?

If the answer is "more than half", your OKR is not working. It is becoming a tool for managing meetings, not for managing the company. The solution is not to remove OKR. It is to remove the meetings that surround it. Operational transparency does that — when the system shows the real state, in real time, the meeting becomes optional. And when the meeting is optional, it becomes brief.

Frequently asked questions

How many meetings are needed to implement OKR in an industrial SME?

You do not need recurring OKR meetings. The effective pattern is: 45 minutes for the CEO to define the OKRs with the CFO, one week for each department to translate them into operational KRs, and a 20-minute monthly conversation. The rest works through continuous visibility on a dashboard, without weekly "syncs".

What is the difference between participation in defining OKR and understanding of the decision?

Participation is a luxury — meetings with many people "co-creating" priorities. Understanding is an obligation — everyone understanding what was decided and why. Communication can be an email with context, a visible dashboard or a 10-minute conversation. It does not need to be a meeting.

Why does OKR in industrial SMEs not work as it does in technology start-ups?

Technology start-ups have cultures of open debate with teams that think in parallel. Industrial SMEs have client deadlines, tight margins and high turnover. They do not have time for "management democracy". They need quick clarity and immediate action, not prolonged consensus.

What should an OKR dashboard show to avoid unnecessary meetings?

The dashboard should show in real time whether each KR is on-track or off-track. If the production manager sees OEE at 71%, the defect rate and the average delivery lead time, they do not need a meeting to confirm status. They see it, understand the situation and act directly.

What should the monthly OKR review look like in an SME?

A 20-minute conversation between the CEO and department head. Not an "OKR checkpoint" meeting with multiple participants. If a KR deviates by more than 5%, the person responsible contacts the CEO for support, with no need for a scheduled meeting.

What is the most common mistake in implementing OKR in Portuguese companies?

Confusing OKR with management democracy. Many companies imported the framework thinking it means everyone participating in the definition. In reality, OKR means everyone understanding what was defined. This generates unnecessary workshops and more meetings than before.

How is an OKR translated into operational KRs in a factory?

Each department head has a week to translate an OKR into 2-3 measurable KRs. For example, a volume OKR can be translated into three KRs: machine efficiency, defect rate and meeting deadlines. An email with context is enough — no meeting needed.