Copyright © 2026 Bonfiglioli Consulting. All rights reserved. P.I. 02646871208 Privacy Policy | Cookie Policy | Adjust Preferences
There are problems in a factory that don't explode suddenly. They accumulate. An unexplained delay, a saturation not read in time, a quality deviation that no one links to a specific cause, an incomplete handover. Taken one by one, they seem manageable incidents. When added up, they become the reason why a seemingly controlled production loses speed, reliability, and profit margin.
This is where Daily Management stops being an insider term and becomes a management issue. His true purpose It's not “having a daily meeting,” but preventing anomalies from remaining invisible until they are too costly to ignore. In other words, Daily Management serves to build an organization that sees first, Decide first and correct first.
Many companies think they already have something similar. They have KPIs, reports, dashboards, regular meetings, and competent people. Yet they continue to discover problems late. Not because data is lacking, but because a daily discipline capable of transforming data into action is missing. The point isn't to measure more. The point is to make visible what matters while it's still possible to intervene.
This is why Daily Management is one of the most concrete pillars of any Lean Thinking journey. It is not an extension of reporting. It is not an organizational liturgy. It is the system that connects daily work to operational objectives, makes deviations legible, clarifies responsibilities, and activates countermeasures along a precise cadence.
One of the most common illusions in industrial organizations is.
Daily Management is born precisely to resolve this paradox. It doesn't add information: it organizes it within an operational rhythm. which forces the company to look every day at what could compromise safety, quality, delivery, productivity, and flow. As long as data remains confined to a report, it tells the past. When it enters a daily comparison routine, it becomes a tool to manage the present.
This passage is particularly important in complex production contexts, where different departments work on the same flow but with priorities, constraints, and languages that are not always aligned. Without a daily management system, each function tends to optimize its own part of the process. The result, however, is not a more efficient factory: it is a more fragmented factory.
This is also why Bonfiglioli Consulting, in its approach to Change Management in Operations, Daily Management is a structured system of meetings, visual boards, and routines distributed across multiple organizational levels, designed to quickly identify deviations and initiate corrective actions within the work shift. keyword not a “meeting.” It's a“system”.
To truly understand Daily Management, one must shed a common misconception: it’s not the same as the morning meeting. The meeting is merely one of its most visible manifestations. Daily Management, in reality, is an operational discipline that makes the process visible, structures moments for discussion, and builds a chain of reactions to anomalies.
The daily meeting should be conceived as a brief, typically 15-20 minute stand-up discussion, designed to punctually address the main critical issues that have emerged and share key production and quality KPIs. This detail is important not so much for the duration itself, but for what it implies: Daily Management thrives on synthesis, frequency, and focus. If it's prolonged, it loses effectiveness. If it becomes generic, it stops providing guidance.
But the heart of the system isn't the meeting time. It's the fact that every day there's a place, physical or visual, where the reality of the process is made explicit. What's late? Where are bottlenecks accumulating? Which department is saturated? Which anomaly requires escalation? What needs to be resolved today, and by whom?
From this perspective, Daily Management is much closer to an infrastructure of clarity than an internal communication technique. It serves to prevent critical issues from being scattered across fragmented conversations, emails, phone calls, or personal interpretations. In a good Daily Management system, a problem should not be told ten times to ten different people. It should be seen once, understood quickly, and routed correctly.
When this discipline is lacking, organizations enter a condition that Bonfiglioli Consulting contrasts with that of the agile factory: a context where anomalies arrive late, responsibilities are not always clear, coordination between functions is weak, and management is drawn into continuous micromanagement to compensate for the absence of a system.
The interesting point is that, from the inside, many companies don't immediately perceive this clumsiness. They normalize it. Delays become physiological, permanent urgencies are accepted as part of the job, problems are tackled case by case, and reactivity is mistaken for efficiency. But a factory that always reacts at the last moment isn't agile. It's just trained for emergencies.
Daily Management Break this pattern because Shift the focus from exceptions to routine.. It doesn't ask the organization to be brilliant when the problem has already exploded. It asks for discipline beforehand. The best performances are rarely born from extraordinary gestures. They are born from an ordinary system that makes obvious what's not working every day.
A mature Daily Management system does not operate on a single level. Instead, it functions as a sequence of boards and meetings distributed throughout the organizational structure: from the shift to the department, from the department to management, according to coherent escalation logic. This approach allows every problem to be discussed at the right point, with the appropriate level of detail, and with the truly involved decision-makers.
In a well-designed Executive Flash Meeting, the operational first lines participate, with a combination of fixed attendees and attendees activated based on the topics. The composition is itself a methodological choice: not everyone has to be present all the time, but all critical functions must be able to quickly enter the decision-making circuit when needed.
The agenda is also significant. Production and release trends, delays and their reasons, first-time quality, corrective and preventive actions, capacity and saturation of different departments, product development progress, Gemba Walk results, and Project Management milestones are monitored. This mix clearly shows what distinguishes a useful routine from a generic meeting: We are talking about concrete operational deviations, not abstract updates.
One of the most frequent mistakes in building Daily Management is thinking that everything must be daily. In reality, good daily management distinguishes what requires daily oversight from what makes sense to monitor weekly.
Production and release monitoring is typically daily because it changes rapidly and has an immediate impact on workflow. Other topics, such as quality, capacity, product development, Gemba Walks, or project progress, may follow a weekly cadence. This breakdown is far from trivial. It prevents the meeting from becoming too dense and helps each function prepare data and actions with a precise logic.
The lesson for anyone designing a similar system is clear: Daily Management is not about talking about everything every day. It's about bringing to the surface every day what deserves daily attention, placing the rest within a readable and sustainable rhythm. When this distinction is missing, the opposite of the desired phenomenon occurs: more discussion, but less clarity.
Daily Management thrives on indicators, but not just any indicators. The KPIs that enter the system must have three characteristics: they must be understandable by those involved, relevant to the flow, and linked to a possible decision. If a number cannot guide an action, it has little value within Daily Management.
This is the point where the Visual Management it stops being just a representation technique and becomes an organizational lever. When everyone looks at the same board and reads the same priorities, the system reduces the margin for individual interpretation. And fewer arbitrary interpretations mean less dispersion, fewer excuses, and more accountability.
This is why Daily Management only works when the board isn't a passive bulletin board, but an active alignment tool. It's not there to decorate the process. It's there to make it objectively debatable.
Among the most cited indicators in industrial contexts is OEE, often used as a synthetic measure of implant efficacy. But precisely because it is widely used, it is also widely misunderstood. The article OEE Beyond the Number: How to Turn It into a Daily Improvement System, it clearly shows a key principle: efficiency only truly matters when it becomes a system of continuous improvement. This is where Daily Management shows its true value: an OEE can be good in numbers but poor in effects if it doesn't become a routine that clarifies its causes, losses, and priorities.
There is also another risk: optimizing individual departments without optimizing the system.. This is the classic problem of organizations reading metrics in silos. Three areas can appear efficient individually and still produce a weak overall flow. Daily Management serves precisely to avoid this pitfall by refocusing attention from local data to flow performance.
There is one point on which Daily Management plays out much of its credibility: the relationship with Gemba. If the system remains confined to numbers and meetings, it risks becoming bureaucratic. If, on the other hand, it maintains a constant connection with the place where value is created, it retains its diagnostic capacity.
For Bonfiglioli Consulting, leadership at the Gemba is an integral part of building the agile factory. This means that management should not use daily management as a screen to distance themselves from operational reality. On the contrary, they should use it to get closer, with more method and less improvisation.
A board can flag an anomaly. But only contact with the process truly allows one to understand its nature. This is where Daily Management stops being an exercise in formal alignment and becomes a real governance tool again.
When talking about Daily Management, one of the healthiest questions is also the simplest: Does all of this really produce results or does it just generate more rituals? The best way to respond is to look at real-world cases and understand what problems they solved, what choices they made, and what results they achieved.
In a Lean transformation project for a make-to-order manufacturing company, the path began with three explicit objectives: ensuring delivery times, reducing lead times, and maintaining the expected profit margin. The context was typical of many complex productions: strong pressure on time, quality, and profitability, the need to coordinate multiple functions, and difficulties in aligning technical activities, physical progress, and bottleneck management.
The intervention combined project planning and progression, reorganization of the technical office, continuous and pull flow logic, application of Lean principles to assembly and mechanical processing activities, material servicing, operational flash meetings, Focus Improvement, Lean Design, and document standardization. The key point is the link between these levers: when flow is managed in an integrated way, daily meetings become a coordination tool rather than a ritual in themselves.
The results were significant: a 38% reduction in lead times, a 35% reduction in space requirements, a 12% increase in productivity, greater delivery reliability, and protection of expected profit margins. The methodological point, however, is even more interesting than the data. These results do not stem from a single practice. They emerge when daily management is integrated with operational rules, anomaly visibility, interfunctional coordination, and improvement discipline.
This is perhaps the most useful lesson from the case: the Daily Management It's not worth it because it adds control. It's worth it because Create continuity between goals, problems, and actions. And it is this continuity that allows improvement to become a system, not an episode.
Not all boards lead to improvement. Not all flash meetings create clarity. Not all daily routines become operational advantages. Daily Management truly works only when it meets certain precise conditions.
The first is the real visibility of the problem. If the data is incomplete, late, or unreliable, daily comparison becomes meaningless. The second is the clarity of responsibilities. If the system highlights anomalies but doesn't assign who should intervene, the problem just becomes more visible. The third is the Attendance policy. If the rhythm breaks, the organization quickly reverts to chasing emergencies instead of managing them.
There is then a fourth condition, often underestimated: the Daily Management must be sustainable. It cannot depend on the exceptional energy of a few people. It must be built so that the team can maintain it over time. This is also why Bonfiglioli Consulting connects these systems to auditing practices, standardization, and controlling adherence to standards.
It would be a mistake to think that Daily Management is only useful on the shop floor. The logic behind it is much broader: to create visibility, synchronize priorities, make deviations clear, clarify responsibilities, and activate escalations. These are needs that also exist in technical offices, project management, product development, and transactional processes.
Project management clearly demonstrates a key principle: Daily Management truly works when it is built upon planning, flow, standards, and daily coordination.
Those who want to introduce or strengthen Daily Management in their company often make an initial mistake: they start from the board instead of the problem. In reality, the correct starting point is different. It is first necessary to understand which deviations truly compromise performance, which decisions need to be made more quickly, and which organizational interfaces today generate delays or ambiguities.
It only makes sense to design the system afterward: what KPIs to show, with what frequency, on which board, with which participants, according to which escalation rules. If you reverse the sequence, the risk is building a nice container that no one uses to make better decisions. And at that point, Daily Management is perceived as just another practice imposed from above.
The rule to remember is simple: a board is useless if it doesn't change behavior. A meeting is useless if it doesn't accelerate a decision. An indicator is useless if it doesn't make it clearer where to intervene today. Daily Management is only useful when each of these elements produces operational consequences.
In recent years, operational complexity has increased almost everywhere: unstable supply chains, more complex product portfolios, greater pressure on service, flexibility, and response times. In this context, continuing to manage anomalies as occasional events is no longer enough. Systems are needed that increase the speed of interpreting reality, not just the capacity for downstream reaction.
This is where Daily Management proves its relevance. Not because it's new. But why is it one of the few disciplines that allows for the integration of visibility, coordination, prioritization, and problem-solving in an operational way?. In an era full of data but poor in attention, its value lies precisely in building organized attention.
Daily Management is not a bulletin board. It's not a meeting. And it's not even an accessory technique to activate when you want to “do a little Lean.’ It is a managerial discipline that makes goals, problems, and responsibilities visible at the exact moment action is needed.
When integrated into a coherent system of visibility, escalation, process control, and continuous improvement, the results become tangible: fewer delays, less waste, greater operational reliability, and an enhanced ability to make decisions sooner. And that, ultimately, is the point: not just to make the morning meeting better, but to build an organization that doesn't wait until the final problem arises to realize something has already gone wrong.
If you want to make daily management more effective, the first step isn't to increase meetings: it's to design a system that makes problems visible and acts on their causes. This is the heart of Daily Management, and the starting point for building a truly agile factory.
Copyright © 2026 Bonfiglioli Consulting. All rights reserved. P.I. 02646871208 Privacy Policy | Cookie Policy | Adjust Preferences