When decisions are made in the field, tools need to keep up

Government inspectors often work in complex, unpredictable environments — moving between locations, managing tight schedules, and documenting critical information in real time. Their tools must support accuracy, efficiency, and safety — often under pressure and without ideal conditions.


Field Portal was designed to help inspectors plan routes, manage inspections, and capture data in the field without friction. This project required designing not just an interface, but a reliable system that works where connectivity, time, and attention are limited.

At A Glance

Role: Product Designer (UX, Front-End Collaboration)

Partners: Engineering, Product, Field Operations

Timeline: End-to-end product build

Platform: Mobile-first (Android)

Focus: Field workflows, routing, scheduling, real-time data capture


System Scope & Scale

  • AI-generated visual narratives used across K–5 literacy experiences

  • Reusable character and environment system supporting hundreds of story variations

  • Designed for multi-year reuse across grade bands and international markets

The Real Challenge

Designing for the field — not the desk

Inspectors needed to complete their work across multiple locations while tracking schedules, routes, inspection details, and safety checks. Existing tools were fragmented and difficult to use in real-world conditions.


Key Challenges

  • Switching between multiple tools and paper processes

  • Poor visibility into routes and schedules

  • Limited time on site

  • Variable connectivity in the field

  • High cost of errors or missed steps

My Role & Scope

Wearing multiple hats to bring the system to life

I led the design of Field Portal from concept through implementation, working closely with engineering to ensure the system was both usable and technically feasible in real-world conditions.


Direct ownership:

  • End-to-end UX design

  • Mobile interaction patterns

  • Information hierarchy


Hands-on contribution:

  • Front-end development (Android)

  • Prototyping and validation in real scenarios


Collaboration:

  • Partnered with field teams to understand constraints

  • Worked with engineers on routing, data sync, and performance

Designing the Field System

From route planning to inspection completion

Field Portal needed to support a full inspection workflow — from planning routes to completing tasks on-site — within a single, cohesive system.


At a system level, the experience needed to:

  1. Plan efficient inspection routes

  2. Provide clear daily schedules

  3. Support real-time updates and changes

  4. Enable fast, accurate data capture

  5. Sync data reliably when connectivity allowed


The design focused on reducing context switching and keeping inspectors oriented throughout the day.

Key Decisions & Tradeoffs

Designing for reliability over polish

Key decisions:

  • Optimized for speed and clarity
    Interfaces were designed for quick scanning, not visual flair.

  • Designed for intermittent connectivity
    The system assumed offline or degraded conditions.

  • Minimized input burden in the field
    Data entry was streamlined to reduce time on site.


Prioritized predictability

Consistent patterns reduced cognitive load during long days.

How the System Showed Up for Inspectors

Clear, calm, and dependable

For inspectors, Field Portal provided a focused, mobile-first experience designed to work under real conditions.


Design patterns included:

  • Route maps with clear visual hierarchy

  • Schedule views optimized for glanceability

  • Simple inspection checklists

  • Location-aware context


Every screen answered a practical question:

  • Where am I going next?

  • What needs to be done here?

  • What has already been completed?

Results & Impact

Making inspectors’ lives easier

Field Portal improved the inspection experience by:

  • Reducing planning and navigation time

  • Increasing consistency across inspections

  • Improving confidence in schedules and routes

  • Supporting inspectors throughout long, complex days


Feedback from the field emphasized the value of having one reliable system instead of many disconnected tools.

Designing for reality, not best-case scenarios

Field Portal reinforced the importance of designing for real conditions — not ideal ones. This work shaped how I think about reliability, clarity, and trust as core design principles, especially in environments where tools must perform without fail.