Product Design for the Web
Beyond HTML and CSS
Description
There was a stretch, roughly the mid-2000s, when a web designer's toolkit was easy to name. You knew HTML, you knew CSS, maybe a little Photoshop, and you could turn a brief into a page that looked right in a browser. That was the job. Randy Hunt, who spent years designing at Etsy and eventually ran its creative organization, watched that description quietly stop being true. The pages were still there, the markup was still there, but the work that mattered had migrated somewhere else — into decisions that happened before a single tag was written and continued long after the site went live.
His book Product Design for the Web starts from that shift and refuses to treat it as a footnote. Building something like Etsy or Twitter or Pinterest — or, honestly, a small app made by two people in a weekend — is not the same as building a website. A product is a thing people come back to, form habits around, get frustrated by, abandon, return to. Designing for that means thinking about behavior, systems, business goals, and what happens on the tenth visit, not just the first. HTML and CSS became table stakes: necessary, assumed, and nowhere near sufficient.
Hunt's aim is to give a working vocabulary for the discipline that grew up in that gap — what a product designer on the web actually does when the deliverable is no longer a static comp but a living, changing experience. It's less a manual of techniques than a way of seeing the whole arc of the work, from the first fuzzy problem to the version that ships and the versions that follow.
The question we’re asking : When the deliverable is a living product rather than a finished page, what does designing for the web actually involve?What we’ll see : How the craft expanded past markup into strategy, research, systems, and the ownership of an entire experience over time.
Table of contents
01Chapter 1 — The job stopped being about the pixels
Hunt's opening move is to separate two things that used to be the same. A website was a document — you made it, you published it, you were mostly done. A product is a relationship. It changes, it responds, it has to keep earning attention on the second visit and the two-hundredth. Etsy in 2007 was not the Etsy of 2012, not because someone redrew the logo but because the product kept absorbing what people did with it and adjusting. That ongoing quality is the whole difference, and it's why the old job description quietly expired.
Once you accept that a product lives over time, the skills that seemed peripheral move to the center. Knowing the syntax of CSS matters far less than knowing why a person would want the thing you're building, how they'll behave once they have it, and what the business needs to be true for the whole enterprise to survive. Hunt is blunt that markup is craft you should have — a designer who can't touch code is at the mercy of translation — but it's the floor, not the ceiling. The interesting decisions are about people and systems, and those decisions don't render in a browser.
02Chapter 2 — Design starts long before anyone opens Photoshop
The part of the work Hunt insists on most is the part that produces nothing visible for a while. Before there's a layout, there's a problem to define, and defining it well is most of the battle. He treats the early stage as research and framing: figuring out who you're building for, what they're actually trying to accomplish, and where the current experience fails them. Skip this and you end up polishing a solution to a problem nobody has — which is how a lot of beautifully executed products quietly die.
He's practical about how you learn this. Talking to people, watching them use things, reading the behavior in whatever data exists — none of it glamorous, all of it the raw material of good decisions. A product designer, in Hunt's account, is comfortable sitting with ambiguity for longer than feels natural, resisting the urge to jump to a screen because a screen feels like progress. The screen is easy. Knowing which screen to make is the hard, valuable part, and it comes from understanding rather than taste.
03Chapter 3 — Building the thing you can actually ship
When Hunt turns to making, he's writing for a world where design and build aren't separate departments handing files back and forth. The product designer sketches, prototypes, and works close enough to code that the thing in their head survives contact with reality. He's a strong advocate for getting to something functional fast — a rough prototype teaches you more in an afternoon than a month of debating static comps, because you can only really judge an interaction by using it.
This is where his insistence on technical fluency pays off. A designer who understands how the product is actually built makes better decisions and fewer impossible ones. You stop asking for things that would take three months when a slightly different version takes three days. You can speak to engineers as collaborators rather than as a vendor lobbing over requirements. Hunt frames code literacy not as a demand that designers become engineers, but as the difference between drawing a picture of a product and helping build one.
04Chapter 4 — The designer as the person who owns the whole experience
Step back from the individual skills and a bigger claim emerges from Hunt's book: the web designer role didn't just gain a few responsibilities, it changed category. What used to be a specialist who executed a defined slice became a generalist who owns an arc — from the fuzzy problem, through research and framing, into building and shipping, and back out into learning and revising. The discipline absorbed strategy, a bit of research, a working grasp of engineering, and an eye on the business, and folded them into one seat.
That's a demanding definition, and Hunt doesn't soften it. The product designer he describes has to hold tensions that used to belong to different people — the user's needs and the company's needs, the ideal design and the buildable one, the pleasure of craft and the discipline of shipping. Nobody hands you the answer where those meet; you're the person expected to find it. The value of the role is precisely that it sits at the intersection rather than in any one corner.
05Conclusion
Randy Hunt built his argument from the ground he'd actually stood on — designing and then leading design at Etsy while the company grew from a curiosity into a marketplace millions of people used. The pattern he saw there wasn't unique to Etsy; it was the same shift playing out across Twitter, Pinterest, Facebook, and countless smaller products. The moment a website became a product, the person designing it had to care about everything the product touched, and the neat old boundary between design and everything-else dissolved.
