Colour theme
Book a consultation

Testing work tasks on phones and tablets

Test mobile work one task at a time: readable screens, the right data access, weak connections and a clean handoff back to the main business record.

A person using a phone and laptop at a table beside a takeaway coffee.

Mobile work starts with a task someone needs to complete away from a desk. Checking a schedule, updating a job record and editing a long report have different requirements. Moving an application into the cloud doesn’t automatically make those tasks usable on a phone.

Choose one workflow and test it on the phones, tablets and connections staff will use. Keep a desktop fallback for work that doesn’t fit.

Define the task and where the record lives

Write down the input, required action and result. Identify the business system that holds the final record and who can approve changes.

Decide what can be viewed, edited or sent from a mobile device. A notification can alert someone to a task without granting permission to complete every related action.

Use fictional records for the first trial. Include an incomplete request and an error that needs another person’s help.

Test the interface beyond its opening screen

Check the full task at the user’s preferred text size. Include sign-in, search, forms, attachment handling and confirmation. Controls should remain readable and usable without depending on hover.

Test relevant assistive technology and an external keyboard where staff use them. A mobile application may have fewer features than its desktop counterpart, so verify each required step.

Ask staff to identify unnecessary scrolling, repeated entry and places where the result is unclear. Record those issues as acceptance work.

Check access on company and personal devices

Review business-owned and personal devices separately. State what management can see, what information remains local and what happens when access is removed. Canada’s privacy commissioners’ BYOD guidance addresses the privacy responsibilities.

Device management and application protection serve different purposes. For supported apps and configurations, Intune app protection can apply with or without device enrolment. Check platform, licence and policy requirements with IT.

Don’t treat one management model as compulsory for every mobile task. Choose controls according to the information and workflow.

Test a weak or missing connection

Confirm whether the application can work offline and what information it caches. Check a dropped connection during submission and a later reconnect.

Verify that staff can tell whether an update reached the main business system. A retry shouldn’t create duplicate work or overwrite another person’s change without warning.

Review data usage and charging arrangements with staff. If offline copies are required, include their protection and removal in the plan.

Keep notifications and handoffs manageable

Agree on the events staff need to see and the response expected during working hours. Don’t make every alert an instruction to respond immediately.

Test the handoff from a mobile update to the next person. They should find the correct record, status and outstanding action without asking the sender to reconstruct the conversation.

Measure the pilot before expanding

Compare completion, errors and staff effort with the current process. Include recovery from a failed submission and support requests.

Roll out the tasks that pass the agreed checks. Document limitations and revisit them when the application, device policy or business process changes.


Featured Image Credit