Category Archives: Design

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.

Finding Innovation in the Humble Garbage Can

Finding Innovation in the Humble Garbage Can

GUEST POST from Howard Tiersky

Uber has taught us that even the most commonplace products and services are ripe with innovation. They’ve re-invented the taxi experience, and many people would agree that, given a choice, they’d never go back to the old way.
Today, I want to give a shout out to another company, one that’s doing amazing things with garbage cans: simplehuman.

Simplehuman, founded in 2000 by Frank Yang, is a great case study in terms of product innovation, as well as business model. It had one simple mission: make a better trash can. For the last year, I’ve had a simplyhuman garbage can in my kitchen, so I can attest. It is a better trash can.

Before we switched to simplehuman, this is the kind of trash can we had in the kitchen:

And this is the simplehuman can that’s in my kitchen today:

Two features of this product make it a real game-changer. The lesser of these was the rim around the top that completely hides the edges of the plastic bag that peek over the edge most cans. I didn’t realize how ugly this was until it was gone. (insert sigh of relief here)

But the real hero is the built-in garbage bag dispenser. As you can see from the image below (pulled directly from simplehuman’s website), a dispenser for new garbage bags is built right into the body of the can, saving me from having to walk across the room to get a new bag from the box under the kitchen sink when I need a replacement. Yes, this is a seemingly small inconvenience, but once it’s removed, it seems a silly waste of effort that you ever had to walk across the room in the first place.

While they may not be solving world hunger, these two improvements are enough for me to never want to go back.

Simplehuman: Our new stainless steel rectangular step can features an innovative ‘liner pocket’ that stores and dispenses liners from inside the can for a faster liner change.

But from a business perspective, here’s where it gets interesting. In order to have garbage bags that fit both the dispenser and perfectly around the rim (so that no “spillover” bag is showing,) I need to use their custom-fitted bags. These bags are sized specifically for this can and come in little boxes perfectly sized to fit the built-in dispenser.

So where does one get these magical bags? Well, when you buy the can, there’s an insert that directs you to download simplehuman’s app. In the app, you can “manage your supplies,” by ordering garbage bags or, even better, setting up a subscription, which is what I did.

What do these garbage bags cost? A 100-count box of simplehuman garbage bags is about $25. That doesn’t break the bank, but as it turns out, it’s about twice what Hefty and Glad bags cost. Besides that, the garbage can itself is about $100, compared with less than half of that for one of their less innovative competitor’s stainless steel kitchen garbage cans. Again, not outrageous, but still a substantial premium. So what’s innovation worth to simplehuman? About double. And it’s worth it to me to pay it to solve problems, even if I never realized there were problems until simplehuman’s solution brought them to my attention.

Coming up with these types of innovations for your business starts with finding painpoints. What is your customer’s equivalent of having to walk across the room to get a garbage bag from under the sink? It doesn’t have to be pain that drives them crazy. Solving just a small irritation can turn out to be a highly appreciated innovation. And what about aesthetic gaps in your products that nobody focuses on, but would be obvious once gone (the way Steve Jobs showed us how ugly PCs were by creating the iMac)?

Finding these types of unmet points of pain can be achieved through ethnography and other research techniques that create customer empathy. Techniques like these can generate profound insights with relatively minimal effort, and at FROM, we utilize them on nearly every project. The majority of the time, the most winning features of the new digital products we create come from solving problems generated by these insights. The ideas may not come from the customers (in fact, they probably won’t) but the pain insights do. Once you have those, it can open up new doors, and allow your team to come up with many new solutions.

Additionally, innovation is often not just about the product, but also the business model. Achieving simplehuman’s innovation required custom-fit garbage bags. I’d imagine that, at one point before launching this product, simplehuman realized it would be difficult to get every grocery store in America to carry these bags, especially before their product achieved critical mass. That logistical problem could have killed the whole concept. But instead of working within the existing ecosystem, where can-sellers have to align to a few non-tailored garbage bag sizes, they shifted their business model to app-based subscription. This allowed them not only to deliver the innovation, but also to double the price of their bags (probably without customers even noticing, since their bags aren’t sold side-by-side with mainstream brands), and to realize 100% of the revenue via direct sales, rather than splitting with a retailer and distributor.

So I say Bravo!, simplehuman. Great innovation, great business, and thanks for making my life a little bit better — I’m happy to pay you more for it. Now imagine what I’d be willing to pay if you could figure out how to get the can to take the full garbage bag outside!

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.






