Category Archives: Design

Voting Closed – Top 40 Innovation Bloggers of 2024

Vote for Top 40 Innovation BloggersHappy Holidays!

For more than a decade I’ve devoted myself to making innovation insights accessible for the greater good, because I truly believe that the better our organizations get at delivering value to their stakeholders the less waste of natural resources and human resources there will be.

As a result, we are eternally grateful to all of you out there who take the time to create and share great innovation articles, presentations, white papers, and videos with Braden Kelley and the Human-Centered Change and Innovation team. As a small thank you to those of you who follow along, we like to make a list of the Top 40 Innovation Bloggers available each year!

Our lists from the ten previous years have been tremendously popular, including:

Top 40 Innovation Bloggers of 2015
Top 40 Innovation Bloggers of 2016
Top 40 Innovation Bloggers of 2017
Top 40 Innovation Bloggers of 2018
Top 40 Innovation Bloggers of 2019
Top 40 Innovation Bloggers of 2020
Top 40 Innovation Bloggers of 2021
Top 40 Innovation Bloggers of 2022
Top 40 Innovation Bloggers of 2023

Do you just have someone that you like to read that writes about innovation, or some of the important adjacencies – trends, consumer psychology, change, leadership, strategy, behavioral economics, collaboration, or design thinking?

Human-Centered Change and Innovation is now looking to recognize the Top 40 Innovation Bloggers of 2024.

It is time to vote and help us narrow things down.

The deadline for submitting votes is December 31, 2024 at midnight GMT.

Build a Common Language of Innovation on your team

The ranking will be done by me with influence from votes and nominations. The quality and quantity of contributions to this web site by an author will be a BIG contributing factor (through the end of the voting period).

You can vote in any of these three ways (and each earns points for them, so please feel free to vote all three ways):

  1. Sending us the name of the blogger by @reply on twitter to @innovate
  2. Adding the name of the blogger as a comment to this article’s posting on Facebook
  3. Adding the name of the blogger as a comment to this article’s posting on our Linkedin Page (Be sure and follow us)

The official Top 40 Innovation Bloggers of 2024 will then be announced here in early January 2025.

Here are the people who received nominations this year along with some carryover recommendations (in alphabetical order):

Adi Gaskell – @adigaskell
Alain Thys
Alex Goryachev
Andy Heikkila – @AndyO_TheHammer
Annette Franz
Arlen Meyers – @sopeofficial
Art Inteligencia
Ayelet Baron
Braden Kelley – @innovate
Brian Miller
Bruce Fairley
Chad McAllister – @ChadMcAllister
Chateau G Pato
Chris Beswick
Chris Rollins
Dr. Detlef Reis
Dainora Jociute
Dan Blacharski – @Dan_Blacharski
Daniel Burrus – @DanielBurrus
Daniel Lock
David Burkus
Dean and Linda Anderson
Dennis Stauffer
Diana Porumboiu
Douglas Ferguson
Drew Boyd – @DrewBoyd
Frank Mattes – @FrankMattes
Geoffrey A Moore
Gregg Fraley – @greggfraley
Greg Satell – @Digitaltonto
Helen Yu
Howard Tiersky
Janet Sernack – @JanetSernack
Jeffrey Baumgartner – @creativejeffrey
Jeff Freedman – @SmallArmyAgency
Jeffrey Phillips – @ovoinnovation
Jesse Nieminen – @nieminenjesse
John Bessant
Jorge Barba – @JorgeBarba
Julian Birkinshaw – @JBirkinshaw
Julie Anixter – @julieanixter
Kate Hammer – @Kate_Hammer
Kevin McFarthing – @InnovationFixer
Leo Chan
Lou Killeffer – @LKilleffer
Manuel Berdoy

Accelerate your change and transformation success

