During my eight years at SOM, I led firmwide research and software development initiatives. I co-founded SOMtools and was product lead for OpenBox, its architecture toolkit. It remains in use today.
Role - Co-founder / Product Lead
Team - In collaboration with computational designers, software developers, IT specialists, architects and structural engineers across Skidmore, Owings & Merrill (SOM).
2019 - 2025
90%
faster than by hand
40+
projects
1 in 3
SOM designers
137
tools
SOMtools turned siloed, one-off workflows into a scalable, standardized and accessible set of tools for architects and engineers. It has four toolkits on one platform.
Before
One-off scripts saved in project folders
After
Four toolkits in one unified platform
OpenBox takes a building from massing to a documented facade with a collection of reusable building blocks.
From idea to detailed model: Area Calculations, Building Systems, Facade Development, Facade Analysis
SOM had developed decades of computational knowledge and tools, but they were fragmented within teams, studios and offices. Architects and engineers were solving the same problems by hand or with one-off scripts.
Nothing like this existed at SOM. I started OpenBox as a grassroots effort. It was later funded by the firm, and SOMtools grew from there.
12
global offices
6
disciplines
1,300
people
10k
projects in 50+ countries
I assembled a team from across the firm: computational designers, software developers, IT specialists, architects and structural engineers. Together we developed an MVP and rolled it out to a pilot group.
After the feedback we refined and consolidated the toolkit: speed and reliability for the highest-impact tools, and the rest retired.
50
beta testers surveyed
8
power users
16
hours of testing each
11
tool categories rated
Alongside tool development, I led the work that made SOMtools trusted. Local champions in each office carried the tools into project teams, and an automatic installer put them on every designer's machine.
Standards. Naming conventions, input and output formats, UI patterns.
Training. Workshops, tutorials and presentations.
Documentation. Tooltips, searchable knowledge base, example workflows.
Contribution. Feature requests, bug reports and contributed tools.
After deployment, I set up a continuous feedback loop. Usage analytics tracked adoption and the most-used tools, and updates were prioritized from user feedback. OpenBox became the blueprint for the other three toolkits.
137
tools
9
global offices
207
active users
90%
Faster
Compared to the manual process. From 1 day to 30min.
40+
Project Impact
Projects delivered.
100+
Time Reinvested
Hours of time given back to design.
4
Scalability and Longevity
Toolkits built on the OpenBox blueprint, still in use today.
Led end-to-end product development, from identifying user needs and setting the roadmap to global deployment.
Created scalable, repeatable frameworks: modular tools that work across projects and offices.
Created feedback loops from analytics and user feedback, and focused on high-impact features.
Empowered local champions in each studio to drive adoption.