Case Study · Branch 3D (StructureCraft)
UX design system for a hybrid 2D/3D structural engineering platform
Branch 3D (StructureCraft) set out to bridge the gap between traditional 2D structural engineering workflows and the spatial precision of 3D modeling — creating a hybrid platform where engineers could design, analyse, and visualise complex structures within a single, coherent environment.
The engagement was foundational — establishing the UX patterns, interaction model, and design system that would underpin the platform's long-term development. The challenge was twofold: designing for users who think spatially but work in 2D, and setting conventions robust enough to scale with the product.
Add a key insight or design principle that guided the project here.
Structural engineering workflows sit at a unique intersection of precision, regulation, and creative problem-solving. Engineers work across multiple tools — often switching between 2D drafting, analysis software, and 3D visualisation — and carry deep mental models of how geometry, loads, and connections behave in space.
Understanding this meant understanding not just the software gaps, but the cognitive model engineers bring to their work — and where a hybrid 2D/3D environment could support rather than disrupt that model.
Add caption describing the research finding or methodology shown here
Add additional research findings, user quotes, or insights here
Add caption here
Add caption here
The structural engineering software landscape is dominated by tools that excel in analysis or drafting, but rarely both — and almost never in a fluid, spatially-integrated environment. Tools like Revit and Tekla are powerful but carry significant UX debt. Newer entrants like SketchUp and Rhino offer 3D fluency but lack engineering-grade analysis integration.
Branch 3D's opportunity was in the space between — a platform purpose-built for the hybrid workflow that engineers increasingly need, without the legacy constraints of older tools.
Add caption here
A short engagement demanded clear priorities. Rather than designing individual screens, the focus was on establishing the patterns, principles, and component conventions that would make every future design decision faster and more coherent.
The process began with deep dives into the existing product and competitor tools, followed by rapid concept exploration in Figma. Early explorations focused on the core interaction model for navigating structural geometry — how users select, manipulate, and inspect elements in both 2D and 3D space.
Add caption here
Add caption here
One of the most significant design challenges was establishing interaction patterns for 3D structural models — navigating, selecting, and editing geometry in a way that felt intuitive to engineers rather than to 3D artists or game developers.
The conventions of engineering software differ meaningfully from those of DCC tools. Selection behaviour, camera navigation, manipulation handles, and feedback mechanisms all needed to be considered through the lens of structural engineering workflows rather than borrowed wholesale from adjacent domains.
Add caption here
Add caption here
Add caption here
In a compressed engagement, the work delivered a coherent design foundation — interaction patterns, component conventions, and a visual language the Branch 3D team could build on with confidence. Early alignment between design, engineering, and product meant fewer costly pivots later.
Add specific outcomes, deliverables, or impact metrics here as they become available
Add caption here
Working within a compressed timeline on foundational work demands a particular discipline — the ability to make principled decisions quickly, communicate them clearly, and resist the temptation to over-specify what should remain flexible for the team that follows.
The structural engineering domain also reinforced a recurring theme across complex technical products: expert users have deeply held mental models, and the designer's job is to understand those models before attempting to improve on them.
Add specific learnings, challenges overcome, or reflections from the engagement here
Add notes on the platform's future direction, areas for continued design investment, or potential follow-on work here