Elon Musk tweeted this yesterday: “Please note that Twitter will do lots of dumb things in coming months. We will keep what works & change what doesn't.”
I celebrate the idea that trying to improve means that not everything we try will work out as we would predict.
It's better to admit a mistake, adjust, and move forward instead of being stubborn.
“Keep what works & change what doesn't,” as Elon put it.
Listen to Mark read the post (subscribe to Lean Blog Audio):
That said, should we aim to be:
1) Planning enough so we have a well-thought-out hypothesis about what we expect to work (being prepared to accept we might be wrong)
2) Just randomly trying “dumb things” (a.k.a. throwing spaghetti against the wall to see what sticks)?
I'd argue that we should be closer to the first of those two options.
How do we encourage a culture of continuous improvement without it becoming chaotic? Does anybody feel safe to push back on the boss when they suggest a “dumb thing” that everybody else would predict to be a bad idea?
What's the risk of trying a “dumb thing?” What's the worst that could happen? Those are important questions to ask in different situations. When do we go ahead and just test the “dumb idea” and when do we pause to think about it more, without getting into analysis paralysis? It's all situational, right?
What happens if the ability to admit a mistake becomes an excuse for not properly planning out our improvement experiments?
If we think in terms of Plan-Do-Study-Adjust cycles, does our ability to “Study and Adjust” mean that we don't need to Plan before we Do?
Post a comment below or join the discussion on LinkedIn, where I made a similar post.
What do you think? Please scroll down (or click) to post a comment. Or please share the post with your thoughts on LinkedIn. Don't want to miss a post or podcast? Subscribe to get notified about posts via email daily or weekly.