Episode #84: Designing Software as a Cultural Medium with Bob Baxley

Bob Baxley's route into software design began before user interface design was an established field of study. He explored photography in high school, studied film and history in college, spent time making music, and moved into graphic design. At 27, a job at Claris, Apple's software subsidiary, brought him to California and revealed a medium that fit both his engineering instincts and his artistic interests. He has continued designing software for more than three decades.

His view of software as more than a productivity tool crystallized years later. After leaving Pinterest in 2016, he became disillusioned with the technology industry's role in culture and politics. Learning about Silicon Valley's countercultural history helped him reconnect with the idea that personal computing could be a form of media alongside movies, music, and books. That framing explains why he approaches software as an experience capable of expressing ideas, not merely as a machine for transactions or measurement.

What you'll learn

• How film and history shaped Bob's approach to collaborative design and uncertainty

• Why writing a book can make a designer's instincts precise and defensible

• What feedback from Steve Jobs taught him about clarity and user behavior

• Why design becomes powerful only when the wider company treats it as a core value

• How leaders can adapt after leaving a strong organizational culture

Use other disciplines to strengthen design judgment

Film taught Bob two related lessons: storytelling and large-scale creative coordination. A film can involve hundreds or thousands of contributors yet still feel guided by one vision. Software presents a similar challenge because no single person can master every part of a complex product. Design leadership must help many specialists contribute to an experience that feels coherent.

History offered another useful practice. Studying the past requires a person to combine competing narratives, acknowledge uncertainty, and synthesize a point of view without pretending every answer is settled. Bob connects that comfort with possibility to design exploration. A team needs enough conviction to make something and enough openness to test whether another direction could work better.

Writing *Making the Web Work* forced those instincts into a clear system. Bob originally wanted to help engineers apply basic design principles because the supply of dedicated designers could not match the amount of software being built. The process also improved his own craft. Ideas that can remain ambiguous in someone's head must become specific once they are placed on a page, explained, and justified.

Make design a company behavior, not a department

Bob joined Apple in 2006 to lead design for the online store, months before the iPhone was announced. Over six years, his team worked on the ecommerce experience, the Apple Store app, self-checkout in retail stores, handheld point-of-sale concepts, and a real-time floor reporting product. The work exposed him to both digital design and the operational design of Apple retail.

One review with Steve Jobs made the value of decisive, reasoned feedback concrete. Bob's team had placed ratings and reviews behind a tab on a product page. Jobs objected because customers needed to see that important information without another click. The force of the response got attention, but the rationale made it useful. Bob also stresses that reviews with Apple executives improved work because those leaders had strong product judgment and could identify problems quickly.

He describes design at Apple as a business strategy shared across the organization. The company competes by making products people consider better designed and worth a higher margin. That promise creates accountability far beyond the design team. His example is Apple's patented round pizza box, created by cafeteria staff to manage heat and oil more effectively. The lesson is not to imitate Apple's artifacts. It is to make the desired value concrete enough that employees throughout the company treat failure against it as a serious business risk.

Enter a new culture by listening first

Bob moved directly from Apple to Pinterest, leaving one company on Friday and starting at the next on Monday. In retrospect, he believes he needed a break and more time to understand the new environment. Companies may hire leaders from Apple because they want its values, but behaviors that work inside one strong culture do not automatically transfer to another. At Pinterest, he says he brought Apple behaviors into a culture that received them differently.

The practical advice is to separate principles from habits. A new leader should listen, learn how decisions are made, and reinterpret useful values for the organization they have actually joined. This can be difficult when a design leader enters a fast-growing company under pressure to fix urgent problems. Bob still recommends protecting time to observe, even if a full year of orientation is unrealistic. He also learned while scaling Pinterest's design team from roughly 9 or 10 people to 40 in about 16 months that hiring sometimes requires transparent experiments rather than certainty.

For leaders managing their own communication, Bob offers a personal lesson. His pattern recognition, attention to detail, and ability to build mental models help his design work, but colleagues cannot see when new information changes those models. He learned to explain how his thinking evolved so a thoughtful update would not look inconsistent or unreliable.

Listen to Episode #84.