WhoBuilt

Design for Startups

Sep 19, 2018· 1 h 7 min· 173K views·Watch on YouTube

Speaker

Garry Tan, a self-taught designer, former Y Combinator partner and Posterous founder, explains startup product design at Y Combinator’s Startup School.

Design starts with users

Tan defines design as making things that work well and delight users, and says it belongs alongside product management, engineering, and customer support. He urges founders to understand users’ needs before choosing a solution, using empathy and clear problem statements to keep the work focused.

Turn user needs into a product plan

Tan combines product design with product management: identify the problem, the people who have it, possible solutions, and their priorities. Using Posterous as an example, he describes personas such as a less tech-savvy grandmother and features like posting by email without an account. He recommends user research, a written requirements document, and clear priorities so teams can manage scope and ship.

Make interactions clear and easy

Tan says interaction design translates user goals into flows, wireframes, and clear instructions. He recommends direct calls to action, removing unnecessary steps such as password confirmation, and breaking complex tasks into smaller steps. Familiar patterns can help users move quickly, as long as they fit the device and context.

Use visual hierarchy to guide attention

Tan describes visual design as showing users what matters through contrast, grouping, and hierarchy. He recommends removing decoration that adds no meaning, using grids and spacing to organize content, and applying the squint test to see where attention goes. Too many boxes or lines can obscure the next step.

Test, listen, and repeat

Tan recommends usability testing with people who have not seen a design before, asking what they notice and what they would do next. He also treats customer support as a source of product feedback: recurring small issues can add up to a broken experience. Product work continues in repeated cycles of research, design, testing, and improvement.

Takeaways

  • Talk to users early and write down the specific problem you plan to solve.
  • Use personas to clarify how different users’ needs and technical comfort vary.
  • Prioritize features so the team can cut scope and still ship on time.
  • Remove unnecessary steps and use familiar interaction patterns where they fit.
  • Test designs with new users and treat support requests as product feedback.

Mentioned in this talk

Search inside this talk

What was claimed 7

Related talks