AMH · Field research · Greensboro · 2024
The short story · 4 minI followed a property Turn beyond the interface.
A Turn prepares a rental home for its next tenant: inspection, repairs and a final check that it is ready. Technicians do the work in the field; Field Managers coordinate people, progress and costs.
Across four days, I studied where AMH’s tools supported that process—and where people had to fill the gaps.
See what the fieldwork changed
01 / The central discovery
I observed technicians in vacant properties and Field Managers in the back office. The broad journey held up, but it underrepresented parts runs, lockbox work, additional systems and poor connectivity. These were requirements to investigate, not exceptions to ignore.
Inspect the journey
Why this mattered
Designing only for the original model would leave recurring parts of the technician’s day outside the product conversation.
02 / From observation to direction
I separated the findings by the kind of response they needed. That kept a specific interface issue distinct from a workflow gap or an unresolved system dependency.
The preferred visit time was on the Work Order, but hidden behind hover during scheduling.
Surface the preferred day and time at the point of action. Carried forward for later design.
Parts runs, lockbox tasks and self-performed Work Orders expanded the technician journey.
Use the fuller journey to explore task requirements and support for poor connectivity.
Inspection detail and vendor updates did not travel consistently across the operational tools.
Investigate inspection-data continuity, vendor visibility and the Field Manager workflow.
The end-to-end map connected field inspection, downstream information gaps and coordination outside the core tools. It identified questions for product, technical and operational investigation.
Inspect lifecycle map ↗
03 / The outcome
The handoff connected observations to recommendations—and distinguished what was ready to act on from what still needed learning.
My contribution was the field-informed journey, lifecycle map and prioritised direction. Implementation and its impact were still to be established.
Scope of the evidence: two technicians and two Field Managers in Greensboro. The findings gave the next team a direction to test, not proof that every market had the same needs. No implementation impact is claimed.
The next conversation
In an interview, I can take you through the reasoning behind the handoff:
The working assumptions and the observations that expanded the journey.
Why similar friction led to different recommendations.
Prioritisation, sample limits and the questions left for the next phase.