Some patterns that I used to do a bunch were you take features that you are kind of geek mode features and bury it down deeper in your UI. And then you watch the behavior, anonymous use statistics or UXR or what have you and get a sense of what those users are doing. Then you can expand that usage from there if you find something interesting. Like you don't have to build stuff except things that respond to concrete demand. So what's one or two examples of real life products that you feel did this?
Read the full transcript here.
Why do organizations get slower as they grow? What can organizations learn from slime molds? What are the advantages of top-down organization versus bottom-up organization, and vice versa? How can organizations encourage serendipity? What use are doorbells in jungles? Why is it so hard for organizations to set a "north star" that is at once plausible, coherent, and good?
Alex Komoroske has over a decade of experience in the tech industry as a product manager focusing on platform- and ecosystem-shaped problems. While at Google, he worked on Chrome's Web Platform PM team, Augmented Reality in Google Maps, and Ambient Computing. He's fascinated by how to navigate the emergent complexity within organizations to achieve great results. You can find some of his public writing at komoroske.com.
Staff
Music
Affiliates