Field service and mobile adoption

Before any design, the cost of the current state, named in numbers a field crew already knows are true.

1. VideoFive to six systems every morning, before a single job startsPreview6 min
2. VideoAssets leaving site with no removal tracking7 min
3. ReadingThirty-plus hours to convert one hand-drawn map, every time it changed6 min
4. Video82 percent of orders not fully estimated, and what that costs downstream7 min
5. VideoWhat field staff actually open first, and why it was never the plan6 min
6. LabLab: time a field technician’s real morning across five systems6 min

A mobile screen is not a desktop screen made smaller. It is a different design problem with its own rules.

1. VideoOne hand, one thumb, and a signal that drops mid-task7 min
2. VideoOffline-first: what has to work with nothing coming back6 min
3. ReadingScreen density on a phone, and the table that should have been a list7 min
4. VideoBig targets, short forms, and the field that autofills from the record6 min
5. LabLab: redesign a desktop screen for one thumb7 min
6. VideoTesting a mobile screen in actual sunlight, not on a monitor6 min

A desktop table component that silently does not render in the mobile app at all, and the mobile-safe flow built to replace it.

1. VideoThe desktop table component that does not render in the mobile app at allThe table component the desktop hours flow relied on simply does not render inside the mobile app. Nothing errors. It is just absent.6 min
2. VideoFinding out from a support ticket, not from a release note7 min
3. ReadingWhich Lightning components are mobile-safe, and how to check before you build6 min
4. VideoBuilding a mobile-safe hours flow to replace the table that would not load7 min
5. LabLab: rebuild one desktop screen as a mobile-safe flow6 min
6. VideoVerifying the replacement on an actual phone, signed in as a field user7 min

Equipment does not stop leaving a site because someone asks nicely. It stops when leaving without a record is harder than scanning.

1. VideoAn asset leaving site with no record, until it is missing6 min
2. VideoA removal scan that takes less time than not scanning6 min
3. ReadingWho is accountable for an asset between two sites, and how that is recorded7 min
4. VideoReconciling what left against what came back, on a schedule6 min
5. LabLab: build an asset check-out and check-in flow7 min
6. VideoThe untracked assets number, six months later: what changed and what did not6 min

Seventeen field users, one symptom-to-cause matrix, and a finding that redirected the whole triage: the mobile app itself was never the problem.

1. VideoA symptom-to-cause matrix for seventeen field users7 min
2. VideoMobile app logins never failed in thirty days: the finding that redirected the triageEvery login failure in thirty days traced back to the browser login page. The mobile app itself had a perfect record the whole time.6 min
3. ReadingEvery failure was at the browser login page, not the app6 min
4. VideoThe top ticket’s real cause: a passkey registered on a different device7 min
5. LabLab: build a symptom-to-cause matrix from login history and setup audit trail6 min
6. VideoReading verification history without assuming the obvious cause7 min

A phone is not a laptop. A security policy written for one and applied to the other produces incidents that look like malice and are not.

1. VideoThreat detection freezing a user minutes after a login from a VPN address7 min
2. VideoWhy a 90-day password expiry means a forced re-login chosen on a laptop6 min
3. ReadingSetting password expiry to never for one profile, and defending it in writing7 min
4. VideoSession settings for a phone: length, IP ranges, and what breaks a field day6 min
5. LabLab: set and defend a mobile-appropriate session and password policy7 min
6. VideoThe security reviewer’s question, and the answer that is not just because it is easier6 min

Training captured as the person who actually does the job, and adoption measured by what people stopped doing rather than by counting logins.

1. VideoIn-org training served from a static resource, not a slide deck nobody opens7 min
2. VideoCaptured by logging in as an actual field user, not mocked up as an administrator6 min
3. ReadingMeasuring adoption by what people stopped doing, not by counting logins7 min
4. LabLab: record an in-org training walkthrough as the actual field userThe capstone lab. Build one in-org training resource, captured under the field user’s own permissions rather than an admin’s.28 min
5. VideoThe rollout week: what breaks first, and who hears about it6 min
6. QuizCheck: field service and mobile adoption14 min