Mari Anixter- @MariAnixter
Maria Paula Oliveira – @mpaulaoliveira
Matthew E May – @MatthewEMay
Michael Graber – @SouthernGrowth
Mike Brown – @Brainzooming
Mike Shipulski – @MikeShipulski
Mukesh Gupta
Nick Jain
Nick Partridge – @KnewNewNeu
Nicolas Bry – @NicoBry
Nicholas Longrich
Norbert Majerus and George Taninecz
Pamela Soin
Patricia Salamone
Paul Hobcraft – @Paul4innovating
Paul Sloane – @paulsloane
Pete Foley – @foley_pete
Rachel Audige
Ralph Christian Ohr – @ralph_ohr
Randy Pennington
Richard Haasnoot – @Innovate2Grow
Robert B Tucker – @RobertBTucker
Robyn Bolton – @rm_bolton
Saul Kaplan – @skap5
Shep Hyken – @hyken
Shilpi Kumar
Scott Anthony – @ScottDAnthony
Scott Bowden – @scottbowden51
Shelly Greenway – @ChiefDistiller
Soren Kaplan – @SorenKaplan
Stefan Lindegaard – @Lindegaard
Stephen Shapiro – @stephenshapiro
Steve Blank
Steven Forth – @StevenForth
Tamara Kleinberg – @LaunchStreet
Teresa Spangler – @composerspang
Tom Koulopoulos – @TKspeaks
Tullio Siragusa
Yoram Solomon – @yoram

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

We’re curious to see who you think is worth reading!

Nominations Closed – Top 40 Innovation Bloggers of 2024

Nominations Open for the Top 40 Innovation Bloggers of 2024Human-Centered Change and Innovation loves making innovation insights accessible for the greater good, because we truly believe that the better our organizations get at delivering value to their stakeholders the less waste of natural resources and human resources there will be.

As a result, we are eternally grateful to all of you out there who take the time to create and share great innovation articles, presentations, white papers, and videos with Braden Kelley and the Human-Centered Change and Innovation team. As a small thank you to those of you who follow along, we like to make a list of the Top 40 Innovation Bloggers available each year!

Our lists from the ten previous years have been tremendously popular, including:

Top 40 Innovation Bloggers of 2015
Top 40 Innovation Bloggers of 2016
Top 40 Innovation Bloggers of 2017
Top 40 Innovation Bloggers of 2018
Top 40 Innovation Bloggers of 2019
Top 40 Innovation Bloggers of 2020
Top 40 Innovation Bloggers of 2021
Top 40 Innovation Bloggers of 2022
Top 40 Innovation Bloggers of 2023

Do you just have someone that you like to read that writes about innovation, or some of the important adjacencies – trends, consumer psychology, change, leadership, strategy, behavioral economics, collaboration, or design thinking?

Human-Centered Change and Innovation is now looking for the Top 40 Innovation Bloggers of 2024.

The deadline for submitting nominations is December 24, 2024 at midnight GMT.

You can submit a nomination either of these two ways:

  1. Sending us the name of the blogger and the url of their blog by @reply on twitter to @innovate
  2. Sending the name of the blogger and the url of their blog and your e-mail address using our contact form

(Note: HUGE bonus points for being a contributing author)

So, think about who you like to read and let us know by midnight GMT on December 24, 2024.

We will then compile a voting list of all the nominations, and publish it on December 25, 2024.

Voting will then be open from December 25, 2024 – January 1, 2025 via comments and twitter @replies to @innovate.

The ranking will be done by me with influence from votes and nominations. The quality and quantity of contributions by an author to this web site will be a contributing factor.

Contact me with writing samples if you’d like to publish your articles on our platform!

The official Top 40 Innovation Bloggers of 2024 will then be announced on here in early January 2025.

We’re curious to see who you think is worth reading!

SPECIAL BONUS: From now until December 31, 2024 you can save 30% OFF on my latest best-selling book Charting Change on either the eBook (immediate download) or the hardcover (free shipping worldwide) when using code HOL30.

Support this blog by getting your copy of Charting Change

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

Make the Planet and Your Bottom Line Smile

Make the Planet and Your Bottom Line Smile

GUEST POST from Mike Shipulski

What if the most profitable thing you could do was work that reduced the rise in the earth’s temperature? What if it was most profitable to reduce CO2 emissions, improve water quality or generate renewable energy? Or what if it was most profitable to do work that indirectly made the planet smile?

What if while your competitors greenwashed their products and you radically reduced the environmental impacts of yours? And what if the market would pay more for your greener product? And what if your competitors saw this and disregarded the early warning signs of their demise? This is what I call a compete-with-no-one condition. This is where your competitors eat each other’s ankles in a race to the bottom while you raise prices and sell more on a different line of goodness – environmental goodness. This is where you compete against no one because you’re the only one with products that make the planet smile.

