

Applications Don’t Fit the Job: Why One Screen Can’t Serve Every Role.
Most SAP screens were designed for someone at a desk. Most of the work happens somewhere else.
A quality inspector on a production line wears gloves. A warehouse operator holds a scanner in one hand and a carton in the other. A technician stands on a ladder. Each of them is asked to use the same screens that were designed for a planner with a keyboard, a mouse and a large monitor.
That is the gap behind SAP for frontline workers. The process in SAP is right. The way people are asked to use it doesn’t fit the job they do. This post closes the first theme of our series on the execution gap. After too many screens and clicks and repetitive manual data entry, we look at the root cause behind both: applications that weren’t built for the role.
The Problem: Built for Every Role, Fit for None.
Standard SAP transactions are designed to serve many roles, many industries and many scenarios. That makes them complete. It also makes them general.
A frontline role needs the opposite. It needs a narrow set of steps, in a fixed order, on a specific device, under specific conditions: noise, gloves, poor light, a moving line, a customer waiting. When the application doesn’t fit those conditions, people don’t stop working. They work around it.
So the screen stays in the office, and the work moves to paper. Or the transaction gets used, but only by the two people who have learned its quirks. Or every site builds its own spreadsheet to fill the gap, and nobody knows which version is right.
A Practical Example: Recording Inspection Results on the Line.
An inspector checks samples from a production run every hour. For each sample, they measure several characteristics, compare them to the specification and record the result.
The SAP process is clear: an inspection lot, characteristics, results, a usage decision. But the screen is built for a desktop. On the line, the inspector can’t type with gloves, can’t read small fields on a handheld and can’t leave the line to walk to a terminal.
So the measurements go on a printed sheet. At the end of the shift, the sheet goes to the quality office, where someone records the results in SAP. If a value was out of tolerance at 10 a.m., the system knows at 6 p.m. By then, eight hours of product may need to be checked again.
Now picture the same inspection in an application built for the role. Large fields and buttons that work with gloves. The next sample and its specification already on screen. Values read straight from the measuring device where possible. A clear red flag the moment a value is out of tolerance, and the right person notified before the next batch starts.
The Impact: Poor Fit Has a Price.
When applications don’t fit the job, the cost shows up across the operation:
- Workarounds become the process. Paper, spreadsheets and personal tools fill the gap. The real process lives outside SAP.
- Problems are found late. Results recorded hours after the fact mean deviations are caught after more product, parts or time are lost.
- Training takes longer. New hires need to learn a general system, not their job. Time to proficiency grows, and so does turnover risk.
- Low adoption, low trust. People who struggle with an application stop using it. Data quality falls, and planners stop trusting what SAP shows.
- AI without a foothold. An AI agent can flag a deviation or suggest the next step only if the result reaches the system when it happens. Fit at the point of work is what gives AI something to act on.
How Neptune Closes the Gap.
The fix is not a new process. It is a Business Application shaped around the role, on the SAP process you already have.
With Neptune, you build role-specific Business Applications that fit the people, the device and the conditions of the job:
- Designed for the role. Each application shows one role its steps, in the order the work happens, with only the information that role needs.
- Designed for the device. Rugged handhelds, tablets, desktops and large shop floor screens, with layouts made for gloves, scanners and one-handed use.
- Online or offline. Work continues without a connection and syncs to SAP when the device is back online.
- Native on SAP. Results go straight into SAP through native SAP integration, with the same specifications, rules and authorizations.
- Start from what works. With Six Proven Use Cases and Naia Build, teams start from applications that already fit common roles, instead of a blank page.
In Production Operations, customers use role-specific applications to work toward higher first-pass yield and throughput. In Health & Safety Inspections, the goal is higher compliance and fewer repeat findings.
The Metrics It Moves.
Applications that fit the job show up first in two of the six outcome areas from the series introduction:
| Outcome area | KPIs to baseline |
|---|---|
| Improve workforce adoption and effectiveness | Application adoption rate · Task success rate · Time to proficiency |
| Improve accuracy and process quality | Transaction error rate · First-time-right rate · Rework rate |
Faster recording also moves operational responsiveness (time from event to action), because a deviation found in minutes is cheaper than one found at the end of the shift.
How to Build the Business Case.
Start with one role, not one transaction.
- Pick the role. Choose a frontline role with high volume and visible workarounds: inspectors, pickers, technicians, operators.
- Watch the work. Spend an hour with them. Note where they leave SAP, what they write down and what device they would actually want in their hand.
- Measure the delay. Time from event (a measurement, a pick, a repair) to the moment it is recorded in SAP. Count the corrections and the rework caused by late or wrong entries.
- Do the math. Time saved per task, multiplied by tasks per day, people and working days. Then add the cost of what late recording lets through: scrap, rework, repeat findings, longer onboarding.
An illustrative example: 30 inspectors each record 25 inspections a day. If an application built for the role saves 90 seconds per inspection, that is almost 19 hours a day, or about 4,100 hours over 220 working days. That is before you count a single batch saved by catching a deviation earlier.bount a single minute of downtime.An illustrative example: a site receives 80 deliveries a day, and each one takes three minutes to type into SAP from paper. That is four hours a day, or about 880 hours over 220 working days, before you count a single correction.
The Question to Ask Your Teams.
Which roles have stopped using SAP in the moment, and what do they use instead?
The answer shows you where the application doesn’t fit the job, and where your execution gap is easiest to see. Next in this series: work that happens away from a desk, and what it takes to bring SAP to the field, the yard and the line.

