What Production Progress Software Should Show to Different Roles

Manufacturing companies evaluating production software often assume that one dashboard, showing the same raw data to everyone, will keep the whole operation informed. But the reality of a shop floor is more subtle. An operator, a production manager, and a purchasing customer all look at the same production job, yet each needs a different view. If they all see the same raw dashboard, the result is confusion, wasted time, and even strained customer relationships. This article explains why production progress software must tailor its displays to different roles, and what each role should actually see.

What Actually Happens: Why a Single Dashboard Fails

When a company first implements production progress software, the simplest approach seems to be a single dashboard that everyone can access. The dashboard shows every job, every workstation, every status update, and every exception. It appears democratic: all information is available to all. But in practice, this approach creates problems.

Operators are flooded with data about jobs they are not working on. Managers have to sift through raw logs to find the exceptions that need their attention. Customers, if given access, see internal notes about machine breakdowns or quality issues that they may misinterpret. The result is that the software becomes a source of noise rather than clarity.

The core issue is that different roles have different responsibilities and different questions. An operator asks, 'What do I do next on this specific job?' A production manager asks, 'Which jobs are behind schedule and why?' A customer asks, 'When will my order ship?' One dashboard cannot answer all three questions well.

Production progress software, therefore, must be role-aware. It should present the same underlying data in different forms, filtered and summarized according to what each person needs to make decisions. This is not about hiding information; it is about presenting the right information at the right level of detail.

The Operator's View: Task-Level Detail

Operators are the people who physically complete the work on the shop floor. Their primary need is to know what to do next on the job they are currently assigned to. They need specific instructions: which operation to perform, which workstation to use, what quantity to produce, and any quality checks that are required.

Production progress software should show the operator a clear list of tasks or operations for their current job, with the current status of each step. It should allow them to update progress when they start and complete an operation, and to flag exceptions such as a machine problem or a missing material. This is the level of detail that helps them do their work efficiently.

What the operator does not need is a company-wide view of every other job. They do not need to see the progress of jobs on other lines or the overall delivery performance to customers. That information is not actionable for them and only adds cognitive load.

A good operator view is simple: a queue of jobs assigned to them, the current operation, and a clear way to record progress. The software should make it easy to update status without interrupting the workflow. For example, a touchscreen at the workstation that shows the current job and allows one-tap updates is more practical than a desktop dashboard that requires navigation.

This operator-centric view is a fundamental part of production progress tracking. As explained in the info100.cc article on production progress tracking, the software covers production stages, shop floor updates, jobs, nodes of work, current status, completed work, and exceptions. For the operator, the relevant part is the immediate job and its current operation.

The Production Manager's View: Aggregated Status and Exceptions

Production managers are responsible for the overall flow of work through the factory. They need to know which jobs are on schedule, which are at risk, and where bottlenecks are forming. They also need to coordinate resources—people, machines, materials—to keep production moving.

For a manager, the software should show an aggregated view of all active jobs, with status indicators such as 'on track', 'at risk', or 'behind'. It should highlight exceptions: a workstation that has stopped, a quality issue that needs a decision, or a material shortage. The manager can then drill down into specific jobs to understand the cause of a delay.

Managers do not need to see every individual update that an operator makes. They need the summary and the alerts. A dashboard that shows a live feed of every status change is as useless as no feed at all, because the signal is lost in the noise.

The software should also allow the manager to see the workload of each workstation or operator, so they can balance resources. For example, if one workstation is overloaded and another is idle, the manager can move work or reassign people. This type of decision support is what makes the software valuable to management.

A manufacturing execution system (MES) often provides this kind of tracking and documentation, as described in the Wikipedia article on manufacturing execution systems. The software tracks production progress, stages, and status, and is used on the shop floor. For a manager, the MES is a control tower that gives a real-time picture of the factory.

The Customer's View: High-Level Progress Without Internal Details

Purchasing customers want to know one thing: when will my order be delivered, and is it on track? They do not need to know the internal details of how the job is progressing through each workstation. They do not need to see the names of your machines, the details of your quality issues, or the internal notes about operator performance.

Customer-facing progress updates should be high-level and positive. They might show a percentage complete, the current stage of production (e.g., 'in machining', 'in assembly', 'in quality control'), and an estimated completion date. If there is a delay, the customer should be informed through a controlled message, not by seeing a raw exception log that might be alarming or confusing.

Sharing too much internal information with customers can create problems. For example, if a customer sees that a machine broke down, they might assume the order will be late, even if the delay is only a few hours and will be recovered. They might also gain insight into your production capacity and efficiency, which could affect their negotiating position.

Therefore, production progress software should have a separate customer view that is carefully designed. It should only show information that is safe and appropriate to share. The software should also allow the company to control when updates are sent to customers, rather than allowing customers to see real-time internal data that may not be polished.

This is a key principle: transparency is not the same as showing everything. Transparency means being honest and open about the information that matters to the customer, without exposing internal operations that are not relevant.

Concrete Example: The Same Job, Three Different Views