The problem with an environmentally-centric, compete-with-no-one approach is you have to put yourself out there and design and commercialize new products based on this “unproven” goodness. In a world of profits through cost, quality and speed, you’ve got to choose profits through reduced CO2, improved water quality and renewable energy. Why would anyone pay more for a more environmentally responsible product when its price is higher than the ones that work well and pollute just as much as they did last year?

When the Toyota Prius hybrid first arrived on the market, it cost more than traditional cars and its performance was nothing special. Yet it sold. Yes, it had radically improved fuel economy, but the fuel savings didn’t justify the higher price, yet it sold. Competitors advertised that the Prius hybrid didn’t make financial sense, yet it sold. With the Prius hybrid, Toyota took an environmentally-centric, compete-with-no-one approach. They made little on each vehicle or even lost money, but they did it anyway. They did the most important thing. They started.

The Toyota Prius hybrid wasn’t a logical purchase, it was an emotional one. People bought them to make a statement about themselves – I drive a funny-shaped car that gets great gas mileage, I’m environmentally responsible, and I want you to know that. And as other companies scoffed, Toyota created a new category and owned the whole thing.

And, slowly, as Toyota improved the technology and reduced their costs, the price of the Prius dropped and they sold more. And then all the other manufacturers jumped into the race and tried to catch up. And while everyone else cut their teeth on high volume manufacturing a hybrid vehicle, Toyota accelerated.

Below is a chart of hybrid electric vehicles (hev) sold in the US from 2000 to 2017. Each color represents a different model and the Toyota Prius hybrid is represented by the tall blue segment of each year’s stacked bar. In 2000, Toyota sold 5,562 Prius hybrids (60% of all hevs). In 2005, they sold 107,897 Prius hybrids, 17,989 Highlander hybrids and 20,674 Lexus hybrids for a total of 209,711 hybrids (69% of all hevs). In 2007, they sold 181,221 Prius and five other hybrid models for a total of 228,593 (65% of all hevs). In 2017, sold 15 hybrid models and the nearest competitor sold four models. The reduction from 2008 to 2011 is due to reduced gas prices. (Here’s a link to the chart.)

United States Hybrid Electric Vehicle Sales

The success of the Prius vehicle set off the battery wars which set the stage for the plug-in hybrids (larger batteries) and all-electric vehicles (still larger batteries). At the start, the Prius didn’t make sense in a race-to-the-bottom way, but it made sense to people that wanted to make the planet smile. It cost more, and it sold. And that was enough for Toyota to make profits with a more environmentally friendly product. No, Prius didn’t save the planet, but it showed companies that it’s possible to make profits while making the planet smile (a bit). And it made it safe for companies to pursue the next generation of environmentally-friendly vehicles.

The only way to guarantee you won’t make more profits with environmentally responsible products is to believe you won’t. And that may be okay unless one of your companies believes it is possible.

Here’s a thought experiment. Put yourself ten years into the future. There is more CO2 in the atmosphere, the earth is warmer, sea levels are higher, water is more polluted and renewable energy is far cheaper. Are your sales higher if your product creates more CO2, or less? Are your sales higher if your product heats the earth, or cools it? Are your sales higher if your product pollutes water, or makes it cleaner? Are your sales higher because you bet against renewable energy, or because you embraced it? Are your sales higher because you made the planet frown, or smile?

Now, with your new perspective, bring yourself back to the present and do what it takes to increase sales ten years from now. Your future self, your children, their children, and the planet will thank you.

Image credits: Google Gemini

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Success is a Hardship Too

Success is a Hardship Too

GUEST POST from Mike Shipulski

Everything has a half-life, but we don’t behave that way. Especially when it comes to success. The thinking goes – if it was successful last time, it will be successful next time. So, do it again. And again. It is an efficient strategy – the heavy resources to bring it to life have already been spent. And it is predictable – the same customers, the same value proposition, the same supply base, the same distribution channel, and the same technology. And it is dangerous.

