5 KPIs Every Operations Manager Should Check Every Morning

Imagine starting the day with a simple question: "How are things going?"

If the answer arrives after a round of phone calls, emails, or manually updated spreadsheets, you've already lost an hour. And that question, "how are things going", probably still doesn't have a precise answer.

We've worked with operations managers at Italian SMEs for years. One of the things they tell us most often is this: "I have so much data, but I never really know where to look." The problem isn't a lack of information, it's the absence of clear, filtered signals available at the right moment.

In this article, we share the 5 operational KPIs that, in our experience, change the way a manager starts their day.

Why the Standard Dashboard Isn't Enough

Most of the SMEs we work with already have something: an ERP, a shared spreadsheet, maybe a monthly report. The problem is that these tools are designed to look backwards: they tell you what happened last month, not what's about to go wrong today.

An effective operational dashboard needs to do one thing: let you spot problems before they become emergencies. You don't need a complex system. You need a few indicators, updated in real time, readable in under 15 minutes.

The 5 KPIs We Recommend Monitoring Every Morning

1. Percentage of Tasks Completed on Time

How many tasks planned for today (or this week) were closed by their deadline? This number, expressed as a percentage, is the thermometer of your team's operational capacity.

If the percentage drops below 70% for two or three consecutive days, it's not a problem with individual people: it's a signal that something in the workload, the priorities, or the dependencies between tasks isn't working.

Alert threshold: below 65% for three consecutive days.

2. Growing Backlog (Tasks Open for More Than N Days)

How many tasks have been open for more than a week with no updates? A stagnant backlog is the most underestimated signal in operations: it indicates work that nobody is moving forward, often because it's blocked by something nobody has resolved yet.

The absolute value matters less than the trend: if this number grows every day, there's a systemic problem that needs to be addressed immediately.

Alert threshold: growth above 20% in one week.

3. Bottleneck by Person or Department

Who has the most tasks waiting for feedback, approval, or input? This indicator, often overlooked because it requires cross-functional visibility, identifies where delay is accumulating before it becomes visible.

With clients using Wrike, we build this as a filtered view by assignee sorted by due date. In 30 seconds you can see who is overloaded and who has capacity to support.

Alert threshold: one person with more than double the upcoming tasks compared to the team average.

4. Average Lead Time by Request Type

How much time passes, on average, between a request being opened and closed? Segmented by type (customer support, onboarding, internal development, etc.), this KPI reveals where the process is slow, regardless of who is working on it.

It's the KPI that most often surprises managers: there are types of requests everyone believes are fast, yet they take 3 times longer than expected. Seeing this number systematically allows you to fix the process, not the people.

Alert threshold: lead time more than 50% above the historical average for that request type.

5. Rework Rate (Tasks Reopened or Modified After Closure)

How many tasks are reopened or significantly modified after being declared complete? This is the most direct KPI for process quality: a high rework rate indicates ambiguous deliverables, unclear acceptance criteria, or poorly structured handoffs.

At a manufacturing company we work with, this number was at 28%: almost one in three tasks was put back into rework. After three months of process intervention (not people intervention), it had dropped to 9%.

Alert threshold: above 15%.

How to Build This Dashboard (Without an IT Project)

The good news is that these 5 KPIs don't require a complex BI system or a data warehouse project. If your company already uses a structured project management tool, like Wrike, most of this data is already available, and can be visualised through configurable reports and dashboards without writing a single line of code.

The process we follow with our clients is this: we start from the data already in the system, define the alert thresholds together for that specific context, and build a morning view that the manager can read in under 15 minutes.

If the data is scattered across different tools, such as ERP, email and Excel, the first step is to centralise it. You don't need to do everything at once: just the most critical operational data is enough to start.

A Real Case: 15 Minutes a Day That Change Decisions

A B2B services company we work with, 35 people and 4 business lines, implemented this dashboard 8 months ago. Before, the operations manager started every day with a round of calls to team leads to understand project status. He estimated spending between 45 minutes and an hour every morning just gathering information.

Today he opens the dashboard at 8:30am, reads the 5 indicators, and within 15 minutes has a clear picture. When one of the indicators flags an anomaly, he already knows where to act, and often can do so before the team even notices the problem.

The most significant change, though, wasn't in the time saved: it was in the quality of conversations. Operational meetings became shorter because everyone started from the same data, and decisions were made on numbers, not perceptions.

When These KPIs Aren't Enough

These 5 indicators cover the daily operational dimension: who does what, how fast, with what quality. They're not sufficient if you need financial analysis, demand forecasting, or commercial KPIs. In that case, additional layers are needed, often with dedicated BI tools.

They're also less useful in very small contexts (2-4 people) where visibility is already naturally high, or in sectors with very long operational cycles where daily granularity doesn't add value.

But for most SMEs with teams between 10 and 100 people and continuous operational processes, these 5 KPIs are the most effective starting point we know.

Want to Understand What Data You Already Have?

Before building a dashboard, let's figure out where to start together: what data you already have, where it lives, and what level of visibility is realistic in the short term. Only then do we define the tools.

→ Browse all articles on Business Intelligence