Designing Beyond the Desk · Longitudinal research · workforce experience
Designing beyond desk-based assumptions.
A multi-year discovery-to-validation program reframed frontline experience around device access, time, privacy, managers, places, and channels.
Public-safe caseNames, values, visual language, and identifying details are reconstructed.
Quick help
What do you need to do?
View a request
Ask for help
Shared device · private mode
Product response Short flow · visible status · safe exit
What conditions make digital help genuinely reachable during the realities of frontline work?
Longitudinal discovery → validation
Access model + experience concepts
Workers outside conventional office settings were often treated as one segment, even though their actual access to devices, time, privacy, managers, and channels varied dramatically.
I co-led foundational research, helped define the multi-phase roadmap, participated in customer and worker sessions, and carried the system model into concept and release discussions.
The work replaced a simple desk versus no-desk label with an access-condition model and used that model to evaluate kiosk, authentication, task, support, and local-configuration decisions.
The research informed product, MVP, authentication, guided-help, and release conversations and remained relevant to later mobile and AI strategy.
Reconstructed access model
The role label was not the useful segmentation.
Select a condition to see why the same job title could produce very different product requirements.
“Deskless worker”
Too broad to explain how someone could access help or complete a task.
Device availability
PersonalSharedManagedNone
Experience responseShort guided pathVisible request statusPrivacy-safe exit
The useful distinction was whether the device was personal, shared, managed, or unavailable, and whether the worker could install or authenticate into the experience.
The job title was less useful than the access conditions.
A worker might have a shared kiosk, a managed device, a personal phone they did not want to use, or no digital access during a shift. Time and privacy could matter as much as the device itself.
Managers became both the path of least resistance and a bottleneck.
When direct self-service did not fit the job, managers raised requests, relayed information, and navigated support on behalf of workers. The opportunity was to support managers without making them permanent gatekeepers.
Adoption problems were often channel and authentication problems.
Passwords, shared devices, limited break time, privacy, plant security, and confusing support pathways explained behavior that could otherwise be misread as lack of interest.
A clear interface still failed when the expected action was missing.
Participants could appreciate the visual design while still being unable to complete important tasks, understand request state, or trust that a submission had gone somewhere useful.
What the work enabled
A more useful model of frontline access.
Reframed the population around access conditions rather than one universal frontline persona.
Connected worker behavior to devices, managers, channels, privacy, and local operational constraints.
Translated discovery into kiosk, task-completion, authentication, and continuity recommendations.
Created a longitudinal evidence base reused in later product and future-work conversations.
Public case boundary
The program has strong discovery and decision relevance. The public case should qualify exact participant metadata and avoid claiming that specific features shipped or improved adoption without verified release evidence.