Client:
Sobha Realty | Dubai, UAE
Tools:
Figma, Photoshop, Illustrator, After Effect
Year:
2023
Our primary goal was to design and develop a comprehensive "First Time Right" (FTR) application for the construction industry. The core objective was to drastically minimize errors, defects, and the need for rework throughout the construction lifecycle. By enabling flawless execution of tasks on the initial attempt, we aimed to significantly elevate client satisfaction, instill stakeholder confidence, and establish our organization as a benchmark for excellence in construction project delivery.
From a UX perspective, the goal was to create an intuitive, efficient, and reliable platform that empowers users across various roles to achieve higher quality standards with minimal friction.
The construction industry is inherently complex, often plagued by rework due to errors and defects. Our key challenges in designing this FTR application were:
Complex Workflows: The existing inspection and complaint management processes involved multiple stakeholders (Foremen, Engineers, QCS, QAQC, Business Excellence, Special Auditors) with hierarchical approval flows. Translating this complexity into a clear, manageable, and error-proof digital workflow was paramount.
Data Capture and Visualization: The need to capture detailed defect information, including photos and markings on drawings, and then present this data in meaningful reports (e.g., "Defect per flat - Activity wise," "Daily FTR percentage") posed a significant challenge for intuitive data input and clear visualization.
Offline Capability & Synchronization: Construction sites often have unreliable internet access. Ensuring the application functioned seamlessly offline with robust auto-synchronization upon reconnecting was critical for user adoption and data integrity.
User Role Management & Permissions: Implementing a granular role-based access control system that defined specific privileges for each user role, while maintaining a consistent and secure user experience, was a complex undertaking.
Performance & Scalability: The application needed to handle a high volume of users (minimum 1000 users with 700 foremen) and process commands in less than 2 seconds, requiring careful consideration of performance from the ground up.
Responsive Design: The application had to be fully responsive and usable across various devices and screen sizes, from mobile phones used on-site by foremen to desktops used by administrators.
Our target audience spans various roles within a construction organization, each with distinct needs and responsibilities:
Foremen: Simple mobile users for defect capture, rework, and feedback.
Engineers (Level 1 Approvers): Perform initial inspections, approve/reject requests, and detail defects with photos.
QCS (Level 2 Approvers): Similar to Engineers, focused on quality control inspections.
QAQC (Level 3 Approvers): Conduct random inspections, approve/reject requests, and manage the CAPA process.
Business Excellence Team: Approve improvement projects (Yellow/Green Belt) based on recurring defects.
Special Auditors: Have unrestricted access for audits and request creation.
Administrators & Process Owners: Manage users, reports, data analytics, and system configurations.
Before embarking on the design, a thorough data analysis of the existing processes and requirements was conducted based on the Business Requirements Document (BRD). Key insights gathered included:
Inspection Flow : A multi-level approval process for inspections (Foreman → Engineer → QCS → QAQC) was designed, including conditions for rejections and rework.
Complaint & CAPA Logic : The complaint management module was built around specific criteria for opening Corrective and Preventive Actions (CAPAs), with project registration for recurring defects.
Reporting Needs : The system requires powerful data aggregation and filtering to generate key reports such as Defect per flat and Daily/Monthly FTR percentage.
Master Data Management : A bulk upload feature was needed for administrators to manage master data like unit classifications, activities, and defect types.
Non-Functional Requirements : The system was designed to meet performance targets (e.g., 2-second command processing), work offline, be responsive, and have robust security.
Communication : Automated email notifications were implemented to address existing communication gaps and improve workflow efficiency.
User Flows
Inspection Process - |
 |
Complaint Booking Process - |
 |
Project Registration Process |
 |
Our approach began with a deep dive into the provided Business Requirements Document (BRD). We treated the BRD as our foundational blueprint, meticulously dissecting each functional and non-functional requirement.
Stakeholder Interviews & Workshops (Simulated)
I would conduct simulated stakeholder interviews and workshops with key user groups, such as Foremen and Engineers.
User Flow Mapping
We mapped detailed user flows for inspections, complaint booking,
Information Architecture (IA) Sketching
I began by sketching the high-level information architecture, organizing modules.
Wireframing Key Screens
After creating the information architecture, we moved to low-fidelity wireframes for critical screens to quickly test layouts and functionality.
Understanding the technical constraints like offline sync and performance was key to making feasible and effective UX design decisions.
Our step-by-step process
Steps towards the new structure and overall experience:
We crafted a journey map to demonstrate the high-level steps that the customers might go through in the future.
We revamped the Information Architecture (IA) by organizing and structuring the content in a way that supports usability and findability.
We defined the flows that a user would ideally go through on the redesigned website.
Steps towards the new look and feel
We created several visual collages (moodboards) featuring elements that illustrate potential directions for the brand’s new identity.
We chose a clean and friendly design. We also set the style for the images.To get the best possible outcome.
Additionally, we held regular check-ins with the developers and SEO expert, while continuously gathering input from the stakeholders.
Our deliverables
Research documentation.
Prototypes we used for testing.
Final, annotated screen-flows for desktop and mobile.
UI Kit with foundational elements, components and guidelines to maintain a unified website.