Unlocking Innovation Through Prototyping

GUEST POST from Mike Shipulski

A prototype moves us from “That’s not possible.” to “Hey, watch this!”

A prototype moves us from “We don’t do it that way.” to “Well, we do now.”

A prototype moves us from “That’s impossible.” to “As it turns out, it was only almost impossible.”

A prototype turns naysayers into enemies and profits.

A prototype moves us from an argument to a new product development project.

A prototype turns analysis-paralysis into progress.

A prototype turns a skeptical VP into a vicious advocate.

A prototype turns a pet project into top-line growth.

A prototype turns disbelievers into originators of the idea.

A prototype can turn a Digital Strategy into customer value.

A prototype can turn an uncomfortable Board of Directors meeting into a pizza party.

A prototype can save a CEO’s ass.

A prototype can be too early, but mostly they’re too late.

If the wheels fall off your first prototype, you’re doing it right.

If your prototype doesn’t dismantle the Status-Quo, you built the wrong prototype.

A good prototype violates your business model.

A prototype doesn’t care if you see it for what it is because it knows everyone else will.

A prototype turns “I don’t believe you.” into “You don’t have to.”

When you’re told “Don’t make that prototype.” you’re onto something.

A prototype eats not-invented-here for breakfast.

A prototype can overpower the staunchest critic, even the VP flavor.

A prototype moves us from “You don’t know what you’re talking about.” to “Oh, yes I do.”

If the wheels fall off your second prototype, keep going.

A prototype is objective evidence you’re trying to make a difference.

You can argue with a prototype, but you’ll lose.

If there’s a mismatch between the theory and the prototype, believe the prototype.

A prototype doesn’t have to do everything, but it must do one important thing for the first time.

A prototype must be real, but it doesn’t have to be really real.

If your prototype obsoletes your best product, congratulations.

A prototype turns political posturing into reluctant compliance and profits.

A prototype turns “What the hell are you talking about?” into “This.”

A good prototype bestows privilege on the prototype creator.

A prototype can beat a CEO in an arm-wrestling match.

A prototype doesn’t care if you like it. It only cares about creating customer value.

If there’s an argument between a well-stated theory and a well-functioning prototype, it’s pretty clear which camp will refine their theory to line up with what they just saw with their own eyes.

A prototype knows it has every right to tell the critics to “Kiss my ass.” but it knows it doesn’t have to.

You can argue with a prototype, but shouldn’t.

A prototype changes thinking without asking for consent.

Image credit: misterinnovation.com

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.






Think Outside Which Box?

Think Outside Which Box?

GUEST POST from Howard Tiersky

We’ve all said it. We need to think “outside the box.”

But what is this box-like barrier that would otherwise constrain our thinking, and how do we move beyond it?

At FROM, we use our custom-built workshop space, Innovation Loft, to help teams from some of the largest brands in the world move beyond that metaphorical box to create new products, processes or entire businesses. We’ve spent a lot of time studying the barriers that limit individual or team thinking, and testing methods to break free of those barriers.

Through our work, we’ve discovered there isn’t just a single box. Instead, there are four nested barriers that can limit thinking.

  1. HABIT
  2. BELIEF
  3. IDENTITY
  4. IMAGINATION

You can use a variety of different techniques that you can apply to help get past each box, but they differ, depending on which box you’re focused on.

BOX ONE: HABIT

People constrained by habit are best described by the phrase, “If it ain’t broke, don’t fix it!” This box exists because it’s our comfort zone – where we know what works. But the uncharted territory is where much of the treasure lies!

Overcoming the Limits of Habit

How do you move teams beyond habit? One way is to explore ‘stretch-goals,’ or goals well beyond what’s possible with your current method of doing business. For example, if your manufacturing process takes 90 minutes to produce a carton of ice cream, conduct an exercise to brainstorm how you could produce that same carton in only 5 minutes. This type of exercise requires completely different thinking about the entire manufacturing process. It might not actually be practical or cost-effective to make the cartons in 5 minutes, but the process of thinking about how it could be done is one way to explore what lies beyond the box of habit.

BOX TWO: BELIEF

Even when we’re ready to move past habit and try something new, there’s another box that constrains what we believe will work or are capable of accomplishing. In corporate environments, the box of belief is epitomized by statements like, “We tried that before and it didn’t work,” or “We can’t compete in that space.”
Whether these beliefs are true or not, they’re often over-generalized or stated in absolute terms. Take, “We can’t compete in that space.” It may not be wise to compete in that space, but is it really impossible? By staying in the box of belief, you could be dismissing possible opportunities.