Success is successful right up until it isn’t. It will go away. But it will take time. A successful product line will not fall off the face of the earth overnight. It will deliver profits year-over-year and your company will come to expect them. And your company will get hooked on the lifestyle enabled by those profits. And because of the addiction, when they start to drop off the company will do whatever it takes to convince itself all is well. No need to change. If anything, it is time to double-down on the successful formula.

Here’s a rule: When your successful recipe no longer brings success, it’s not time to double-down.

Success’ decline will be slow, so you have time. But creating a new recipe takes a long time, so it is time to declare that the decline has already started. And it is time to learn how to start work on the new recipe.

Hardship 1 – Allocate resources differently. The whole company wants to spend resources on the same old recipes, even when told not to. It is time to create a funding stream that is independent of the normal yearly planning cycle. Simply put, the people at the top have to reallocate a part of the operating budget to projects that will create the next successful platform.

Hardship 2 – Work differently. The company is used to polishing the old products and they don’t know how to create new ones. You need to hire someone who can partner with outside companies (likely startups), build internal teams with a healthy disrespect for previous success, create mechanisms to support those teams and teach them how to work in domains of high uncertainty.

Hardship 3 – See value differently. How do you provide value today? How will you provide value when you cannot do it that way? What is your business model? Are you sure that’s your business model? Which elements of your business model are immature? Are you sure? What is the next logical evolution of how you go about your business? Hire someone to help you answer those questions and create projects to bring the solutions to life.

Hardship 4 – Measure differently. When there is no customer, no technology and no product, there is no revenue. You must learn how to measure the value of the work (and the progress) with something other than revenue. Good luck with that.

Hardship 5 – Compensate differently. People that create something from nothing want different compensation than people that do continuous improvement. And you want to move quickly, violate the status quo, push through constraints and create whole new markets. Figure out the compensation schemes that give them what they want and helps them deliver what you want.

This work is hard, but it’s not impossible. But your company doesn’t have all the pieces to make it happen. Don’t be afraid to look outside your company for help and partnership.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Sustainability Requires Doing Less Not More

GUEST POST from Mike Shipulski

If you use fewer natural resources, your product costs less.

If you use recycled materials, your product costs less.

If you use less electricity, your product costs less.

If you use less water to make your product, your product costs less.

If you use less fuel to ship your product, your product costs less.

If you make your product lighter, your product costs less.

If you use less packaging, your product costs less.

If you don’t want to be environmentally responsible because you think it’s right, at least do it to be more profitable.

Image credit: Pexels

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Don’t Wait for the Wheels to Fall Off

Don't Wait for the Wheels to Fall Off

GUEST POST from Mike Shipulski

When your most important product development project is a year behind schedule (and the schedule has been revved three times), who would you call to get the project back on track?

When the project’s unrealistic cost constraints wall of the design space where the solution resides, who would you call to open up the higher-cost design space?

When the project team has tried and failed to figure out the root cause of the problem, who would you call to get to the bottom of it?

And when you bring in the regular experts and they, too, try and fail to fix the problem, who would you call to get to the bottom of getting to the bottom of it?

When marketing won’t relax the specification and engineering doesn’t know how to meet it, who would you call to end the sword fight?

When engineering requires geometry that can only be made by a process that manufacturing doesn’t like and neither side will give ground, who would you call to converge on a solution?

When all your best practices haven’t worked, who would you call to invent a novel practice to right the ship?

When the wheels fall off, you need to know who to call.

If you have someone to call, don’t wait until the wheels fall off to call them. And if you have no one to call, call me.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

28 Things I Learned the Hard Way

28 Things I Learned the Hard Way

