What is daily management and how does it work in production?

Many factories invest in measurement systems, dashboards, and reports, but lack the daily management where the data is actually used.

The result is that problems are discovered in the monthly report, long after they have cost money. This guide covers how daily management works, what is required for the meetings to create value, and how an OEE system becomes the driving force in the work.

Why is daily management needed?

Daily management is needed so that production problems do not grow over time. A stoppage that is handled on the same day costs an hour. The same stoppage recurring silently for three weeks costs several days of capacity. The daily rhythm shortens the time from deviation to action, and it is this time that determines how much a problem will cost.

There is also a cultural dimension. When the team sees the same facts every morning, a common picture of the situation is created. Discussions about whose fault something was are replaced by discussions about what the data shows and what needs to be done. Experience from 300+ factories shows that this shift, from opinions to facts, is often the single biggest change when an OEE system is introduced.

Without daily management, even the best measurement system becomes a report generator. The numbers exist, but no one acts on them in time. With daily management, the same numbers become a decision-making tool used daily.

What does a good daily management meeting look like?

A good daily management meeting is short, standing, visual, and action-oriented. Most successful teams keep it to 10 to 15 minutes at a screen or a board with the same agenda every day.

A proven agenda looks like this:

Yesterday's results against goals. OEE, volume produced, quality results. Not as a long walkthrough, but as a quick review. Green or red against the goal.

Deviations and stoppages. What stoppages occurred on the machines that did not reach their goals, what causes were coded, and which deviations require action? Here, the loss analysis in the OEE system does the work, as the stoppage causes are already coded automatically or by the operators.

Today's plan and risks. Which orders are to be run? What changeovers are to be made? Where are the risks? Staffing levels and material availability are checked.

Actions and responsibilities. Every deviation that requires action gets an owner and a deadline for action. Without this point, the meeting becomes an information session instead of a management tool.

The important thing is not the exact design of the agenda, but that it is the same every day, that the meeting is based on facts, and that actions are followed up the next day.

At Mixum in Motala, which manufactures ready-to-eat food within the Greenfood Group, digital checklists and shared data replaced the previous paper lists. The digital checklists both simplified the work itself and ensured execution, and also made follow-up much simpler. The team got a shared picture to work from every day, which resulted in production increasing by 12%.

What role does the OEE system play in daily management?

The OEE system is the source of facts that makes the meeting fast and objective. Without the system, meeting time is spent reconstructing what happened yesterday. With the system, the answer is already on the screen when the meeting starts.

Four features make the biggest difference in practice.

Dashboards tailored for the meeting. Yesterday's OEE, stoppage causes, quality results, and today's plan in the same view. Different meetings need different views: the team's morning meeting needs details per production process, while management's weekly meeting needs an overview and trends.

The timeline. A visual representation of the past 24 hours, where stoppages, volume produced, and OEE are visible in the same view. When someone asks what happened around two o'clock last night, the answer is there, with the reason code and comment from the operator who was on site.

Coded stoppage causes. Since operators code the stoppages as they occur, no one has to guess afterwards. At Orkla Nidar, a candy manufacturer in Norway, the "Other" category disappeared from reporting when operators were given tools to directly code the correct cause. It is this data quality that makes the daily meeting meaningful.

Andon and notifications. Deviations requiring immediate action should not wait until the next morning meeting. Notifications to maintenance, quality, or production management ensure that urgent problems are handled immediately, and the morning meeting can focus on patterns and priorities.

How does daily management connect to continuous improvements?

Daily management is the fast loop, and continuous improvements is the slow loop; they need each other. Daily management captures deviations and handles urgent problems. But some problems recur, and they should not be solved over and over again. They need to enter the improvement work, undergo a root cause analysis, and receive a permanent solution.

A concrete example of the connection: if the morning meeting sees the same stoppage cause on the same line three days in a row, it is a signal that the problem is systematic. It is then raised from daily management to the improvement work, where it is analyzed in detail. Once the action is implemented, daily management shows if it has worked, as the stoppage cause should have disappeared from the statistics.

At Sibbhultsverken, a supplier to the automotive industry, the team worked systematically in this way for a year. Technical stoppages decreased by 73%, unplanned stoppages by 63%, and OEE increased by 19.4% in one cell and 40% in another. The results did not come from a single effort, but from the rhythm: daily follow-up, weekly prioritization, and actions followed all the way through.

What are the most common mistakes in daily management?

The most common mistakes are that the meeting becomes too long, that it lacks facts, that actions do not get owners, and that management does not participate. All four can be avoided.

The meeting lasts an hour. Then people stop attending. Keep it to fifteen minutes. Deep analyses belong in the improvement meeting, not the morning meeting.

The meeting is based on memories. Without an OEE system as a source of facts, the meeting becomes a discussion about what different people think or believe. Visualized information should be on the screen when the meeting starts.

Actions without owners. A deviation that everyone sees but no one owns is often left unresolved and creates more frustration. Every action gets a name and a date.

Management is never seen. Daily management on the floor works best when it is connected to a chain of meetings upwards, where deviations from the line can be escalated the same day. When management requests the same facts that the floor works with, the structure holds up over time.

How does Good Solutions work with daily management?

The platform from Good Solutions is built to be a source of facts in daily management, from the operator's screen to management's weekly meeting. Dashboards are easily customized by the customer themselves according to the forum and displayed on screens in the factory, in morning meetings, and in management meetings. The timeline provides a visual picture of the day, with stoppages, volume, and OEE in the same view. The operator tool ensures that stoppage causes are coded in the moment, so that the morning meeting is based on correct data. Andon and team chat handle urgent issues, so that meetings can focus on patterns.

Operational implementation ensures that working methods are established, not just the technology. A dedicated Customer Success Manager helps the customer over time. Training sessions and workshops ensure the right skills to succeed in the improvement work.

Today, the platform supports 300+ factories, and the pattern is the same everywhere: results come when the data is used in a daily rhythm, not when it is compiled in monthly reports.

FAQ

How long should a daily management meeting be?
10 to 15 minutes is enough for most teams. The meeting is a review and a prioritization, not an analysis. Recurring problems are escalated to the improvement meeting where there is time for root cause analysis.

Who should participate in daily management?
At the line level: operators, production supervisors, and ideally a representative from maintenance. At the factory level: production managers, maintenance management, quality, and planning. The chain of meetings allows deviations to be escalated from the floor to management on the same day.

What data do we need before the meeting?
Yesterday's production results against goals (did we win or lose, green or red), stoppage causes, quality results, and today's plan. The data should come from the system, not from memory. If the meeting spends time reconstructing yesterday, proper tool support is missing.

Can we run daily management without an OEE system?
Yes, with a board and manual notes, it is better than no daily management at all. However, manual data often becomes incomplete and difficult to discuss. An OEE system provides the meeting with a shared, reliable fact base and saves the time it takes to gather the material.

How do we make the meeting survive after the first few months?
By ensuring it creates value every day. Actions must be followed up, recurring problems must disappear from the statistics, and management must request the same facts that the meeting works with. When participants see that deviations are actually resolved, the meeting sustains itself.