Rebecca Horwitz
FORM
FUNCTION

Untangling systems that run in the background, solving workflow friction and bringing clarity to both form and function. Using the tools that exist, or designing new ones with you.

About 01

I design systems that create clarity for the people using them, and the teams running them.

I'm deeply tuned into how people feel in a space, digital or physical. I notice discomfort. I observe friction. And I build structures — technical, visual, procedural — that gently resolve that tension.

My background is in design: textiles, objects, websites, operational flows. I've always moved between the tactile and the systemic, seeing how the tools we use, the way they look and feel, and the logic behind them all shape the experience we have.

One element of good design is the interface, but just as important is everything behind it: the logic, the systems, the communications, and the process. I work best in complex environments where things are breaking down. I listen, map the terrain, and create frameworks that don't just function — but bring calm, coherence, and confidence to the people who rely on them.

To me, good design isn't just about what's seen. It's about how something feels to use, and how well it holds up under pressure. It's about helping people understand, move forward, and feel supported by the systems around them.

Rebecca Horwitz Geneva, Switzerland
Available worldwide
Examples 02
Selected Work
Approach 03

From friction to flow. How I work.

01

Listen

Shadowing the team and learning the full system. Understanding what tools have been tried, how things arrived at their current state, where friction persists, and what workarounds are in place. I gather as much information as possible, then synthesize everything to see how each element impacts the others.

02

Understand

Rough sketches and notes first, then structured mapping in Miro and spreadsheets. For operations work, this often means tracing the full lifecycle of an order: vendors, lead times, team handoffs, customer communications, role responsibilities, and downstream effects.

03

Define

Framing the problem and defining success criteria. Documented in a project board, a one-page overview, and a refined Miro board for visual comprehension. This becomes the shared reference before any building begins.

04

Explore

Evaluating whether existing tools can be tailored or automated to meet the need, or whether the system requires a deeper redesign. Weighing urgency, effort, role reassignment, and whether the issue can be patched or needs to be rebuilt entirely.

05

Test

Walking through the proposed system with stakeholders before implementation. Acting out real scenarios until all parties are confident the solution holds under actual conditions.

06

Deliver

Handoff varies by project: documentation, training, a built tool, or a complete playbook. The goal is to leave the team equipped to own, maintain, and evolve the system independently.

Contact 04

Working through something complex?

Share a bit about your product, team, and the friction you're experiencing. I'll respond personally.