Consider a job to produce a batch of machined parts for a customer. The job has been released to the shop floor and is currently at the third of five operations: milling, drilling, heat treatment, grinding, and final inspection. The milling operation is complete, drilling is in progress, and there has been a minor issue with a drill bit that caused a short delay.

The operator at the drilling workstation sees a screen that shows the job, the current operation (drilling), the quantity completed (for example, 40 of 100 parts), and a button to report a problem if needed. The operator has already reported the drill bit issue, and the software has recorded it as an exception. The operator does not see any information about other jobs or the overall schedule.

The production manager sees a dashboard that shows all active jobs. This particular job appears with a yellow indicator, meaning 'at risk' because of the drill bit delay. The manager can click on the job to see the exception and decide whether to assign a new drill bit or adjust the schedule. The manager also sees that the heat treatment workstation is idle, so they might consider moving the job forward if possible.

The purchasing customer, if they have access to a customer portal, sees a simple progress bar showing that the job is 40% complete (based on the operations completed) and an estimated delivery date that is still on schedule. They do not see the drill bit issue, the workstation status, or the internal notes. They only see that the order is progressing as planned.

This example illustrates how the same underlying data can be presented in three different ways, each tailored to the needs of the role. The operator gets the detail to act, the manager gets the summary to decide, and the customer gets the reassurance to trust.

Common Misunderstanding: Transparency Means Showing Everything

A common mistake is to assume that if you are not showing every piece of data to every person, you are being secretive or dishonest. This is especially true when it comes to customer communication. Some companies worry that if they do not give customers real-time access to the shop floor, the customers will think they are hiding problems.

But in reality, transparency is about honest and clear communication of the information that is relevant to the other party. For customers, that means reliable delivery dates and proactive notification of delays. It does not mean exposing every internal hiccup that may not affect the final delivery date.

Similarly, within the company, a manager does not need to see every keystroke of an operator's data entry. The manager needs to see exceptions and trends. An operator does not need to see the profitability of a job or the labor efficiency of their colleagues. That information is not relevant to their task and could create unnecessary distractions.

The role-based view is not about hiding information; it is about providing the right information to the right people at the right time. This is a fundamental design principle for any good production progress software.

Practical Takeaway: How to Evaluate Production Software for Role-Based Views

When you are evaluating production progress software for your company, you should specifically ask how the software handles different user roles. Do not assume that a single dashboard will work for everyone.

First, check if the software allows you to define different user roles and permissions. Can you create a view for operators that only shows their assigned tasks? Can you create a view for managers that shows aggregated status and exceptions? Can you create a customer view that shows only high-level progress?

Second, look at how the software handles exceptions. Does it notify the right people when something goes wrong? Does it allow operators to flag issues easily? Does it give managers the tools to respond to exceptions?

Third, consider the customer communication features. Can you send automated progress updates to customers without giving them access to your internal system? Can you control the level of detail they see?

Finally, think about the user experience. The operator view should be simple and fast to use on the shop floor, possibly on a mobile device or a dedicated terminal. The manager view should be easy to scan and drill down. The customer view should be clean and reassuring.

A software that tries to be everything to everyone will likely fail. A software that respects the different needs of different roles will succeed in improving communication and trust.

One example of a production progress software that is designed with these principles in mind is [Manager Mike](https://info100.cc/mmike), a product by info100.cc that is currently in active development. Manager Mike records progress once, verifies it, and shares it deliberately, from machine shop jobs to workstations and customer updates. It aims to provide the right view to the right role.

When you evaluate software, ask for a demonstration of how each role would see the same job. If the vendor cannot show you distinct views for operators, managers, and customers, that is a red flag. The software may not be truly role-aware.

In summary, production progress software should not be a single raw dashboard for all. It should be a tool that respects the different information needs of different roles, enabling each person to do their job effectively.

Related product: Manager Mike

Manager Mike is production progress software for manufacturing that records progress once, verifies it, and shares it deliberately. It is designed to give operators, managers, and customers the appropriate view of production progress. Manager Mike is an info100.cc product currently in active development. To learn more, visit [Manager Mike](https://info100.cc/mmike) or contact the team at [https://info100.cc/contact](https://info100.cc/contact).

Concrete example

Same job, three views: A production job at the drilling operation: the operator sees the task and quantity, the manager sees a risk indicator and exception, and the customer sees a progress bar and delivery estimate.

Common misconception

Mistake: Transparency means showing all internal data to everyone, including customers.

Better view: Transparency is about honest, relevant communication. Customers need reliable delivery dates, not internal operational details. Managers need aggregated status and exceptions, not every operator update.

Practical takeaways

• Evaluate software by asking how it handles different roles: operator, manager, and customer.
• Ensure the operator view is task-focused and easy to update on the shop floor.
• Ensure the manager view shows aggregated status and exceptions, with drill-down capability.
• Ensure the customer view shows only high-level progress and controlled updates.
• Ask for a demonstration of role-based views during software evaluation.

Related product

Manager Mike — Production progress you can trust.

By Manager Mike team

Explore Manager Mike · Discuss your production workflow