product orgs

A good product team needs a mix of design, tech, and business; a mix of genders, creeds, and backgrounds; a mix of industry experience and product management experience; a mix of skills, from the visionary to the detail-oriented, from the data-hungry to the user-research fanatics. This level of diversity not only is the best chance you have of representing your audience, but also ensures the best experience is brought to any product challenge the team will face, and is the best defense against any one individual’s confirmation bias.

– from Product Leadership

transit scheduling

As a result, the scheduler only ever adds run-time to routes and never subtracts it, which costs the agency more money to run the same service. To make matters worse, passengers become upset because operators drag (drive unnecessarily slow) and hold (wait unnecessarily) at timepoints. This cycle has been going on for decades.

Andy Metz, in The Vicious Cycle of Timepoint Adherence


A fallacy is to have designers obsessed with the products and services they work on. Product and service features are just manifestations of a users’ relationship with a company. Instead, designers should be obsessed with their entire user experience. So, organize teams by types of users.

– excerpt from Org Design for Design Orgs