Mobile workflow design

Mobile should support scanning, confirmation, exception capture, and quick approvals where the work happens. It is strongest when it reduces the distance between the operator and the real event rather than trying to reproduce every desktop control on a smaller screen.

Use the section on Design for the moment of work as the decision frame. The learner should explain when it matters, who owns the decision, what state they would inspect first, and how that state supports the lesson objective: identify which tasks belong naturally on mobile.

Evidence should come from task context, scan or confirmation event, handoff state, sync status, offline queue, retry result, or user-facing guidance. For Design for the moment of work, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

The smaller screen should present the next action, the minimum critical context, and unambiguous feedback. Mobile workflow quality improves when users are not asked to navigate across broad menus or interpret dense layouts while standing in operational environments.

Turn the section on Keep decision load low into a realistic example. Ask the learner to describe the situation they are responding to, the first surface they would open, the cue they expect to find, and what they would do if that cue is missing.

For Keep decision load low, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Run the lesson as a field-task walkthrough. Start with the practical task: identify which tasks belong naturally on mobile. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from task context, scan or confirmation event, handoff state, sync status, offline queue, retry result, or user-facing guidance. The practice should end with the learner connecting the action back to the lesson summary: teach teams to design mobile ERP work around short tasks, role context, and environmental constraints instead of shrinking desktop flows.

Close the exercise by asking the learner to restate the objective in operational terms: identify which tasks belong naturally on mobile. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not shrink desktop workflows onto mobile without deciding what the field user actually needs in the moment. Mobile guidance should keep decision load low and status clear. In this lesson, watch for that risk while learners work on this objective: identify which tasks belong naturally on mobile.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain why desktop screens should not simply be copied to mobile and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain why desktop screens should not simply be copied to mobile, keep the lesson in practice mode before marking it complete.