Context
Augmenta generates constructible, code-compliant designs of electrical raceways: the conduit, cable tray, and supports that connect every piece of electrical equipment in a building. Their target user is the Virtual Construction Designer: the engineer inside Autodesk Revit who plans how a project actually gets built. Think Figma, but for the physical world: high-stakes, governed by real-world physics, strict compliance, and precise engineering standards.
I was the sole product designer on a small, engineering-led team, owning product design strategy, research, and execution. When I joined, there was a single design partner, a handful of pilot firms testing, a growing waitlist, and the company was pre-revenue and investor-funded. The product had grown up alongside that first design partner, so their specific workflow had shaped most of its decisions.
Why it matters
Construction runs on thin margins. Rising material costs, inflation, and waste leave little room for error. Modern commercial buildings are staggeringly complex, demanding tight coordination across electrical, mechanical, and plumbing trades that are usually run by separate firms, in silos.
To de-risk all of this, large projects rely on Building Information Modelling (BIM): Virtual Construction Designers model each trade in 3D, inside the architect's Revit model, so the hard decisions get made up front. Done well, components can be pre-fabricated off-site: installers simply follow the blueprint instead of cutting and coordinating in the field. That is the ideal modern workflow.
BIM also asks a lot. Skilled modellers are in short supply, coordinating across separate trades takes real care, and a single sync error or difference of approach can cost significant design effort and still leave problems to solve on site. Augmenta set out to automate this technical design work with AI, starting with electrical, ultimately translating an AI-generated, human-supervised model into real, fabricated components any installer can pick up and install.
The opportunity
The prize is enormous. A traditional manual workflow (model, coordinate, edit, then pre-fabricate) represents a huge block of skilled design hours before anything reaches the field. A flawless AI generation could, in theory, produce the same output in a fraction of that time: a potential 95%+ reduction in modelling effort, with no edits and no extra coordination.
When I joined, the product had not reached that point yet. It took many generation cycles (often weeks) to reach a useful output, before any coordination or edits. The time savings were still modest, and the way generations worked made firms cautious, so pilot firms were hesitant to use it on live projects.
That set our North Star. Pilot firms told us that about a week of iterating (a handful of cycles) was how long they could give it to produce a useful result. A week isn't ideal, but it was the window they were willing to work within. Getting a trustworthy, useful output inside that window became the goal everything pointed at.
The challenge
The product had more to give than people could easily reach. Three themes, one underlying cause:
- Broad feature set: built to serve every persona at once
- Room for more consistency: patterns and components varied across the app, and the information architecture could be clearer
- Time to value: it took several cycles to reach a useful output, which tested firms' patience
These touched the whole business: customers often needed hands-on support to get from a generation to a constructable design; the company wanted to keep pilot firms engaged and bring compute and support costs down as it grew; and design had to balance firm-specific needs against scalability and low-touch usability.
What made this especially interesting is that the output is objectively measurable. A design is “constructable” only if it satisfies several dimensions at once: correct electrical load and capacity for the building, the right materials, and clash-free coordination against the mechanical and plumbing trades. The stakes are high: a wrong calculation can waste material, cost money in the field, or (in the case of electrical load) cause serious real-world damage.
So Augmenta's engineers held a deliberately high bar for correctness and completeness, only surfacing solutions that met strict mathematical standards. The trade-off was that a minor input error (a mislabelled roof material) could mean no solutions at all, which left customers unsure what to change.
Approach
To get inside the customer's head, I designed a workshop I ran on repeat with each of our pilot electrical design firms. The goal was to map their real workflows, test product fit, and prioritise what to build or deprecate. The format was a journey-mapping and service-blueprinting exercise: we mapped their key functions and deliverables over time, walked through which Augmenta capabilities fit each phase, and captured their feedback.
By the end we had a blueprint for each firm: similar in shape, but with telling differences. We consolidated them into a single unified customer journey, and one pattern jumped out: the only process every firm shared, at roughly the same point, was electrical routing.
That reframed the product. Our software didn't just route: it also calculated electrical load and chose materials, a far more complex job. But most designers at these firms didn't do those calculations, as that responsibility sat elsewhere. The capability that defined the product went beyond what most of the market needed. It reflected our first design partner's workflow, which turned out to be less common than we had expected.
The decision: refocus 100% on electrical routing, not calculations. Less strain on the system, a more concentrated effort to do one thing well, and a clean path to many more customers.
Renewed focus: Virtual Construction Design teams, from project kickoff through early phases of coordination. Not earlier (device layout, conduit sizing). Not later (detailing, assembly drawings). One persona, one slice of the workflow, done well.
Solution
Three challenges, three answers.
1. Right surface for the right user
Identified VDCs as the MVP persona and doubled down on solution data: more signal about completion (routed sources and destinations) and correctness (constructability). Everything the VDC teams didn't care about, including the load calculations, came off the critical path.
2. Consistency through a design-system overhaul
The product had been built in close partnership with an electrical design firm, before there was a designer on the team, and engineering preferences had shaped much of it. A heuristic audit pointed to the next opportunities: clearer information architecture, better use of screen space, more visible system status, and errors that helped people troubleshoot.
So I brought in Ant Design as a foundation and worked with engineering to replace every component: redesigning each screen, writing specs and stories, and handing off a master prototype we used for team alignment and testing with pilot firms. The wins were immediate: clearer IA, far higher screen density (several times more studies visible at once), and a dark mode the pilot firms loved.
Framing mattered too. We replaced engineering-speak with intent-aligned language: “Placement considerations” instead of “Unhandled error”. Alarming-sounding failures became calm, actionable guidance.
3. Faster value through better inputs and signal
Two changes went straight at time-to-value.
Better inputs. Unlike a chat assistant, these prompts are 100% mathematical. The first generation often needed more rounds because the input wasn’t granular enough, so we reorganised the prompt structure and roughly doubled the number of fields for fine-grained control. That alone doubled the usability of the very first generation, right out of the gate.
Better signal. Because of the high mathematical bar, the system would detect an error (a clash, say) and silently stop, producing zero output even after a customer had spent time prompting. We did it to save compute and to avoid handing over obviously unconstructable designs. The trade-off was less signal: the customer couldn’t see why a run had stopped, even when the cause was a small, fixable input error on their end.
After analysing hundreds of failed generations, we found the common culprits (clashing chief among them) and made a bet: instead of stopping, let the generation complete and visualise each problem in 3D, as a red box right where the issue was. It worked. Customers could see the full solution, tie each red box to specific parts or routes, fix the problem themselves, and lean on Augmenta far less. Surfacing this previously hidden signal sent successful generations up ~900% and user analysis of solutions up ~400%.
The fully realised workflow ships back into Revit, where the generated designs flow straight into existing detailing and spooling pipelines.
Impact (across the engagement)
The downstream result: detailed 3D schematics flow into pre-fabrication and field installation in days instead of weeks. Engineering interventions (the clearest measure of how well the product could scale) dropped by a third, closing in on the North Star of a useful output inside the window pilot firms had given us.