Product design fundamentals for non-designer founders

Executive overview

Most founders ship products that don't work well because they skip empathy — they never truly understand who the user is or what problem they're solving. Design is not how something looks; it is how something works.

The talk covers three layers: product design (what problem, for whom), interaction design (how users achieve goals), and visual design (how to direct attention). Done in sequence, these layers produce products that are both functional and delightful.

Good design is as little design as possible — remove everything that doesn't carry meaning.

What design actually is

• Design = creating things for users that work well and delight them; remove either word and the definition fails
• The biggest misconception: design is how it looks — it is equally how it works
• Form over function is a persistent failure mode, even at great companies (e.g. the notch on iPhone)
• Novelty is the opposite of functionality; delight is the sizzle, but "works well" is the steak
• Empathy is the core skill — you must become genuinely interested in other people's problems
• If there is no real problem, the output is art, not design

Product design: defining the problem

• Start with a crisp problem statement before touching any interface
• Build personas — named, specific fictional users with devices, skill levels, and motivations
• Personas make trade-offs concrete: a grandma on Hotmail has different needs than a power-user with an iPhone
• Write a PRD (product requirement document / spec) listing features with clear descriptions an engineer can act on
• Prioritise every feature: P0 (must-ship), P1 (wouldn't ship without), P2–P3 (if time allows)
• Prioritisation lets you cut scope cleanly when things go wrong — and they will go wrong
• The three variables are always scope, quality, and time; you can only protect two

User research

• Spend time with target users before deciding what to build; their problems will surface naturally
• Personas are a tool for capturing that research in a reusable, decision-making form
• For B2B products, distinguish the executive buyer, the decision-maker, and the frontline worker — their needs differ

Interaction design: making flows work

• The output is a wireframe or prototype — text, calls to action, screen-to-screen flows; colour and fonts can wait
• Computers are fundamentally a conversation; every interaction follows social-psychological rules
• Use direct command language — passive, descriptive copy kills conversion; tell users exactly what to do
• Removing a "confirm password" field can increase signup conversion by ~50%
• Two ways to reduce friction: remove actions entirely, or chop complex actions into wizard steps
• Steal proven design patterns rather than inventing new ones — novelty at the interaction layer confuses users
• Match patterns to modality: a touch swipe pattern makes no sense on a mouse-driven web page

Visual design: directing attention

• Contrast is the primary tool — bold vs. normal weight, colour, size; if everything is bold, nothing is
• The squint test: blur your eyes on a page and your gaze should land on the most important element first
• Closeness groups related elements, telling users what belongs together
• Contrast + closeness produce visual hierarchy — the guide rail that moves users through a page
• Use whitespace and a grid (e.g. Bootstrap) before reaching for lines or boxes
• Only add a box when you need high contrast around a single call to action; too many boxes destroy hierarchy
• Eliminate ornament that carries no meaning — remove colons, borders, gradients that don't add signal
• Minimalism is not aesthetic preference; it forces you to solve the real problem

Feedback loops: testing and support

• Usability testing can start at the wireframe stage — print it out, ask someone unfamiliar to walk through it
• Ask open-ended questions: "What are you looking at? What will you click next?" before writing a line of code
• Customer support is underrated product intelligence — every complaint surfaces a long-tail bug
• Big companies treat users as cattle; as a founder you can fix a bug the same day someone reports it and create a lifelong evangelist
• Aim for 100 people who absolutely love the product, not 1,000 who mildly like it
• The product cycle never ends: research → PRD → wireframe → visual design → usability test → ship → support → repeat