Streamlining On-Site Issue Reporting
Empowering on-site construction teams to capture, communicate, and resolve issues effortlessly — anytime, anywhere.
Role Product Designer
Timeline 5 months
Team PM, UX, Engineering, Field Ops, QA
Users Site Engineers, Supervisors, Operations Managers
Outcome Shipped and adopted across active projects
Overview
On construction sites, where every minute counts, reporting an issue shouldn’t slow the work down.
Yet, most teams still rely on WhatsApp threads, photos with no context, or handwritten notes to flag problems — leading to confusion, missed updates, and costly delays.
I saw an opportunity to empower non-technical field workers with a simple, intuitive tool that made digital reporting feel as natural as sending a message.
By reimagining how workers capture and track issues, we aimed to bring clarity, accountability, and confidence to daily operations.
Role
As the Product Designer, I led the end-to-end design process — from framing the problem space and uncovering user insights to designing a mobile-first, cloud-based workflow.
I collaborated closely with product and engineering partners to ensure the experience was not only functional and scalable, but also delightful and human-centered.
Outcome
After rollout, teams observed faster issue resolution and higher adoption of a single, centralized system for tracking on-site problems.
Beyond efficiency gains, the platform established a shared source of truth, improved accountability between field and operations teams, and reduced the coordination overhead previously handled through calls, messages, and ad-hoc tools.neering partners to ensure the experience was not only functional and scalable, but also delightful and human-centered.
Understanding Life on the Construction Site
How we learned
To design for workers in a fast-moving, high-pressure environment, I needed to understand their day-to-day reality — not just their tools. Over the course of two weeks, I employed a combination of qualitative and observational research methods to identify friction points and habits that influenced the design direction.
Methodologies
-
Field Shadowing
Observed workers capturing issues live on site — noted gestures, device use, pain points.
-
Contextual Interviews
Conversational interviews with foremen, engineers, and field staff about their workflows and challenges.
-
Task Flow Mapping
Mapped how information traveled from site to back office — handoffs, delays, data gaps
-
Rapid Prototype Feedback
Tested low-fidelity mobile mockups on site to validate assumptions quickly in context
Outcome
I designed a mobile-first experience that breaks down the reporting process into three quick steps:
Designing a workflow that fits in your pocket
Key screens
🎛️ Ticket Dashboard – Field View
A quick-glance dashboard for field workers to track tickets they’ve raised. Status filters and clear ticket cards make it easy to follow progress and stay updated. Dark & light modes support visibility in both indoor and outdoor site conditions.
🛠️ Select a category of your issue
Users select the issue category from clear, icon-based options. The search bar supports quick filtering, while the highlighted selection confirms their choice.
Designed for fast input in high-pressure field conditions, this step keeps the reporting process focused and intuitive.
📸 Record the Issue – Step 2 of 3
Users can quickly snap or upload photos to document the problem. In-app markup and caption tools let them highlight key details, reducing ambiguity for reviewers.
This speeds up communication between field workers and the resolution team — no extra calls or back-and-forth needed.
🎤 Add Details – Step 3 of 3
Workers can record voice notes and set issue priority with one tap, making it easier to report on the go, especially in noisy or hands-busy environments. This improves clarity and streamlines the triage process.
Design System
