Welcome to Musings—
A space where I cut through the noise and get to the heart of effective leadership and strategy execution. Here, I share hard-earned insights, practical frameworks, and candid reflections to help you navigate the complexities of leading teams and driving change.
Each post is designed to be a quick, impactful read—something you can digest between meetings and apply immediately. Whether you're refining your leadership approach, tackling execution challenges, or seeking to foster a more cohesive team, you'll find valuable takeaways here.
Dive in, reflect, and let's grow together.
“We Tried That Before and It Didn’t Work”
“We tried that before and it didn’t work.”
Man, I’ve heard that phrase a lot in my life. And truth be told, I’ve spoken it more than I care to admit.
But when something fails once in the past (or even more than once) should it be doomed forever?
I was once lucky enough to hear futurist Bob Johansen speak, and he said something that really stuck with me:
“Almost nothing that happens in the future is new; it’s almost always something that has been tried and failed in the past.”
The Power of a Little Naïveté
Most of us are experts in something. Our expertise and experience are usually significant advantages that allow us to deal effectively with complex problems and situations. But they can occasionally be Achilles’ heels when they breed the type of overconfidence that causes us to overlook simple solutions in favor of more complex and costly solutions. Injecting a little naiveté into some problem solving sessions can spur new thinking that results in more effective and efficient solutions.
In my experience, experts tend to skip right by the simple solutions to most problems. Groups of experts working to solve a problem are even more likely to head directly to the more complex solutions.
Are Retail Analytics Like 24-Hour News Networks?
We have immediate access to loads of data in today’s world, but just because we can access lots of data in real time doesn’t mean we should access our data in real time. In fact, accessing and reporting on the numbers too quickly can often lead to distractions, false conclusions, premature reactions and bad decisions.
I remember a time I switched on CNN and saw — played out in all their glory on national TV — the types of issues that can occur with reporting too early on available data.
CNN reporters “monitoring video” from a local TV station saw Coast Guard vessels in the Potomac River apparently trying to keep another vessel from passing. They then monitored the Coast Guard radio and heard someone say, “You’re approaching a Coast Guard security zone. If you don’t stop your vessel, you will be fired upon. Stop your vessel immediately.” And, for my favorite part of the story, they made the decision to go on air when they heard someone say “bang, bang, bang, bang” and “we have expended 10 rounds.” They didn’t hear actual gun shots, mind you, they heard someone say “bang.” Could this be a case of someone wanting the data to say something it isn’t really saying?