GUEST POST from Mike Shipulski

  1. If you want to have an IoT (Internet of Things) program, you’ve got to connect your products.
  2. If you want to build trust, give without getting.
  3. If you need someone with experience in manufacturing automation, hire a pro.
  4. If the engineering team wants to spend a year playing with a new technology, before the bell rings for recess ask them what solution they’ll provide and then go ask customers how much they’ll pay and how many they’ll buy.
  5. If you don’t have the resources, you don’t have a project.
  6. If you know how it will turn out, let someone else do it.
  7. If you want to make a friend, help them.
  8. If your products are not connected, you may think you have an IoT program, but you have something else.
  9. If you don’t have trust, you have just what you earned.
  10. If you hire a pro in manufacturing automation, listen to them.
  11. If Marketing has an optimistic sales forecast for the yet-to-be-launched product, go ask customers how much they’ll pay and how many they’ll buy.
  12. If you don’t have a project manager, you don’t have a project.
  13. If you know how it will turn out, teach someone else how to do it.
  14. If a friend needs help, help them.
  15. If you want to connect your products at a rate faster than you sell them, connect the products you’ve already sold.
  16. If you haven’t started building trust, you started too late.
  17. If you want to pull in the delivery date for your new manufacturing automation, instead, tell your customers you’ve pushed out the launch date.
  18. If the VP knows it’s a great idea, go ask customers how much they’ll pay and how many they’ll buy.
  19. If you can’t commercialize, you don’t have a project.
  20. If you know how it will turn out, do something else.
  21. If a friend asks you twice for help, drop what you’re doing and help them immediately.
  22. If you can’t figure out how to make money with IoT, it’s because you’re focusing on how to make money at the expense of delivering value to customers.
  23. If you don’t have trust, you don’t have much.
  24. If you don’t like extreme lead times and exorbitant capital costs, manufacturing automation is not for you.
  25. If the management team doesn’t like the idea, go ask customers how much they’ll pay and how many they’ll buy.
  26. If you’re not willing to finish a project, you shouldn’t be willing to start.
  27. If you know how it will turn out, it’s not innovation.
  28. If you see a friend that needs help, help them ask you for help.

Image credit: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

The Hidden Cost of Waiting

The Hidden Cost of Waiting

GUEST POST from Mike Shipulski

If you want to do a task, but you don’t have what you need, that’s waiting for a support resource. If you need a tool, but you don’t have it, you wait for a tool. If you need someone to do the task, but you don’t have anyone, you wait for people. If you need some information to make a decision, but you don’t have it, you wait for information.

If a tool is expensive, usually you have to wait for it. The thinking goes like this – the tool is expensive, so let’s share the cost over too many projects and too many teams. Sure, less work will get done, but when we run the numbers, the tool will look less expensive because it’s used by many people. If you see a long line of people (waiting) or a signup list (people waiting at their desks), what they are waiting for is usually an expensive tool or resource. In that way, to find the cause of waiting, stand at the front of the line and look around. What you see is the cause of the waiting.

If the tool isn’t expensive, buy another one and reduce the waiting. If the tool is expensive, calculate the cost of delay. Cost of delay is commonly used with product development projects. If the project is delayed by a month, the incremental revenue from the product launch is also delayed by a month. That incremental revenue is the cost of delaying the project by a month. When the cost of delay is larger than the cost of an expensive tool, it makes sense to buy another expensive tool. But, to purchase that expensive tool requires multiple levels of approvals. So, the waiting caused by the tool results in waiting for approval for the new tool. I guess there’s a cost of delay for the approval process, but let’s not go there.

Most companies have more projects than people, and that’s why projects wait. And when projects wait, projects are late. Adding people is like getting another expensive tool. They are spread over too many projects, and too little gets done. And like with expensive tools, getting more people doesn’t come easy. New hires can be justified (more waiting in the approval queue), but that takes time to find them, hire them, and train them. Hiring temporary people is a good option, though that can seem too expensive (higher hourly rate), it requires approval, and it takes time to train them. Moving people from one project to another is often the best way because it’s quick and the training requirement is less. But, when one project gains a person, another project loses one. And that’s often the rub.

When it’s time to make an important decision and the team has to wait for missing information, the project waits. And when projects wait, projects are late. It’s difficult to see the waiting caused by missing or un-communicated information, but it can be done. The easiest to see when the information itself is a project deliverable. If a milestone review requires a formal presentation of the information, the review cannot be held without it. The delay of the milestone review (waiting) is objective evidence of missing information.

Information-based waiting is relatively easy to see when the missing information violates a precedent for decision making. For example, if the decision is always made with a defined set of data or information, and that information is missing, the precedent is violated and everyone knows the decision cannot be made. In this case, everyone’s clear why the decision cannot be made, everyone’s clear on what information is missing, and everyone’s clear on who dropped the ball.

