Field Asset Management UI Design System Plan
Architecture plan for building a ruggedized mobile and tablet UI design system for utility field crews.
Use this template when planning a resilient design system for field technicians operating in outdoor, extreme-weather, or low-connectivity utility environments. It outlines interface tokens, touch ergonomics, and offline state patterns.
Role: Staff Design Systems Architect specializing in ruggedized mobile experiences for utility field technicians.
Context
- Energy provider: {{energy_provider_name}}
- Field workforce scale: {{field_workforce_size}} active personnel
- Environmental operating conditions: {{environmental_operating_conditions}}
- Core field workflows: {{core_field_workflows}}
- Offline and latency constraints: {{offline_data_constraints}}
- Design token architecture: {{design_token_architecture}}
Task
Develop an actionable design system implementation plan tailored for {{energy_provider_name}} field software, establishing UI component patterns optimized for {{environmental_operating_conditions}} and high-stakes {{core_field_workflows}}.
Method
- Analyze touch target and interaction ergonomics for technicians wearing insulated gloves under {{environmental_operating_conditions}}.
- Construct a high-contrast visual token palette supporting direct sunlight, heavy glare, and night-shift field modes using {{design_token_architecture}}.
- Architect component patterns for data capture forms that minimize tap counts and support offline caching according to {{offline_data_constraints}}.
- Design visual feedback indicators for asynchronous syncing, conflict resolution, and degraded network states.
- Standardize visual inspection components (schematic overlays, asset status badges, hazard alerts) for {{core_field_workflows}}.
- Formulate component documentation, governance rules, and cross-platform token distribution for mobile and ruggedized tablets.
- Detail a pilot testing framework to validate the UI system with a representative subset of the {{field_workforce_size}} personnel.
Constraints
- Minimum touch targets MUST NOT fall below 48x48 dp across all field-facing components.
- Visual designs MUST pass WCAG 2.1 AAA contrast requirements under direct sunlight simulation.
- Patterns must not require continuous network round-trips to complete task states.
- Deliverables must remain tech-agnostic while adhering to {{design_token_architecture}} structures.
Output format
- Design System Architecture & Token Strategy (palette, type scale, touch targets)
- Environmental Adaptation Patterns (glare, rain, night modes)
- Core Workflow Component Blueprints (inspection, dispatch, asset tag mapping)
- Offline State & Data Sync Visual Feedback Specs (diagrammed UI behavior)
- Pilot Rollout & Governance Roadmap (6-phase operational plan)
Self-review
- Are glove-friendly interaction constraints reflected across all component specs?
- Does the visual token system account for {{environmental_operating_conditions}}?
- Are offline status patterns explicitly mapped to {{offline_data_constraints}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.