
GUEST POST from Mike Shipulski
When there’s a big problem, the first step is to define what’s causing it. To do that, based on an understanding of the physics, a sequence of events is proposed and then tested to see if it replicates the problem. In that way, the team must understand the system as it is before the problem can be solved.
Seeing Things as They Are
The same logic applies when it’s time to improve an existing product or service. The first thing to do is to see the system as it is. But seeing things as they are is difficult. We have a tendency to see things as we want them or to see them in ways that make us look good (or smart). Or, we see them in a way that justifies the improvements we already know we want to make.
To battle our biases and see things as they are, we use tools such as block diagrams to define the system as it is. The most important element of the block diagram is clarity. The first revision will be incorrect, but it must be clear and explicit. It must describe things in a way that creates a singular understanding of the system. The best block diagrams can be interpreted only one way. More strongly, if there’s ambiguity or lack of clarity, the thing has not yet risen to the level of a block diagram.
The block diagram evolves as the team converges on a single understanding of things as they are. And with a diagram of things as they are, a solution is readily defined and validated. If when tested the proposed solution makes the problem go away, it’s inferred that the team sees things as they are and the solution takes advantage of that understanding to make the problem go away.
Seeing Things as They May Be
Even whey the solution fixes the problem, the team really doesn’t know if they see things as they are. Really, all they know is they see things as they may be. Sure, the solution makes the problem go away, but it’s impossible to really know if the solution captures the physics of failure. When the system is large and has a lot of moving parts, the team cannot see things as they are, rather, they can only see the system as it may be. This is especially true if the system involves people, as people behave differently based on how they feel and what happened to them yesterday.
There’s inherent uncertainty when working with larger systems and systems that involve people. It’s not insurmountable, but you’ve got to acknowledge that your understanding of the system is less than perfect. If your company is used to solving small problems within small systems, there will be little tolerance for the inherent uncertainty and associated unpredictability (in time) of a solution. To help your company make the transition, replace the language of “seeing things as they are” with “seeing things as they may be.” The same diagnostic process applies, but since the understanding of the system is incomplete or wrong, the proposed solutions cannot not be pre-judged as “this will work” and “that won’t work.” You’ve got to be open to all potential solutions that don’t contradict the system as it may be. And you’ve got to be tolerant of the inherent unpredictability of the effort as a whole.
Seeing Things as They Could Be
To create something that doesn’t yet exist, something does things like never before, something altogether new, you’ve got to stand on top of your understanding of the system and jump off. Whether you see things as they are or as they may be, the new system will be different. It’s not about diagnosing the existing system; it’s about imagining the system as it could be. And there’s a paradox here. The better you understand the existing system, the more difficulty you’ll have imagining the new one. And, the more success the company has had with the system as it is, the more resistance you’ll feel when you try to make the system something it could be.
Seeing things as they could be takes courage – courage to obsolete your best work and courage to divest from success. The first one must be overcome first. Your body creates stress around the notion of making yourself look bad. If you can create something altogether better, why didn’t you do it last time? There’s a hit to the ego around making your best work look like it’s not all that good. But once you get over all that, you’ve earned the right to go to battle with your organization who is afraid to move away from the recipe responsible for all the profits generated over the last decade.
But don’t look at those fears as bad. Rather, look at them as indicators you’re working on something that could make a real difference. Your ego recognizes you’re working on something better and it sends fear into your veins. The organization recognizes you’re working on something that threatens the status quo and it does what it can to make you stop. You’re onto something. Keep going.
Seeing Things as They Can’t Be
This is rarified air. In this domain you must violate first principles. In this domain you’ve got to run experiments that everyone thinks are unreasonable, if not ill-informed. You must do the opposite. If your product is fast, your prototype must be the slowest. If the existing one is the heaviest, you must make the lightest. If your reputation is based on the highest functioning products, the new offering must do far less. If your offering requires trained operators, the new one must prevent operator involvement.
If your most seasoned Principal Engineer thinks it’s a good idea, you’re doing it wrong. You’ve got to propose an idea that makes the most experienced people throw something at you. You’ve got to suggest something so crazy they start foaming at the mouth. Your concepts must rip out their fillings. Where “seeing things as they could be” creates some organizational stress, “seeing things as they can’t be” creates earthquakes. If you’re not prepared to be fired, this is not the domain for you.
All four of these domains are valuable and have merit. And we need them all. If there’s one message it’s be clear which domain you’re working in. And if there’s a second message it’s explain to company leadership which domain you’re working in and set expectations on the level of uncertainty and unpredictability of that domain.
Image credits: Pexels
Sign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.






After a week of torrid voting and much passionate support, along with a lot of gut-wrenching consideration and jostling during the judging round, I am proud to announce your Top 40 Innovation Bloggers of 2024:
Greg Satell is a popular speaker and consultant. His first book, 
Mike Shipulski brings together people, culture, and tools to change engineering behavior. He writes daily on Twitter as 
A twenty-five year Procter & Gamble veteran, Pete has spent the last 8+ years applying insights from psychology and behavioral science to innovation, product design, and brand communication. He spent 17 years as a serial innovator, creating novel products, perfume delivery systems, cleaning technologies, devices and many other consumer-centric innovations, resulting in well over 100 granted or published patents. Find him at pete.mindmatters@gmail.com






Dainora (a.k.a. Dee) creates customer-centric content at Viima. Viima is the most widely used and highest rated innovation management software in the world. Passionate about environmental issues, Dee writes about sustainable innovation hoping to save the world – one article at the time.
Soren Kaplan is the bestselling and award-winning author of Leapfrogging and The Invisible Advantage, an affiliated professor at USC’s Center for Effective Organizations, a former corporate executive, and a co-founder of
Diana heads marketing at 
Jesse Nieminen is the Co-founder and Chairman at 

Arlen Meyers, MD, MBA is an emeritus professor at the University of Colorado School of Medicine, an instructor at the University of Colorado-Denver Business School and cofounding President and CEO of the Society of Physician Entrepreneurs at 
Leo is the founder of
Rachel Audige is an Innovation Architect who helps organisations embed inventive thinking as well as a certified Systematic Inventive Thinking Facilitator, based in Melbourne.
Art Inteligencia is the lead futurist at Inteligencia Ltd. He is passionate about content creation and thinks about it as more science than art. Art travels the world at the speed of light, over mountains and under oceans. His favorite numbers are one and zero.
Phil McKinney is the Author of “Beyond The Obvious”, Host of the Killer Innovations Podcast and Syndicated Radio Show, a Keynote Speaker, President & CEO CableLabs and an Innovation Mentor and Coach.
Dr. Ralph-Christian Ohr has extensive experience in product/innovation management for international technology-based companies. His particular interest is targeted at the intersection of organizational and human innovation capabilities. You can follow him on Twitter 
Dr. Dean Anderson and Dr. Linda Ackerman Anderson lead 

Scott Anthony is a strategic advisor, writer and speaker on topics of growth and innovation. He has been based in Singapore since 2010, and currently serves at the Managing Director of Innosight’s Asia-Pacific operations.
Paul Hobcraft runs 
Chateau G Pato is a senior futurist at Inteligencia Ltd. She is passionate about content creation and thinks about it as more science than art. Chateau travels the world at the speed of light, over mountains and under oceans. Her favorite numbers are one and zero.
As an experience architect, Alain helps leaders craft customer, employee and shareholder experiences for profit, reinvention and transformation. He does this through his personal consultancy Alain Thys & Co as well as the transformative venture studio 





Happy Holidays!





