Subscribe to Occasional Observations
Occasional ObservationsWe don't need more founders
Building over founding
Occasional ObservationsThoughts on "How to Build a Car"
Reading through How to Build a Car, a few product-related themes flow through the entire book: • The constant search for advantages. Poring over the newly released rulebooks to find gaps & technicalities to creatively exploit. Examining other domains for cross-over insights. Every team isn’t just racing on the track, the design/engineering teams are racing each other to identify the smallest of levers before the next team. • The car is a system, not merely an object. The interconnectedness of...
Occasional ObservationsMercedes & Microsoft
"Let's put that in the parking lot"
<100 subscribers
Occasional ObservationsWe don't need more founders
Building over founding
Occasional ObservationsThoughts on "How to Build a Car"
Reading through How to Build a Car, a few product-related themes flow through the entire book: • The constant search for advantages. Poring over the newly released rulebooks to find gaps & technicalities to creatively exploit. Examining other domains for cross-over insights. Every team isn’t just racing on the track, the design/engineering teams are racing each other to identify the smallest of levers before the next team. • The car is a system, not merely an object. The interconnectedness of...
Occasional ObservationsMercedes & Microsoft
"Let's put that in the parking lot"
Share Dialog
Share Dialog
Here's a pernicious loop:
A Hot New Thing™️ comes along
Experts™️ tout it as the silver bullet
Teams ask too much of it
Hot New Thing™️ crumples under the weight of unwarranted expectations
Think pieces abound, announcing the death of Hot New Thing™️
Hot New Thing™️ becomes a Cold Dead Failure™️
Design systems. Agile. Design thinking. Design Sprints. MVPs. And so on.
We tend to blame a methodology, externality, or technology rather than examine our own contribution to dysfunction.
[The topic deserves a much larger post, but this will have to suffice for now.]
Header photo by Jorge Salvador on Unsplash
Here's a pernicious loop:
A Hot New Thing™️ comes along
Experts™️ tout it as the silver bullet
Teams ask too much of it
Hot New Thing™️ crumples under the weight of unwarranted expectations
Think pieces abound, announcing the death of Hot New Thing™️
Hot New Thing™️ becomes a Cold Dead Failure™️
Design systems. Agile. Design thinking. Design Sprints. MVPs. And so on.
We tend to blame a methodology, externality, or technology rather than examine our own contribution to dysfunction.
[The topic deserves a much larger post, but this will have to suffice for now.]
Header photo by Jorge Salvador on Unsplash
1 comment
The latest blog post by @trh explores the cycle of excitement and disappointment surrounding new methodologies like design systems and agile practices. It highlights how unwarranted expectations can lead to failure, urging a closer look at our roles in these patterns. Don't miss this insightful analysis!