At a glance
- Age
- 62
- Born
- September 25, 1964
- From
- San Francisco, California, United States
- Nationality
- United States
Biography
If you have come across him through a keynote clip or a line about business serving more than shareholders, the two ideas attached to his name are software as a service and stakeholder capitalism. He is an American businessperson and chief executive, born in San Francisco in September 1964, and his reputation rests less on a single product than on a way of running things: treating scale as something you design for from the beginning rather than something that happens to you if you get lucky.
The material that circulates from him — memos, interviews, keynote talks — works as instruction more than promotion. He has been consistent about documenting what did not work, framing failed attempts as experiments that produced lessons rather than mistakes to be buried. In the middle stretch of his career the work was mostly about turning prototypes into platforms, which meant decisions about architecture, about company culture, and about where the money went. Those decisions are the reason his name gets cited in business teaching at all. He also treated regulatory and ethical questions as part of the design problem rather than an external nuisance, which is where the stakeholder capitalism association comes from.
Later on the emphasis shifted towards mentorship and building institutions that outlast any one release cycle. What survives in the record — talks, correspondence, design notes — tends to show method where observers assumed instinct. That is the useful part for anyone arriving from a short clip: the appeal of his material is that the standard he describes is meant to be repeatable, not personal.
The material that circulates from him — memos, interviews, keynote talks — works as instruction more than promotion. He has been consistent about documenting what did not work, framing failed attempts as experiments that produced lessons rather than mistakes to be buried. In the middle stretch of his career the work was mostly about turning prototypes into platforms, which meant decisions about architecture, about company culture, and about where the money went. Those decisions are the reason his name gets cited in business teaching at all. He also treated regulatory and ethical questions as part of the design problem rather than an external nuisance, which is where the stakeholder capitalism association comes from.
Later on the emphasis shifted towards mentorship and building institutions that outlast any one release cycle. What survives in the record — talks, correspondence, design notes — tends to show method where observers assumed instinct. That is the useful part for anyone arriving from a short clip: the appeal of his material is that the standard he describes is meant to be repeatable, not personal.
Known For
software as a service and stakeholder capitalism.