Innovation by Elimination

When a business has a problem, the reflex is to add something. More software. More reports. Another approval step. Another person to watch the first person. Adding feels like progress because you can point at it. A new system has a launch date and a budget line. Nobody throws a party for the form that stopped existing.

I have spent a good part of my career inside large organizations, and I have watched this reflex play out many times. Processes accumulate steps the way garages accumulate boxes. Each item had a reason when it arrived, and nobody remembers the reason now, so nobody feels safe removing it.

There is a method that works in the opposite direction, and it is easy enough to explain in one sentence: eliminate one thing. This article explains how I use it, why it works, and how you can try it with your own team without hiring a consultant or buying a toolkit.

Why Look for Something Simpler

Innovation, process improvement, and value engineering matter to every business. There are well-known formal methods for them, such as Six Sigma and Lean. They are proven, and they give you structure and a repeatable approach. They also come with a long list of tools, vocabulary, and training, and that overhead keeps many teams from starting at all.

Elimination asks for much less. You do not need a value stream map or a fishbone diagram to begin. You need to look at how people actually do their jobs, pick one item, and take it away in your imagination (or, if you are brave and it is safe, in practice).

The idea has roots in a structured creativity approach called Systematic Inventive Thinking, described in the book Inside the Box by Drew Boyd and Jacob Goldenberg. I recommend the book if you want the full theory. What follows is the version I actually use at work, in plain terms.

The Core Idea

Look at how the roles in your organization do their jobs. What equipment do they use? What paper forms do they fill out? What steps do they follow? Choose one item from that list and ask three questions:

1. What would happen if this were gone tomorrow?
2. How would the work still get done?
3. What is already in the work environment that could take its place?

Sometimes the answer to the third question is "nothing, and we do not need it." That is the best outcome, because it means you found a legacy activity that has been costing time and attention for no benefit.

If you have done business analysis, this will feel familiar. It is close to asking "why" five times to find the root reason something is done. The difference is in the move. Instead of asking why, you remove the thing and watch what the organization reaches for. That reaction tells you what the thing was really for.

An Example: Eliminate the Pen

The exercise I use to introduce this idea is almost embarrassingly simple. Imagine walking into a business and taking away every pen. Here is how it played out when I ran it for real, and then what you can take from it.

The first reaction is usually a laugh, followed by a pause. Then the questions start. How do people complete their forms? Where do they write down a customer's details during a call? How does a supervisor sign off on something?

Every one of those questions points at a real piece of the process. A pen sits underneath a lot of paper, and paper sits underneath a lot of manual handling: someone writes it, someone reads it, someone retypes it into a system, someone files it, someone looks for it later. Once the pen is gone, you have to ask whether the information could go into a computer system directly. You have to ask whether a piece of software the company already owns could replace the paper. And you have to ask whether the form is still needed at all.

I did this at a plasma donation center. I started by walking through how a donation is done, from the front desk to the donor bed, and I observed every staff member along the way: what they handled, what they wrote down, and what they did with it afterward. When I looked over everything I had seen, I chose the pen as the item to eliminate, and I chose it on purpose. It was the most controversial thing I could have picked. Take away the pen and staff cannot write anything down, in a place where a lot of what happens needs to be recorded.

That reaction was the value of the exercise. Because nobody could say "just write it down," we had to find a new solution for every place a pen was used, and the solutions came in three kinds:

• A new feature in existing software. The information could be entered directly into a system the center already used, once the software did a little more.
• A different supplier. In some cases the paper or the process was tied to a supplier's product, and changing the supplier removed the need for the pen.
• Eliminating the process altogether. Some of the writing was a leftover from a past practice. Once we asked what would happen without it, the answer was nothing, and the step could simply go.

What I like about this approach is how fast it moves people off the defensive. Nobody feels threatened by a pen, so they answer honestly, and the honest answers expose the real shape of the work: the duplicate data entry, the forms that exist because another form exists, the steps that survive because "we have always done it this way."

The same exercise keeps going for as long as you want it to. Remove a printer. Remove a computer from the business floor. Remove a meeting room. Each removal opens a fresh set of questions.

Start With Things You Can Touch

You can eliminate an idea, such as a policy or a report, but I find tangible things work best. A pen, a sheet of paper, a printer, a computer, a device, a peripheral, a room, a section of floor space. A physical item forces a concrete answer. You cannot hand-wave about a printer that is gone.

Tangible removals also tend to pay off in several ways at once. Fewer physical touchpoints usually means a more efficient process, fewer places for sensitive information to leak, and an easier time keeping the business running when something goes wrong. A team that does not depend on a particular printer or a particular filing cabinet has one less thing that can stop them.

How to Run It: Five Steps

Step 1: Map What Exists

Write down the steps, tools, people, approvals, and outputs in one process. It does not need to be pretty. A page of notes is enough. The goal is to see the whole set of things you could remove.

Step 2: Pick Something Everyone Assumes Is Required

Do not start with the obvious waste. Lean and Six Sigma already teach you to find that, and people are usually happy to give it up. Choose an item that everyone treats as mandatory: the manager sign-off, the printed statement, the intake call, the staging environment, the status meeting. The more "of course we need that" you hear, the better the candidate.

Step 3: Picture the Process Without It

Run the whole process in your head (or on a whiteboard) with that item gone. You will hear "that would break everything" almost immediately. Write that objection down and keep going anyway. The objection is useful information, because it names what you would need to cover.

Step 4: Replace Only From What You Already Have

If a real function disappeared, such as a quality check or a record of who approved what, look for an adjacent step or an existing tool that can cover it. Stay inside the resources you already have. The moment you reach for a new purchase, you are back to adding, and you lose the pressure that makes this method productive. Constraints make people creative in a way that open budgets do not.

Step 5: Name the Benefit

Ask what the removal gives you. Shorter cycle time? Less handling? Fewer ways for the process to fail? A chance for customers or staff to do the task themselves? If you cannot name a benefit, put the item back. Not every experiment needs to win.

Why Subtraction Works

There are a few reasons this simple move gets results that heavier methods sometimes miss.

• It breaks the "must stay as it is" assumption. People tend to believe a process needs all of its current parts. Removing one part, even in imagination, shows how much of that belief is habit.
• It uses what you already have. Because you can only draw on existing resources, the answers are cheap and fast to try. They also fit your environment, because they came from it.
• It reverses the usual order. Normally you identify a need and then design something to meet it. Here you remove the component first, look at the odd reduced version that is left, and ask who would benefit from it. The function follows the form.
• Constraints produce better ideas than freedom. A team told to cut 5 percent will trim. A team told the approval step no longer exists will redesign.

A well-known product example is the Sony Walkman. Engineers took a standard cassette player and removed the recording function and the speakers. What remained looked like a broken tape recorder, and it turned out to be a light, personal music player that people loved.

It Works Beyond the Office Floor

The pen is a starting exercise. The same thinking has shaped products and business models you probably already use.

A Few Cautions

• Respect compliance and safety. Some steps exist because a regulation or a risk requires them. Check before you remove anything in that category, and treat the exercise as a thought experiment until you have.
• Involve the people who do the work. They know what the pen is really used for. Run the exercise with them, not about them.
• Test small. Try the removal with one team, for a short period, with a way to restore the item. Lasting changes come from evidence.

Try It This Week

Choose one process that frustrates people. Find the step that takes the longest or needs the most coordination. Remove it on paper and ask how the tools you already have could cover what it was doing. If you want a warm-up first, take the pens away from a meeting and see what people reach for.

Most organizations are very good at adding. The advantage goes to the ones who get comfortable removing things and finding out what was never needed.