Overcoming the Limits of Belief

To tackle the barrier of belief, use an exercise that sorts beliefs from facts. Underlying facts are helpful, but the beliefs associated with them can be limiting. If you chose to pursue a certain goal, how would you move past the facts? If it’s not that you can’t compete, but that there are barriers to doing so, what are they and how might you get past them? Ultimately, you want ideas for clearing each obstacle, so you can evaluate if it makes sense to proceed.

BOX THREE: IDENTITY

Even when we’re willing to change and believe certain things are possible, we can remain stuck inside of a box of our own identity. This box is best characterized by statements like, ‘We don’t do that at this company,” or “That wouldn’t be consistent with our brand.”

Overcoming the Limits of Identity

First things first: It’s valuable to have an identity, and to have a brand that customers know stands for something. However, getting past a belief barrier doesn’t necessarily mean acting outside the box, but just to think outside the box. Identities need to grow and change over time, and can’t do that if you never consider possibilities beyond your current identity. (e.g., Apple used to be called ‘Apple Computer,’ but now they make more money from phones and are known as simply ‘Apple.’)

To temporarily think outside your current identity, play the ‘What Would Company X Do?” game. Give separate teams one company or entity, and have them look at the problem at hand in the way that organization might. Apple, the Marines, Starbucks, and Disney are good companies to use as models, as they’re all successful entities with very different identities and ways of solving problems. Viewing your company’s problems or opportunities through the lens of another company can yield interesting, new ideas. If some of the ideas aren’t a good fit, that’s ok! In ideation, we’re mining for gold, so a large quantity of sand and pebbles in the pan is not an indicator of failure – it’s the number of gold nuggets that indicate success.

BOX FOUR: IMAGINATION

Ideas beyond the box of imagination aren’t even a blip on the radar, or even in the realm of our thinking. We don’t consider them outside our beliefs, or inconsistent with our identity because we don’t consider them at all.

Overcoming the Limits of Imagination

What we can imagine comes from a combination of our experiences, plus an ability to take those experiences and combine them in novel ways. To stimulate imagination, it’s important to define a clear goal for your team, and encourage them to share and explore past experiences that may be relevant to that goal. If you want to increase customer loyalty, have your team review experiences that have affected their loyalty to other products and services. Then, expose them to new ideas and knowledge – things like competitive case studies, trends or technologies that might be part of a solution to the problem. When teams have a greater range of experiences to draw from, they can start to imagine possibilities that they didn’t previously have the “raw materials” to form.

It’s fantastic to have an identity, beliefs, and habits. All these aspects of our personality serve us in various situations. But it’s also valuable to be able to temporarily turn these psychological limits off in the context of exploratory ideation. You never know what’s out there, and you can enrich your value proposition, your brand and even yourself by embracing the freedom to explore what lies beyond. Then, you can decide for yourself whether or not to expand the box!

This article originally appeared on the Howard Tiersky blog
Image Credits: Pexels

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






Problems are Required for Progress to Occur

Problems are Required for Progress to Occur

GUEST POST from Mike Shipulski

Without a problem, there can be no progress.
And only after there’s too much no progress is a problem is created.
And once the problem is created, there can be progress.

When you know there’s a problem just over the horizon, you have a problem.
Your problem is that no one else sees the future problem, so they don’t have a problem.
And because they have no problem, there can be no progress.
Progress starts only after the calendar catches up to the problem.

When someone doesn’t think they have a problem, they have two problems.
Their first problem is the one they don’t see, and their second is that they don’t see it.
But before they can solve the first problem, they must solve the second.
And that’s usually a problem.

When someone hands you their problem, that’s a problem.
But if you don’t accept it, it’s still their problem.
And that’s a problem, for them.

When you try to solve every problem, that’s a problem.
Some problems aren’t worth solving.
And some don’t need to be solved yet.
And some solve themselves.
And some were never really problems at all.

When you don’t understand your problem, you have two problems.
Your first is the problem you have and your second is that you don’t know what your problem by name.
And you’ve got to solve the second before the first, which can be a problem.

With a big problem comes big attention. And that’s a problem.
With big attention comes a strong desire to demonstrate rapid progress. And that’s a problem.
And because progress comes slowly, fervent activity starts immediately. And that’s a problem.
And because there’s no time to waste, there’s no time to define the right problems to solve.

And there’s no bigger problem than solving the wrong problems.

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.