The Physical-Digital Gap

There’s a version of design thinking that treats physical and digital as separate disciplines with separate practitioners. Architects design buildings. Product managers design software. The two worlds co-exist but rarely collaborate, and rarely learn from each other.

That separation is becoming harder to defend.

What’s Converging

Walk into any serious woodshop today and there’s a computer running it. CNC routers, laser cutters, parametric modeling tools — the making has gone digital. The hands still matter, but the mind is working in software before a single cut is made. The same is true in architecture, in fabrication, in fashion manufacturing.

The inverse is also happening. Digital products are increasingly concerned with how they translate into physical behavior — how an app changes the way someone moves through a space, organizes a kitchen, or decides what to build next weekend. The screen is no longer the endpoint. It’s a step in a process that terminates in something real.

The Problem With Picking a Side

Studios that specialize in one domain tend to hit a wall at the boundary. A digital-only team builds a tool for woodworkers and gets the interface right but doesn’t understand the workflow — the way a cut list gets marked up on the shop floor, the sequence constraints that a CNC machine imposes, the fact that some decisions only get made when you’re holding the wood. A physical-only firm designs a beautiful space but can’t think through how occupants will use it with their phones out, looking things up, navigating, adjusting.

Both end up designing for an idealized user who lives entirely in their domain.

What the Middle Looks Like

Designing across the physical-digital boundary doesn’t mean doing both things poorly. It means understanding how each discipline informs the other — and having the intellectual honesty to admit when you’re operating outside your depth.

For us, it means building software that’s informed by physical constraints. KerfOS isn’t just a cabinet design tool. It’s an attempt to translate the mental model of a woodworker into something a screen can hold — cut sequences, grain direction, the relationship between a sheet of plywood and what you’re trying to get out of it. That context comes from being in the shop, not just studying the problem from a desk.

It also means taking physical design principles into software. Universal design — the idea that products should work for people across a wide range of abilities and contexts — comes from architecture and urban planning. It applies just as directly to a dashboard or a mobile app, probably more so, but software teams rarely engage with it at that level.

Why It Matters Now

AI is accelerating both worlds simultaneously. Generative tools are producing architectural concepts, furniture designs, and digital interfaces at a pace that’s compressing the time between idea and artifact. The gap between a design and a made thing is shrinking.

That makes it more important, not less, to understand the full path from concept to physical reality. The design decisions that matter most happen at the boundary — where a digital model meets material constraints, where a workflow in software meets a person standing in a real space trying to do real work.

The studios that can operate at that boundary are going to be better positioned to do useful work in the next decade. That’s the bet we’re making.