It’s most difficult to recognize information-based waiting when the decision is new or different and requires judgment because there’s no requirement for the data and there’s no precedent to fall back on. If the information was formally requested and linked to the decision, it’s clear the information is missing and the decision will be delayed. But if it’s a new situation and there’s no agreement on what information is required for the decision, it’s almost impossible to discern if the information is missing. In this situation, it comes down to trust in the decision-maker. If you trust the decision-maker and they say there’s information missing, then there’s information missing. If you trust the decision-maker and they say there’s no information missing, they should make the decision. But if you don’t trust the decision-maker, then all bets are off.

In general, waiting is bad. And it’s helpful if you can recognize when projects are waiting. Waiting is especially bad went the delayed task is on the critical path because when the project is waiting on a task that’s on the critical path, there’s a day-for-day slip in the completion date. Hint: it’s important to know which tasks and decisions are on the critical path.

Image credit: Pexels

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.

Errors You May Be Making in Your Customer Experience

Errors You May Be Making in Your Customer Experience

GUEST POST from Howard Tiersky

Maintaining a website or mobile experience with a high degree of usability is essential to maximize business outcomes, and people who are frustrated often take for granted how easy it is in the digital world to simply click over to a competitor. Even worse are cases where determined customers simply cannot figure out how to proceed to complete a transaction, or otherwise achieve their goals.

At FROM, we regularly conduct both in person and online usability tests for our clients to observe “real” users engaging with their digital experience. This gives us enormous insight into where users are encountering frustration, confusion, or other difficulties, and while we are huge believers in robust usability testing as a tool to identify and prioritize which aspects of a digital touch point should be optimized (and really, it’s not terribly time-consuming or expensive), there is a little-known trick that can start to identify many problems. While not as comprehensive as user testing, it’s generally much faster, and therefore, a great place to start!

What is that place? The server’s error logs.

While it may not sound super sexy, your error logs contain a treasure trove of data.

First, the server will typically log if a page doesn’t load properly, errors occur, or if transactions fail to complete. Naturally, usability is hampered if your customers are receiving errors because the system not functioning properly, and yet it’s amazing how often server logs don’t get looked at. And since error logs can generally be viewed by browser and device, it’s not uncommon to find that a new version of Chrome or Edge is causing errors that previously didn’t exist, so this is something that need regular attention. In addition, many systems rely on external cloud services, increasing the points of failure. By monitoring server errors, you can make sure you are aware if your site is “breaking,” a simple but often overlooked part of managing an effective digital experience.

Second, we have errors of user validation, i.e., a user enters an invalid email or phone number, tries to complete a transaction without checking the “terms and conditions” acceptance box, etc. Now, on the one hand, you might say “That’s not my fault, my site worked. It was the user made a mistake!” Bzzzzt. Wrong answer. Especially if there are a lot of these types of errors, or if the number suddenly spikes.

It’s our job to design a solution that makes it unlikely that users will make errors. If they’re frequently overlooking something, or misunderstanding what they are meant to do, it’s a sign we need to look at that screen or field and consider how to redesign it to reduce confusion. It might be as simple as rewriting the instructions or moving a button.

One nuance we like to look for is circular errors. What’s a circular error? It’s when, during a single session, a user sends the same input multiple times and receives the same error. For example, a user submits a page, and the email is determined to be invalid (a logged error.) Then the user submits again, with the same email (and maybe then a third time, again with the same email.) These types of circular errors usually mean the error messaging system in your application is flawed. Perhaps the error text appears at the top of the screen, and the field itself is below the fold, so the user may not even be seeing the error text.

The third type of error is failed search or out of stock messages. The user wants to rent a car with a pickup at 2 am but that location is closed, or the user wants the pants in a 42 waist, but you don’t have any in stock. Or, the user is searching your site for information on bed wetting, but no articles match that term. These types of errors indicate a missed opportunity to meet a customer need, and you should scour these types of messages to consider what steps can be taken to meet commonly requested unmet needs.

All of this is based on the assumption that your site’s back-end code is logging errors properly. This is a standard coding practice, but just because it’s standard doesn’t mean it can’t get omitted, or that certain errors might not have code that logs them. It’s important to check with your technical team; if your site is not logging most errors, or not logging them with sufficient detail, this code can generally be added.

