Open to the right role

Stephen
Sherwood

Product Designer

I design products that work and make things that surprise. Occasionally both at once.

I design products that work and make things that surprise. Occasionally both at once.

I design products that work and make things that surprise. Occasionally both at once. The ratio has been improving.

About

The longer version

Product designer with 3+ years of end-to-end experience — from blank Figma file to shipped product. Founding designer at a SaaS edtech startup, Design Methods TA at the UW iSchool, and currently building a solo product.

I'm at my best in environments where design decisions have real consequences and where someone needs to champion the user when it's inconvenient to do so.

Outside work: inspired by The Great British Baking Show to bake my own creations. Trail mix cookies are very good. Butterscotch pie is improving.

Currently: Building habit.all. Open to product design roles at stable companies with a real design culture.

I've been a founding designer, which means I know what it feels like to navigate the gap between "we need a design system" and "we have three engineers and a Tuesday deadline."

My background is Informatics (HCI) from UW, with a double in Comparative Philosophy — useful when you need to defend a design decision to a skeptical CEO and an equally skeptical engineering team simultaneously.

I TA'd Design Methods at the UW iSchool for two professors at the same time — the first undergrad in the department's history to do so. HR had to invent a new job code. Two completely different pedagogies: one Figma-heavy, one writing-intensive.

Outside work: inspired by The Great British Baking Show. Trail mix cookies are genuinely excellent.

Currently: Building habit.all. Open to roles at companies with more than 10 people and a functioning design culture.

Founding designer at a SaaS edtech startup — a great way to learn exactly how much a blank Figma file can intimidate you before you stop letting it. Built the design system, shipped the LMS, wrangled offshore engineers, mentored four design interns. Roughly in that order of difficulty.

UW Informatics (HCI) + Comparative Philosophy. The philosophy part is useful for arguing with engineers. Also TA'd Design Methods for two professors simultaneously — the iSchool had to create a new HR code for it, which I consider a minor institutional achievement.

Now building habit.all solo — WebGL renderer, agentic AI architecture, HealthKit integration, and the slow realization that "solo founder" is just "founding designer" with even fewer people to blame. Enjoying it anyway.

I bake. The Great British Baking Show is aspirational television. Currently in the "follow the recipe" phase. The butterscotch pie is improving.

Currently: All-in on habit.all. Open to interesting work at companies that have survived long enough to have a design team.

Selected projects

Smash.technology
SaaS / LMS Founding Designer 2021–2024

Smash.technology — Learning Management System

Shipped a SaaS LMS MVP in 3 months. NPS improved from -27 to +46. Saved $200K via product strategy pivot.

View case study →

Production was stuck. The offshore team was building the wrong thing, the CEO was running out of runway, and I was the only designer.

I diagnosed the failure mode, pivoted to an open-source foundation, rebuilt the design system, and shipped in 3 months — after two contractor attempts failed over 8 months.

Outcome: NPS -27 to +46. $200K saved. First revenues generated. 4 design interns onboarded in their first week.

Read the full case study →

The company burned through two contractor teams over 8 months before I proposed starting over with an open-source LMS. The CEO said yes partly because we had no other options.

Three months of design system work, offshore negotiation, user research in Thai restaurants, and one very opinionated decision to kill the Smash Score feature.

Outcome: NPS -27 to +46. $200K saved. Shipped. The company didn't find product-market fit, but the product worked.

[Designer take]

The design system was the real unlock — not because it made things prettier, but because it let interns contribute without breaking things, which meant I could stop being a bottleneck.

Read the full case study →
UW iSchool
UX Research Teaching 2018–2022

UW iSchool — Design Methods Teaching Assistant

TA'd Design Methods for two UW iSchool professors simultaneously — the first undergrad in the department's history to do so.

View case study →

Most TAs work for one professor. I worked for two at once — different enough that HR had to invent a new job code.

One class was Figma and Miro-heavy. The other was writing-intensive. Code-switching between two modes of design thinking turned out to be excellent preparation for startup life.

Read the full case study →

Teaching design methods is a reliable way to discover which parts of your process you actually understand versus which parts you do on instinct.

Two professors, two completely different pedagogies. One wanted Figma deliverables. The other wanted thousands of words of written analysis per week. I wrote a lot of words.

[Designer take]

Grading other people's design work made me a much harsher critic of my own. Recommended.

Read the full case study →

habit.all

An ambient data art app for smart home displays.

Connects personal data streams — health metrics, weather, calendar — to generative visual artwork rendered in real time on displays like Samsung Frame and Amazon Echo Show.

See the project →

I got tired of dashboards that looked like spreadsheets. So I made one that looks like a painting that changes when your heart rate does.

habit.all connects to personal data streams — Apple HealthKit, weather, calendar density — and generates real-time visual mutations in digital artwork on smart home displays. Solo founder project: product strategy, technical architecture, and design all mine.

The argument it makes: data has an aesthetic life. Utility and beauty are not opposites.

See the full project →

I got tired of dashboards that looked like spreadsheets. So I made one that looks like a painting that argues with you.

The architecture uses a multi-modal agentic harness: an orchestrator routes tasks between specialized sub-agents — data ingestion, art generation, parameter mapping, rendering, billing — each with typed input/output contracts. Personal data stays on-device. Only prompts and billing events touch the cloud. Renderer is WebGL, cast via AirPlay/Chromecast.

Currently at prototype stage, which means I'm simultaneously debugging shader code and writing GTM strategy. This is fine.

[Designer take]

Building this alone is the best design education I've had since the founding designer role. Every decision is mine, which means every mistake is mine too. Recommended.

Full technical breakdown →

Let's connect Let's talk Say hello

Open to product design roles at stable companies with a real design culture. Best way to reach me is email.

If you're building something that deserves better design and you want someone who'll push back when it matters — I'd like to hear about it.

If you have opinions about design systems, generative art, agentic architecture, or the right way to make butterscotch pie — let's talk.