


Designing for Work That Happens Elsewhere
Rebuilding the mobile task experience for distributed property operations.

Designing for Work That Happens Elsewhere
Rebuilding the mobile task experience for distributed property operations.
01 — The Reality of Field Operations
In property management, the most important work happens far away from the people responsible for it.
Managers often oversee multiple properties across different cities while relying on contractors or distributed staff to perform work on site.
Before a property can be marked ready for guests, operators must complete detailed operational inspections covering cleanliness, maintenance, and safety.
These inspections can be extensive. A single property checklist may include 80–100 individual requirements, often involving:
- Photo documentation
- Status confirmations
- Notes and follow-ups
But when the work happens in the field and the oversight happens remotely, a checklist alone isn't enough.
QuoteManagers don't just need tasks completed. They need to trust that the work actually happened.
02 — The Original System
Our mobile experience was originally a wrapped web application.
While this allowed us to launch quickly, it struggled to support the realities of field work.
Beyond performance issues, two deeper operational problems emerged.
Managers couldn't reliably verify work
Because managers were rarely on site, they relied on task documentation to understand what had happened.
But documentation was inconsistent. Photos were often missing, poorly organized, or difficult to review.
The system recorded task completion, but it didn't always provide confidence in the outcome.
Operators lacked the context needed to complete tasks
Field operators frequently needed additional information to perform their work correctly:
- What the finished result should look like
- Property-specific instructions
- Manuals or guidelines
- Reservation details tied to the task
This information often lived outside the task itself, forcing users to switch between tools or contact managers for clarification.
03 — Why Tasks Needed to Be Granular
At first glance, property operations might seem like they could be managed with simple checklist items:
- Clean the bathroom
- Prepare the bedroom
- Restock supplies
In reality, tasks needed to be far more detailed.
Because managers were often not physically present, tasks needed to capture specific operational data and documentation. This allowed them to understand what actually happened at the property without visiting it themselves.
A task like "clean the bathroom" might include multiple requirements such as:
Count missing supplies
How many toilet paper rolls are missing?
Confirm completion visually
Upload a photo of the cleaned bathroom
Verify specific conditions
Is the mirror clean? Is the trash emptied?
Report issues
Are any fixtures damaged?
These granular steps served two purposes.
Standardizing work across distributed teams
Many properties relied on different contractors or rotating staff. Breaking tasks into clear requirements ensured the same operational standards were applied regardless of who completed the work.
Creating a reliable audit trail
Granular inputs — counts, confirmations, and photos — created a detailed operational record managers could review remotely.
Instead of simply seeing that a task was marked complete, they could understand:
- What was done
- What supplies were missing
- Whether the property met readiness standards
QuoteThis level of detail transformed the system from a simple checklist into a trusted operational record.
04 — My Role
I worked across research, design, and implementation to rethink the mobile experience.
This included:
- Conducting interviews with property operators and managers
- Testing workflows directly in the field
- Mapping the task completion process
- Designing simplified interaction patterns
- Collaborating with engineering to transition the mobile experience from a wrapped web app to a fully native mobile application
The redesigned mobile experience was developed and launched within a few months.
05 — A Shift in Perspective
Rather than treating the app as a checklist tool, we reframed the problem:
QuoteThe system needed to become a reliable operational record of what happened on site.
This reframing focused the redesign around two goals:
Enable remote auditing and verification
Bring operational context directly into the task workflow
06 — Enabling Remote Auditing
Managers overseeing multiple properties needed to confidently verify work without being physically present.
To support this, we redesigned how documentation was captured and reviewed within the task system.
Structured Photo Documentation
Tasks were redesigned to encourage consistent photo capture tied to specific checklist items.
Operators could quickly attach images directly to the requirement being verified, creating a clear visual record of each step in the inspection.
This made reviews easier and helped ensure documentation was complete.
AI-Assisted Photo Review
To help managers audit work at scale, we introduced AI-assisted photo verification.
Managers could define prompts describing what a valid photo should show. For example:
- A properly cleaned kitchen surface
- Required equipment present in a room
- A correctly staged bedroom
When operators uploaded images, the system evaluated the photo against the prompt and provided feedback.
This helped surface potential issues earlier and reduced the time managers spent manually reviewing inspections.
Communication Within Tasks
Operational work often requires clarification.
To keep communication tied to the work itself, we introduced comment threads within task sections.
Users could:
- Leave notes
- Ask questions
- Tag other team members
This created a shared record of discussion directly attached to the task, improving coordination between field operators and managers.
07 — Bringing Context Into the Workflow
Completing operational tasks correctly often depends on having the right information at the right moment.
To support this, we redesigned tasks to include all relevant context directly within the workflow.
Operators could access:
- Reference photos showing the expected result
- Instruction manuals or guidelines
- Property-specific details
- Reservation information connected to the task
Keeping this information embedded within the task interface reduced confusion and allowed operators to complete work without switching tools.
08 — Moving to a Native Mobile Experience
Delivering these improvements required moving beyond the limitations of the wrapped web application.
We rebuilt the product as a fully native mobile app, which allowed us to:
- Improve performance on lower-end devices
- Integrate camera functionality more seamlessly
- Design faster interaction patterns for repetitive task completion
The result was a significantly more reliable experience for operators working in the field.
09 — Impact
The redesigned mobile experience improved both task execution and operational visibility.
Operators could move through large inspections more efficiently and with greater clarity, while managers gained a more reliable understanding of property readiness.
- More consistent photo documentation for audits
- Faster resolution of issues through task-level communication
- Reduced confusion when completing complex checklists
- Greater visibility for managers overseeing distributed teams
The system evolved from a simple checklist into a shared operational record between field teams and remote managers.
10 — Reflection
This project reshaped how I think about operational software.
When work happens in the physical world but oversight happens remotely, software must do more than track tasks.
QuoteIt must capture reality in a way that others can trust.
Designing for that level of trust requires thinking beyond interfaces and focusing on how software supports the entire system of work.
Next Case Study
Dugout Studio
View Project →