Additionally, you may include logging at different levels of your system, and therefore have multiple log files. For example, the web server may have one log file, the commerce layer may have a separate log file, and your security/authentication layer may have its own log files, and that’s fine. There are great tools that can combine them together and make them easy to analyze, filter, sort, etc.

The logging I’ve been referring to is generally done on the server. However, with each new generation of digital experiences, we push more and more code (including more and more error checking) to the client. Whether it’s javascript (in the case of web pages), or Java code (in the case of mobile apps.) These types of error events can be logged as well, it just requires a separate effort or technology (but it’s well worth it!) You can use analytics packages like Google Analytics to record “events” when certain things (like error messages) happen in the interface.

A one or two-day analysis of error logs can help you focus in on specific, frequently occurring error states that were previously off your radar. Sometimes, it’s still necessary to do user testing to figure out what the deeper reason for the confusion is, but even still, it’s helpful to know where the errors are occurring, so you can focus your testing there. In other cases, it’s easy to guess what’s tripping your users up, once the errors are there to act as signposts.

This article originally appeared on the Howard Tiersky blog

Image Credits: Pixabay

Subscribe to Human-Centered Change & Innovation WeeklySign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.

SpaceX is a Masterclass in Innovation Simplification

SpaceX is a Masterclass in Innovation Simplification

GUEST POST from Pete Foley

This capture from a recent SpaceX tweet is a stunning visual example of smart innovation and simplification. 

While I’m not even close to being a rocket scientist, and so am far from familiar with all of the technical details, I’ve heard that breakthroughs incorporated into this include innovative sensor design that allows for streamlined feedback loops. But this goes beyond just impressive technical innovation.   To innovate at this level requires organizational and cultural flexibility as well as technical brilliance. That latter flexibility is probably far more broadly transferable and adoptable than specific advances in rocket science, and hence more useful to the broader innovation community. So let’s dig a little deeper into that space.

Secret Sauce?  Organizationally SpaceX is well known for less formal hierarchies, passion, ownership and engineers working on the production floor.  This hands on approach creates a different, but important kind of feedback, while passion feeds intrinsic motivation, ownership and engagement, which is so critical to consistent innovation. 

Learning from Failure – An Innovation Superpower?  But perhaps most important of all is the innovation culture. Within SpaceX there is a very clear willingness to experiment and learn from failure.  Not lip service, or the sometimes half-hearted embrace of failure often found in large, bureaucratic organizations, where rewards and career progression often doesn’t reflect the mantra of learning by failing.  This is an authentic willingness to publicly treat productive failure of individual launches as a learning success for the program, and to reward productive failure and appropriate risk taking.  Of course, it’s not always easy to walk the talk of celebrating failure, especially in spacecraft design, where failures are often spectacular, public, and visual gold for the media.  And no doubt this is compounded by Musk’s controversial public profile, where media and social media are often only too keen to highlight failures.  But the visual of Raptor 3 is for me a compelling advertisement for authentically embedding learning by failure deeply into the DNA of an innovative organization. 

Stretch Goals:  Musk is famous for, and sometimes ridiculed for setting ambitious stretch goals, and for not always achieving them.   But in a culture where failure is tolerated, or if done right, celebrated, missing a stretch goal is not a problem, especially if it propelled innovation along at a pace that goes beyond conventional expectation.    

Challenging Legacy and ‘Givens’:  Culturally, this kind of radical simplification requires the systematic challenge of givens that were part of previous iterations.  You cannot make these kind of innovation leaps unless you are both willing and able to discard legacy technical and organizational structures.  

At risk of kicking Boeing while it is down, it is hard not to contrast SpaceX with Boeing, whose space (and commercial aviation) program is very publicly floundering, and facing the potentially humiliating prospect of needing rescue from the more agile SpaceX program. 

