ContractorOS
Background & Problem
FacilityOS ContractorOS is a comprehensive contractor management system designed to streamline operations for facilities that work with external contractors and vendors. The platform addresses critical pain points in contractor management, including compliance tracking, document management, onboarding, and safety protocols.
The solution targets facilities management professionals who need to efficiently manage multiple contractors while ensuring regulatory compliance and workplace safety. It serves industries such as manufacturing, healthcare, education, commercial properties, and any facility that regularly engages contractors for maintenance, repairs, construction, or specialized services.
Role
Lead Product Designer
Timeline
6 Months
Project Process
We started with in-depth secondary research using the data from our analytics team and drawing hypothesis and insights on what needs to be exactly worked on.
Phase 1: Product Concept Visualization for ContractorOS
As the CTO's trusted designer for this new contractor management platform, I was tasked with rapidly transforming their vision into tangible concepts. Having demonstrated success with previous iLobby products, I was brought in to create visual representations that would effectively communicate the potential of ContractorOS to key stakeholders.
My Approach Focused on Two Core Deliverables
These rapid visualizations bridged concept and development, letting stakeholders assess value before major investment. My designs weren't final products but strategic tools that catalyzed discussions on priorities and requirements. By visualizing the CTO's vision effectively, I aligned the team on direction and secured stakeholder support early, preventing wasted development resources.
Understanding the Core Features
Main Target (Personas)
Phase 2: Research and Developing User Flows
After securing stakeholder approval, we intensified development with the VP of Engineering joining our sessions. Together, we assessed technical constraints affecting our user flows and design concepts. Our strategy leveraged existing components reconfigured in novel ways, creating three distinct product variations tailored to each user persona's specific needs and workflows.
Statistics & Research
We collected this data through industry reports (Gartner, Forrester), surveys with 30+ facility managers and 70+ contractors across multiple sectors, competitive analysis of five leading platforms, and four focus groups with industry professionals to validate pain points and quantify improvement opportunities.
We incentivized early participation by offering contractors and potential clients exclusive beta access to ContractorOS, along with guaranteed discounted rates upon full launch. This approach not only secured valuable testing partners but also created a pipeline of committed customers eager to deploy the finalized platform.
Overview of Persona Objectives
User Flow Form Creation
User Flow Form Triage
Phase 3: The Design
To validate if our redesign actually had impact, we tested our interface with over 500 users with specific goals. Here are some methods we used.
Phase 4: Iteration Process & Changes
The Beta launch marked a critical point where we could begin seeing the results of our work. We needed to leverage this opportunity to actively communicate with companies testing the beta version, identifying any user experience or logic issues that emerged.
Iteration of User Flow 2.0
We scaled back our custom component maker after discovering users preferred templated generic forms over more customization options. This surprised us, as we had anticipated the opposite. Nevertheless, we maintained an open channel with our customer service team to assist with developing custom forms when needed.
Reflections & Findings
Throughout this project, my collaboration with the development team and product managers proved to be both challenging and rewarding. Working closely with developers taught me the importance of clear communication when translating design requirements into technical specifications. The development team's technical constraints often pushed me to find creative solutions that maintained design integrity while being feasible to implement within our timeline.