Lecture 17 - How to Design Hardware Products (Hosain Rahman)

Summary

Hosain Rahman explains Jawbone’s approach to designing hardware products, especially products that combine hardware, software, and data. He argues that Jawbone is not simply a hardware company: it aims to create integrated experiences in which the physical device, app, cloud services, and data work together to solve a user problem.

Product vision and system design

Rahman describes Jawbone’s work as combining crafted innovation with engineering that is largely invisible to the user. Its products—including Bluetooth headsets, Jambox wireless speakers, and UP health trackers—are part of a broader vision for connected devices.

He sees a major problem with the Internet of Things: many devices have their own apps but do not work together, leaving users with a confusing experience. Jawbone’s view is that connected products should be organized around the person, not just around individual devices. Wearables could serve as a “context engine,” using information about a person’s activity or state to help other devices respond more appropriately.

To deliver this vision, Jawbone treats hardware, software, and data as equally important. Hardware must be comfortable and reliable enough to wear consistently; software must keep people engaged; and data systems must turn measurements into useful insights.

This creates challenges because hardware development cycles are slower and more constrained than software iteration. Jawbone tries to bring the disciplines together while learning from each: hardware teams should move more quickly where possible, while software teams need to resolve more of the experience before release.

Jawbone’s product-development process

Rahman outlines a flexible, staged process:

1. Exploration: Teams investigate future possibilities through research, tinkering, hackathons, and “Demo Fridays,” where people share work and get feedback. Executives act mainly as sounding boards. A concept may receive further exploration much like an early investment.
2. Validation: Teams test whether the idea addresses a real problem and whether it is scientifically, technically, and commercially plausible. They begin defining the product’s purpose—the “why.”
3. Concepting: The product-experience team develops the experience across industrial design, software, audio, writing, and storytelling. Teams identify key user problems and the product’s “hero experiences,” while considering how it fits into a longer-term roadmap.
4. Planning: Once a project is approved, teams make practical trade-offs involving cost, schedules, battery life, materials, manufacturing, and technical limits.
5. Development and launch: Product managers and engineers coordinate implementation, prototyping, refinement, and release. The company then learns from users and feeds those lessons into the next iteration.

The process is not rigid. Jawbone may fast-track a product, skip stages when uncertainties are already understood, or run parallel technology work to address longer-term obstacles.

Defining the “why” and researching users

A central tool is a clear statement of what user problem the product solves and why the solution matters. Rahman says this helps teams evaluate ideas and make creative decisions without losing focus.

He recommends researching how people behave and what they need, rather than asking directly whether they would buy a specific product or feature. Users may not be able to imagine a new category in advance; the company must form a thesis, then use research to refine and test it.

Jawbone’s Jambox is one example. Rahman says the company saw mobile media becoming increasingly centered on phones and identified a need for portable, high-quality audio that worked across settings. He also viewed speakers as an entry point into the connected home. According to Rahman, wireless speakers grew from 0% of the speaker market when Jambox launched in 2010 to 78% by Christmas 2013. He uses this to illustrate how a product can create demand that users might not have articulated in a focus group.

UP and UP24: from tracking to action

For Jawbone’s health products, Rahman describes the guiding sequence as track, understand, and act:

• Track: Design the hardware, battery, materials, and fit so people will keep wearing it and build a habit.
• Understand: Interpret measurements in context. Raw data—for example, a heart-rate value—does not explain what it means for a particular person.
• Act: Use insights and timely guidance to help users change behavior, such as reminding someone to exercise if their data suggests it improves their sleep.

The system includes sensors, algorithms, a phone app, cloud processing, and third-party integrations. Notifications are treated as a potential tool for behavior change, and experiences may be tailored to different user motivations and needs.

Design details and collaboration

Rahman emphasizes the role of small details in making a product feel distinctive and satisfying. Examples include Jambox’s startup sound, the feel and color of its rubber casing, and the animations and transitions in the UP app. These details can take considerable time to refine, but he sees them as part of the overall product experience.

Because decisions in one area affect the rest of the product, teams must work across functional boundaries. Rahman describes lengthy cross-functional meetings on UP3, where choices about sensor materials affected reliability, sourcing, and signal performance. Jawbone used frequent communication to make trade-offs against overall product goals rather than optimizing each department’s work in isolation.

Key Q&A points

• System thinking: Even a small product should be considered as a system of interacting parts. Startups can begin with a narrow product, but should understand how its components and trade-offs fit together.
• Iteration: Lessons from shipped products can send teams back to earlier stages, but teams can also skip steps when they already understand the problem or solution.
• Product categories: Decisions depend on the category’s use case, pace, and replacement cycle. Phones, tablets, and home devices do not necessarily follow the same upgrade pattern.
• Company growth: Jawbone had about 500 employees and offices across several cities. Rahman identified communication across teams and locations as a continuing challenge.
• Hardware and software practices: Jawbone tried to apply rapid software iteration where possible, while applying hardware’s attention to resolution and quality to software design. Rahman said the company was still developing its own model for combining the disciplines.

Reviews, guides, and tutorials

• Reviews: No product review is provided.
• Guide/tutorial: The lecture serves as a conceptual guide to Jawbone’s hardware-product development process, including product framing, user research, cross-functional design, trade-offs, and iteration. It is not a step-by-step build tutorial.

Main speakers and sources

• Hosain Rahman: Jawbone CEO and founder; primary speaker.
• Sam Altman: Introduces Rahman and asks how Jawbone balances user research with products users might not know to request.
• Audience members: Ask questions during the lecture’s Q&A.