Innovation Plaque:  But in the spirit of learning from failure, if we look a bit deeper, perhaps it should not be a surprise that Boeing are struggling to keep up. They have a long, storied, and successful history as a leader in aerospace.  But history and leadership can be a blessing and a curse, as I know from P&G. It brings experience, but also bureaucracy, rigid systems, and deeply rooted culture that may or may not be optimum for managing change.  Deep institutional knowledge can be a similar mixed blessing.  It of course allows easy access to in-domain experience, and is key to not repeating past mistakes, or making naïve errors.  But is also comes with an inherent bias towards traditional solutions, and technologies.  Perhaps even more important is the organizationally remembered pain of past failures, especially if a ‘learn by failure’ culture isn’t fully embraced.  Failure is good at telling us what didn’t work, and plays an important role in putting processes in place that help us to avoid repeating errors.  But over time these ‘defensive’ processes can build up like plaque in an artery, making it difficult to push cutting edge technologies or radical changes through the system.

Balance is everything.  Nobody wants to be the Space Cowboy.  Space exploration is expensive, and risks the lives of some extraordinarily brave people.  Getting the balance between risk taking and the right kind of failure is even more critical than in most other contexts. But SpaceX are doing it right, certainly until now. Whatever the technical details, the impact on speed, efficiency and $$ behind the simplification of Raptor 3 is stunning.  I suspect that ultimately reliability and efficiency will also likely helped by increased simplicity.  But it’s a delicate line.  The aforementioned ‘plaque’ does slow the process, but done right, it can also prevent unnecessary failure.   It’s important to be lean, but  not ‘slice the salami’ too thin.  Great innovation teams mix diverse experience, backgrounds and personalities for this reason.  We need the cynic as well as the gung-ho risk taker.  For SpaceX, so far, so good, but it’s important that they don’t become over confident.  

The Elon Musk Factor:  For anyone who hasn’t noticed. Musk has become a somewhat controversial figure of late. But even if you dislike him, you can still learn from him, and as innovators, I don’t think we can afford not to. He is the most effective innovator, or at least innovation leader for at least a generation. The teams he puts together are brilliant at challenging ‘givens’, and breaking out of legacy constraints and the ‘ghosts of evolution’. We see it across the SpaceX design, not just the engine, but also the launch systems, recycling of parts, etc. We also see an analogous innovation strategy in the way Tesla cars so dramatically challenged so many givens in the auto industry, or the ‘Boring company in my hometown of Las Vegas.

Ghosts of Evolution I’d mentioned the challenges of legacy designs and legacy constraints. I think this is central to SpaceX’s success, and so I think it’s worth going a little deeper on this topic.  Every technology, and every living thing on our planet comes with its own ghosts.   They are why humans have a literal blind-spot in our vision, why our bodies pleasure centers are co-located with our effluent outlets, and why the close proximity of our air and liquid/solid intakes lead to thousands of choking deaths every year. Nature is largely stuck with incrementally building on top of past designs, often leading to the types of inefficiency described above. Another example is the Pronghorn antelope that lives in my adopted American West. It can achieve speeds of close to 90 mph. This is impressive, but vastly over-designed and inefficient for it’s current environment. But it is a legacy design, evolved at a time when it was predated upon by long extinct North American Cheetah. It cannot simply undo that capability now that it’s no longer useful. So far, it’s survived this disadvantage, but it is vulnerable to both competition and changing environment simply because it is over-designed.

Bio-Inspiration:  I’ve long believed we can learn a great deal from nature and bio-inspired design, but sometimes learning what not to do is as useful as ‘stealing’ usable insights. It’s OK to love nature, but also acknowledge that evolution has far more failures than successes. There are far, far more extinct species than living ones.  And virtually every one was either too specialized, or lacked the ability to pivot and adapt in the face of changing context.  

As innovators, we have unique option of creating totally new 2.0 designs, and challenging the often unarticulated givens that are held within a category. And we have the option of changing our culture and organizational structures too.  But often we fail do so because we are individually or organizationally blind to legacy elements that are implicitly part of our assumptions for a category or a company.  The fish doesn’t see the water, or at least not until it’s dangling from a hook. By then it’s too late.   Whatever you think of Musk, he’s taught us it is possible to create innovation cultures that challenge legacy designs extremely effectively.  It’s a lesson worth learning

Image credits: Twitter (via SpaceX)

Subscribe to Human-Centered Change & Innovation WeeklySign up here to join 17,000+ leaders getting Human-Centered Change & Innovation Weekly delivered to their inbox every week.