Rebuilding the most ignored tool in construction
Scheduling is the backbone of every construction project. Yet Procore's tool was so limited that only 5% of users ever touched it. I led the end-to-end redesign. From defining the product vision to shipping a connected, cross-platform experience that finally made scheduling worth using inside Procore.
- Design Leadership
- Strategy
- UX Design
My Role
Design lead and vision owner. I set the strategic direction, led a team of designers across multiple workstreams, aligned stakeholders across product and engineering, and drove the work from concept to scaled adoption
The Problem
The tool existed but was barely used. It was too limited, too disconnected from the rest of the platform, and not compelling enough to replace the external tools teams were already relying on.
Strategic Direction
New focus on value
Data showed only 30% of paying customers had ever uploaded a schedule and just 4.1% of projects had any schedule data at all. The tool was failing because it lived in isolation from everything else teams were doing in Procore. I pushed back on a surface-level redesign and defined this as a platform investment, which changed the scope, the resourcing, and the timeline conversation entirely.
Designing for five personas without losing focus
The tool needed to serve five distinct user types. From the person building the master schedule to the field supervisor tracking daily work to the executive monitoring milestones. Rather than designing for an average, I mapped what each type actually needed to accomplish and used that to sequence what to ship first, what to defer, and what to say no to.
Design Execution
Leading design across multiple teams simultaneously
I led a team of talented designers each working on a different layer of the product at the same time. My job was to set the direction, keep the work coherent across teams, and make the tradeoff calls that kept everything moving as a unified product rather than a set of disconnected features. That meant regular design reviews, close alignment with product and engineering leads, and a clear point of view on what mattered most at every stage.
Connecting scheduling to the rest of the platform
The highest-stakes design challenge I directed was bridging scheduling with other tools. Specifically procurement workflows managed by entirely separate product teams. When a delivery date slips and nobody catches it, work stops. I set the direction for a cross-tool linking system with real-time conflict detection, surfacing risks at three levels at once: a page-level alert, a row-level indicator, and a flagged field in the detail panel.
Versioning: unlocking collaboration at scale
A key blocker to broader adoption was trust. Teams wouldn't give multiple people edit access if there was no way to recover from a mistake. I led the design of a full versioning system: automatic history capture, named save points, a read-only preview of any prior state with color-coded change attribution, one-click restoration, and side-by-side comparison showing exactly what shifted and by how much. Beyond error recovery, version comparison enables two high-value workflows: tracking how a plan evolved over time, and performing historical analysis to identify exactly when a delay was introduced and by which change.
Outcome
From a baseline of 152 to 1,040 — on pace to hit 2,000 by end of year
The 2026 goal was to grow deeply committed company adoption from 152 to 2,000. By May, seven months in, the product had reached 1,040, well ahead of a linear pace. Fewer than 1 in 20 users had ever opened the old tool. Today over 7,000 professionals use it daily across nearly 8,000 active projects. Over 1,040 companies have deployed it across at least a quarter of their active work, which is the threshold that signals a real organizational switch, not a trial.
A roadmap that kept growing beyond the original scope
The phased strategy I defined is still driving the product forward. Versioning ships July 2026, directly enabling broader team access and accelerating toward the adoption goal. The cross-tool integration moved into active engineering in June 2026.