The 10 Worst Innovation Mistakes In A Recession (Update and Repost)

Are we in a recession? No.

Could we be in one real soon? Yes.

Regardless of what “the experts” tell you, two things are true.

  1. Trade Wars are BAD for the economy.
  2. Economic Alliance Breakdown (like Brexit) is BAD for the economy.

Both of these events can spark recessions, and are very statistically likely to at least spark localized recessions in some industries in some geographies. And while it’s hard to say which geographies and industries and to what extent due to the proliferance of alternative facts on even the major media outlets (which is what happens when you let party oriented moguls conglomerate holdings and reduce journalist headcount), it’s still not hard to say the risks are rapidly increasing.

It’s also not hard to say that, based on past behaviour, most organizations are bound to do the wrong thing when it starts. So, to this end, SI is reposting this classic piece from 2008 to remind you of what not to do if things get tight (which is based on a great piece on the 10 Worst Innovation Mistakes in a Recession that appeared in Business Week in January, 2008.

Moreover, making these mistakes creates a self-fulfilling prophecy that spirals you towards hardship.

  1. Fire Talent
    Talent is the single most important variable in innovation. And innovation is the single largest lever you have to increase productivity and decrease costs.
  2. Cut Back on Technology
    The rise of social networking and consumer power means that companies have to be part of a larger conversation with their customers. This requires technology. Furthermore, the best way to insure you are getting the best price is to tackle the right categories, as identified by spend analysis, with strategic sourcing decision optimization to make sure you are making the award with the lowest total cost of ownership. It’s also important to make sure that all of your invoices are submitted in an electronic format that can be automatically matched against contracted rates to make sure you are being overcharged. This requires leading-edge technology.
  3. Reduce Risk
    Innovation requires taking chances and dealing with failure. Although it’s important to control risk, trying to eliminate it entirely will just end up eliminating any chance for innovation at your company.
  4. Stop New Product Development
    This hurts companies when growth returns and they have fewer offerings in the marketplace to attract consumers. And with today’s rapid pace of technological change, you could even lose customers in a recession to a competitor who keeps innovating while you stand still.
  5. Replace a Growth-Oriented CEO with a Cost-Cutting CEO
    Most recessions only last two or three quarters and, these days, are relatively shallow. Penny-pinching CEOs don’t have the skills to grow when growth returns. Plus, a penny-pinching CEO is the most likely individual to fire your top talent.
  6. Retreat from Globalization
    Emerging markets are sources of new revenue, business models, and talent. And, like it or not, emerging economies like India and China are soon going to have more buyers for your product than the countries you’re currently selling to.
  7. Replace Innovation as Key Strategy
    … With Systems Management and Cost-Cutting. Once focus shifts away from innovation, it can be very hard to get the focus shifted back.
  8. Change Performance Metrics
    Shifting employee evaluations away from rewarding riskier new projects toward sustaining safer, older goals. This leads to risk-averse behavior and stifles innovation.
  9. Re-inforce Hierarchy over Collaboration
    A return to command-and-control management. This alienates creative-class employees, young Gen Y and X-ers, and stops the evolution of the corporation. In today’s world, companies that don’t evolve die – and they do it quickly. The average life-span of a Fortune 500 company is shrinking every year.
  10. Retreat into Moated Castles
    Cutting back on outside consultancies is seen as a quick way to save money. Yet, one of the key ways of introducing change into business culture is to bring in outside innovation and design consultants.

Remember that winners always emerge out of recessions and they always win on the basis of something new. If you don’t always have something new in your pocket, you’re not going to win. And if it is a recession, and you don’t have something brand spanking new to pull out of your pocket when the recession is over, you could literally be toast. Furthermore, even a recession provides growth opportunities. People still spend money. They still need to eat, maintain their homes, and their life-styles. The difference is that they don’t spend as much money and look considerably harder for the best deal. This means that they’re much more likely to waver on brand loyalty if you can provide them a better product on a better price – and this means that you can still grow by taking market share away from your competition.

So don’t make the innovation mistakes. If it is a recession, then whether you come out of it a winner or a loser is up to you.

Furthermore, if it is a recession, and your company supplies sourcing and procurement technology and services, then this should be a major growth period for you! After all, how else is your average blind-in-one-eye company going to save money? This means that not only do you have to make sure that you don’t make any of the top 10 innovation mistakes, but that you invest for a growth period because, if you play your cards right, it will be.

Platform iZombie, Part II

As we stated yesterday, we’re all zombies. Procurement is continuing along in the most undead fashion possible, going through the same motions day after day like a clockwork automaton of the 19th century. The platforms that the visionary consulting firms and platform providers were supposed to provide us by 2020 (less than 15 short months away) have not materialized and we are stuck in a tactical nightmare. Which is about the worst kind of nightmare.

We’re dead serious about that last part. If you consider the most common bad nightmares — being naked in public is only going to embarrass you at most once (and not at all if you are a nudist), a broken bone will heal, a fall just wakes you up, we’re all cheated, we’re all interested in the unknown, we probably know or believe ghosts aren’t real (or probably can’t harm us), many spiders are more scary than dangerous, teeth fall out when we’re young to regrow, danger is always present, we will eventually be late for something because Murphy’s laws tell us sh!t happens, people are always trying to steal our IP, we all fell like we’re drowning in the modern world (of work), it’s easy to be lost in the big picture, and we all get fed up of loved ones sometime — I think the living nightmare of doing the same thing day after day expecting a different result (which is the definition of insanity by the way) is the worst of all. And, remember, you can always wake up from a nightmare. You can’t wake up from the zombie state modern platforms have put us in.

But it could be better. In our last post we indicated how a modern platform could have saved over 80% of our time with simple capabilities that really should have been in every platform for the past five years.

But would this be the case in general? Would a modern platform really eliminate 80% of our entire workload? Let’s run through the rest of the day.

We return from lunch to our stakeholder meeting. Now, it’s true that no platform can eliminate the meetings and you’re still going to lose that time to a degree, but with the right platform, you can make meetings more productive.

With a good platform, the customer success rep would see that her peers were happy with the supplier’s performance and that it was improving and that her customers were next to get the replacements. She’d still be unhappy, but well informed and willing to wait until the next shipment before taking her final position.

The finance rep would already know why you disqualified the lowest bidders. Any discussion could thus be focussed on the question as to whether or not one of the lowest bidders could be improved to a level of acceptability over time versus an inquisition as to why the bidder was eliminated.

The engineering rep could see all the cost models and the savings projections over time and understand the issues everyone (else) has with the incumbent.

And the marketing rep would know that while you want suppliers with exciting features, there are critical requirements that need to be met in order to keep production lines going and shelves stocked. And those needs must come first.

Instead of thirty minutes of complaining, ranting, and basic Q&A before you can get down to meaningful discussions, since all the stakeholders have insight into all the facts, you can get down to real discussions and debates. It may not be productive, but at least you skip addressing the stuff you should already know.

And then there’s the issue of the meeting conclusion — more suppliers are needed and that’s another discovery project that you estimate at 20 hours or more. But if you had a modern discovery platform with deep intelligence and match capability, it would not be a 20 hour project, it would be a 2 hour project — at most. The first phase would be like 20 minutes, and you could slip out and do it on a break.

But anyway, because it’s not something you can make any progress on today, you move onto supplier emails and that’s where discover that your steel shipment didn’t ship yesterday and you need a replacement in 21 days or your production line is going down. And you spend an hour and a half trying to find a substitute. With a good platform, you know all of the suppliers that provide a similar or substitute product, which are under contract, and what the last bids were. You can start calling them immediately, and likely find a replacement supplier in three calls and 30 minutes, not 90 or more.

And let’s not mention the 40 minutes you waste reviewing emails that ask questions that could be answered in a good supplier portal or automatically answered by a chatbot.

It’s almost five before you get down to the project work. The platform won’t save you the time required to answer technical supplier questions, the time to manually score an RFX, or the time to figure out why suppliers aren’t bidding, but you’d get to it about 5 hours earlier in the day!

And when you accomplish something by noon, versus working to seven and accomplishing nothing, you find your headaches are a lot less and you don’t need to pop quite so many painkillers.

Platform iZombie, Part I

If you’ve been keeping up to date on our ongoing blog series, you know why we’re all zombies. The reason, simply put, is that, instead of Procurement recognizing that it was supposed to be dead and buried two years ago, and maybe rising from the ashes, it has instead continued along in an undead fashion. Each day, we go through the same motions, using the same processes, on the same old platforms. Platforms which, according to the visionary consulting firms and platform providers, were supposed to solve all our problems and release us from this tactical nightmare. Instead, they have done nothing to ease our woes and, in many situations, have made them worse!

Not only are the majority* of platforms still based on last decade’s processes, but they aren’t even making them easier. In essence, they are fueling the Procurement zombie nation and they should be ashamed of themselves.

To understand how, let’s consider our average Monday morning, as documented in iZombie: A Prelude Part I, and how a modern platform would have prevented us from wasting four hours of our day.

First of all, it takes you five minutes just to judge how many emails are from each type of project stakeholder. A good platform with integrated communications would give you that information in 5 seconds, with communications already arranged by urgency and seniority (based on your organizational structure and derived from your typical review patterns).

Secondly, the modern system with the integrated cognitive monitor would immediately detect that an email didn’t go out because it didn’t have the new SSL certificate, invoke the process to download the SSL certificate, and send the email again.

Thirdly, you never would have gotten that call from your widget supplier because:

  • as soon as the invoice was marked “DO NOT PAY”, you would have been alerted, known of the issue, and marked it for “monitoring”
  • as soon as it was past due, you would have followed up with Engineering, who would have said “yes, we got the shipment, it’s in the system”
  • you would have searched for all invoices with similar products, found one for the proper product, noticed the invoice ID was miskeyed, fixed it, and sent Finance an e-mail to remove the “DO NOT PAY”
  • the invoice would immediately enter the payment queue, and the supplier would be notified on their portal
  • it would have been paid on the next payment date, 7 days in the future, and 23 days before you got the angry screaming call

and all this would have taken you 10 minutes a month ago, instead of almost an hour now!

But now the biggie — because of your antiquated platform, it took you 3 hours to construct a project overview report that summarized the status on all the key projects, issues, and actual/projected vs. budget. A modern platform would automatically track all those metrics, allow you to record issues as they arrive and tie those metrics to issues, and then, when a summary report is created, automatically pull the issue summary and status into an appendix.

A modern sourcing platform would come with a customizable template that you could customize in 15 minutes and (schedule to) run, as needed, saving you hours of work compiling all the information that is already known, and linked. The only thing you should have needed to do was edit the executive summary to contain a few expert notes on the situation and expectations based on team dynamics and broader organizational knowledge the system didn’t capture. In other words, your three hour effort should have been a 30 minute effort that started with a 5 minute scan of the auto-generated report, a 20 minute edit and augmentation of the executive summary, and a final 5 minute proof.

In other words, the work that took you four (4) hours and 15 minutes should have taken you about 35 minutes. And that’s only because one of the reports was being presented to the C-Suite and needs a human touch and review.

But because the average amoeba has more “artificial intelligence” and “automation” than an average Procurement platform, you had the privilege of spending yet another half workday as a Procurement Zombie.

* A few providers are actively working towards the key next generation capabilities we outlined in our * series, but the majority of platforms on the market today are still based on processes and capabilities innovated a decade ago. In internet time where even the largest provider will roll out bug fixes, patches, and minor updates on a quarterly cycle, that’s a professional lifetime!

13 Reasons your RFP Scoring Sucks


Today we welcome another guest post from Brian Seipel a Procurement Consultant at Source One Management Services focused on helping corporations understand their spend profile and develop actionable strategies for cost reduction and supplier relationship management. Brian has a lot of real-world project experience in supply chain distribution, and brings some unique insight on the topic.

The most thorough, best designed RFP questionnaire counts for nothing if Procurement can’t interpret the results. Proper submission scoring is critical, yet many Procurement Pros commit at least a few mistakes that seriously damage their ability to assess RFP responses.

I’ve seen my share of such mistakes over the years, and work with clients to clear them up before it’s too late. I’ve included the worst offenders, “The Unlucky 13”, below.

How many did your last RFP fall victim to?

Evaluating Questions

1. Questions aren’t weighted (or aren’t weighted properly).

Not every question is created equal. Consider how important one response is versus another. Critical questions should receive the lion’s share of total weight. I recommend starting at a high-level, assigning weight to each category of questions. Once done, delve into each category to distribute this weight to each individual question.

Not every question needs to be scored – some are for information gathering only. However, if you notice too many unscored questions, evaluate whether they all need to be included in the first place.

2. “Kill switch” responses aren’t treated as such.

On the subject of weight, some responses are so heavy that the wrong answer can (and should) disqualify a participant out of the gate. If an unacceptable answer invalidates a proposal, don’t bother weighting it – call out the answer as grounds for dismissal.

For example, one critical question may ask for confirmation that a respondent can handle required volumes. If any responses indicate a supplier can’t, no amount of weight would suffice – they simply are no longer viable.

3. Scoring is overly simplistic.

True/false questions are easy to understand and score, but too many of these cause problems in the long run. Odds are your suppliers will end up looking too similar if the bulk of responses fall into simple yes/no buckets.

4. Scoring is overly complex.

On the other side, some scoring systems end up too complex to be reasonably applied. I’ve seen scores range from 1 to 20. On paper, this appears to allow fine-tuned scoring. In reality, I’d challenge anyone to properly differentiate a score of “12” from “13.”

Evaluating Responses

5. Questions from participants go unanswered.

Your questionnaire may seem clear to your team, but chances are good that one or more participants either don’t understand your intent or don’t have the background information from you to properly answer.

Every RFP should include chances for Q&A with participants. If you don’t provide this opportunity, responses will hinge on assumptions made by participants – enough assumptions, and the end result may not align at all with your requirements.

6. Questions to participants go unasked.

The same is true on the other end. If a response is unclear to the scorer, then clarification should be sought. Otherwise, the scorer is left to make assumptions in order to interpret a response.

7. The wheat wasn’t separated from the chaff.

Anyone who’s ever scored a Marketing RFP will be familiar with this concept. Ever read a 200 word reply to a question, only realize at the end that the participant never gave a direct answer? Quantity does not equal quality – a detailed non-response is still a non-response.

Evaluating the Scoring Process

8. Clear criteria aren’t provided to scorers.

Simply providing a scoring scale isn’t enough. If you ask for a score of one to five, be sure to provide concrete direction on what constitutes a one versus a five and every point between.

9. Too few scorers are included.

The more stakeholders involved in scoring, the less likely results will be thrown by huge score discrepancies. The team in charge of scoring should encompass any stakeholders who would interact with the supplier or the product/service in addition to Procurement.

10. Score results are averaged blindly.

As a counterpoint to the above, don’t simply average all scores together at the end of the initiative. Large discrepancies in scores may indicate that two or more scorers viewed either the question or response (or both) differently. Use big discrepancies as a flag to ensure everyone is on the same page and revise accordingly.

11. External factors influence results.

Score only what it within the questionnaire. Don’t award ghost points to an incumbent based on their years of service. Likewise, don’t give an artificial boost to a hungry alternate because they came in competitively on pricing. There will be time later to consider outside elements – for now, stay focused on specific questions and responses.

12. Internal factors influence results.

“What? Dave’s team gave these guys a ‘nine’?!” “Don’t worry about it – just give them a ‘two’ to even the score out.” I wish I made this example up. I did not. I’ve worked with stakeholders who doctored their own scores to offset other scores that they disagreed with. Needless to say, this artificial tampering helps nobody.

13. Scoring lacks consistency from one response to another.

Here’s a fun way to screw with your team. Give them a pop quiz by asking them to rescore one of their first questions right after they finish scoring all responses. I’d be willing to bet on the outcome – the scores won’t match. Maybe by a little, possibly by a fair margin. When we’re evaluating half a dozen or more participants by scoring potentially hundreds of questions… it’s easy to get fatigued or change your mindset midway through.

Many people like to score one participant fully, then moving on to the next. I recommend scoring on a per-question basis instead. Take a question, and score the response from each participant down the line. Repeat for the next question. So on, so forth. This way, you’ll be in the same frame of mind and consider each response on the same standing.

Do your RFP justice – you worked hard to develop it and marshal participants through it to the end. Before working through responses, sit down with your team and review your strategy for evaluating the results. And make sure everyone is on the same page when it comes to avoiding the mistakes above.

Thanks, Brian!