Project Summary
The Launch Experience for a Construction Intelligence Platform
Senior Product Designer · Strategy, UX, UI, prototyping · Shipped at Avvir
Overview
Avvir's platform could detect deviations and clashes by comparing 3D reality-capture scans against the design model. It was powerful, and it dropped every user straight into that depth: thousands of deviation highlights, long issue lists, dense model overlays. A VDC specialist (Virtual Design and Construction, the team that runs the laser scans and 3D models) could work there. A project manager or executive was lost.
I designed Project Summary as the front door to the whole platform: a project-level view that answered "is this project healthy" before anyone had to descend into scan-level detail. It was built to be the default landing experience and the top of a funnel that led down into cost, progress, and quality, each at the altitude the user needed.
Project health at a glance, before diving into scan detail.
The problem
The product was organized around the data, not the decision. Everyone landed in the same expert view regardless of what they came to do. Project managers needed to know what changed this week and where to focus. Executives needed to know which projects were trending toward cost or schedule failure. Both were forced to either learn a specialist tool or fall back on manual spreadsheets and verbal briefings.
The solution: one architecture, many compositions
The core design bet was structural. Instead of building separate products for separate roles, I designed the platform as a system of modular panels, 3D model, costs, progress, filters, comments, that could be composed differently for different people from one shared codebase.
Project Summary is the executive composition: pulled-up health signals, a building-level progress view, trade build-accuracy indicators. The same panels recompose for a project manager into a triage view, and for a VDC specialist into a full line-item view with complete data access and no capability regression.
I designed and shipped Project Summary for both desktop and mobile. The mobile experience came directly from watching how the work actually happened: in one interview, a project manager took my call while walking the site, checking status on his phone between conversations with trades. Executives read project health on a monitor in a coordination meeting; project managers pull up the same signals on a phone mid-walkthrough. Same composition, different contexts.
Start at project health, drill into detail only when needed.
That funnel led into distinct destinations. The first product I shipped at Avvir was the Budget experience, its own surface within the system, reached by drilling down from the overview. It was built around a 3D model tied to a work breakdown structure cost table that reconciled reported, captured, and modeled totals, with hierarchical trade filters and comments threaded to specific line items. Project Summary was the executive front door, Budget was the cost destination, floor detail was another, all composed from one panel system sharing a design language and a data model. That product became the primary driver of new bookings the year it shipped, roughly 60 percent of new business per my manager.
One panel system, recomposed per role.
Reflection
Enterprise tools generate enormous data and rarely help anyone interpret it fast enough to act. The lesson I carry forward: the same dataset needs different compositions for different people, and the architecture has to make that cheap. That thesis is the spine of how I design complex products now.