Fail Fast, Fail Cheap applies to your career, too.

January 26th, 2010 by Andrew Swenson in career, life
work

image credit: Joe Loong

To be honest, this post has less to do with failure and more to do with personal innovation from within the corporate structure—the struggle to make change happen, to get your ideas implemented if you aren’t in a senior leadership position.

The Math of Fast and Cheap

In 2007, Doug Hall suggested that businesses should Fail Fast, Fail Cheap when it comes to innovation. Specifically he showed the business sense of failing quickly and cheaply:

If it takes six months and $100,000 to take a product from idea to customer reaction, then at best you’ll get two cycles in a year. However, if you can do a complete cycle of learning in a week for $1,000, you can get 52 cycles in a year at about half the cost.

Actually, if you do the math right, it’s about one-fourth the cost.

In any case, Hall’s point is that you should try new ideas often and on a small scale because you can’t know exactly how an idea will turn out until you try it.

Simply put, this type of rapid iteration that drives innovation. With each iteration you learn, and with each cycle of learning, you get closer to making something work.

What about my career?

Failing fast and cheap is well and good for product development, but what about your career? Consider the following adaptation of three tips to decreasing the cost of failure by Scott AnthonyManaging Director of Innosight Ventures:

Anthony: “Lower the costs of experiments”

Me: Gaining support for your ideas at work may not cost you much money, but it certainly costs you time and effort. To prevent too much of your time from being lost, your first pitch shouldn’t be super polished. It should be “good enough.”

Never blindside your director or CEO with a written action plan, no matter how well researched.  Despite your good intentions and solid argumentation, this approach is too easily dismissed. Trust me, it’s happened to me twice in my professional career (you think I’d learn).

The point is to find the sweet spot where your research and verbal pitch are “good enough” to get your foot in the door. Once you’re in, then work on that formal brief. This is will save you oodles of time in the long run.

Anthony: “Change the order of experiments.”

Me: When pitching your ideas, don’t start with your enormous, big idea goal. Instead, start with something smaller. I’d recommend asking yourself, “what simple solution would make others’ jobs easier?

If you find a way to remove an obstacle your coworkers are presently dealing with, they’ll be more likely to support you when pitch a bigger idea down the road.

Anthony: “Increase the pace of decision making”

Me: One of the most effective ways to sell an idea is to build a prototype. If, however, the prototype isn’t producing some kind of results in relatively short order, consider it may be the idea, not the prototype that’s at fault.

Also consider that the big idea you’ve been pitching for 8 months may not be worth all of the effort you’re putting into it. It doesn’t mean you should abandon your big idea if it isn’t adopted right away, it means you should recognize when a pitch has failed, regroup, shift the order of your experiments, and come back to you big idea later.

This way each cycle of learning can bring you closer to selling your big idea.

What would you add?

When it comes to pitching your ideas at work, how do you decrease the cost of failure?

Please share!

-Andrew

*image only:

There is a Creative Commons license attached to this image. AttributionShare Alikeimage credit: Joe Loong (joelogon on Flickr); original here

Related Posts

  1. The Paradox of Constant Connection
  2. Age Discrimination isn’t just for Grandpa (Guest Post)
  3. Gen Y: Made for Collaboration; Time-Clock Incompatible
  4. To Gen-Y: Part of the reason your ideas are ignored

Tags: , , , ,

  • Excellent post and topic Andrew and the comments by your audience really add to the value here. I have pitched and executed on a lot of projects internally in a corporate structure like you describe here. Expanding on your point about not starting with a big enormous idea another way to look at this is to focus on getting an initial achievable outcome. The bigger goal, while exciting and sometimes game changing, draws more attention than it can be worth. You either won't likely have the resources you need or if the failure is large everyone sees it.

    The achievable outcome also gives you something to point to when you want to raise the visibility of what you are doing and get support for expanding whatever the idea is. Saying "look what I did in a limited way, the outcome was X" gives you credibility when you walk into the C's office to discuss how to get to the next level, ask for more funding, etc…

    To expand on your point about pitching your idea and not blindsiding a senior exec it’s important to know why they don’t like to be surprised. One reason is that they didn’t think of the idea. The other is that they may be put off that you are spending time on something they don’t understand and/or don’t what you to focus on that is not in line with whatever their plan is.

    This leads to the topic of agenda. Virtually all people are motivated by some type of an agenda. Keep that in mind and use it to your advantage if you decide to move on a project that isn’t sanctioned or approved by higher-ups. Some companies value unsolicited innovation and unfortunately others do not. If you understand a specific agenda of those above you AND can tie your project to that agenda you virtually always can get support for doing something (growing revenue, reducing cost, expanding markets, whatever).
  • abbyannette
    What a great post! I've been trying to read it all day, if for no other reason than I thought the graphic you chose was awesome. :) Turns out the content is too. I'd also add a few thoughts.

    Getting one good idea out there will allow more trust for the ideas to follow.

    I always go with verbal pitches first too, and my company rarely (until now with IT red tape) asks for a large formal brief unless it costs BIG dollars. When that does happen, our PR/AD firm usually creates that kinda stuff for us anyway, or the director/vp/svp of a department (which I am not).

    I'd also say that your boss should be your advocate for new ideas. Get them on your side and they'll push it through management, and usually more importantly, accounting.

    Just a take from a big company girl.

    I also love what Jason said about "good enough." I am, and many of us are, such a perfectionist that I struggle to begin for fear of failure and wanting my results to be perfect. Sometimes you just need to get something good enough out there.

    Also, an example. I decided to do this one social media campaign. It was a bit rushed and many road blocks came up. Needless to say, it was the least successful one I've ever done. I learned from it. It was short lived. We all moved on and no one cared. Every project/idea will not always be good. No one is ever 100%.

    Thanks for your words Andrew. Always well processed, well spoken and different from the regular bullshit being posted elsewhere. :)
  • "We all moved on and no one cared."

    I think that statement is probably the wisest thing that's been said on this post so far. I'm like you when it comes to perfectionism. The "good enough" lesson is probably one of the hardest for me to learn.

    But I wrote it down. "We all moved on and no one cared." I think I'm going to pin it to my cube wall.
  • Failing is all about perception... What does it really mean? :)
  • Sheesh...

    I think in this case it means getting that big rubber "NO" stamp that sits on your boss's desk smacked across your forehead.
  • Great post Andrew. I think the concept of lowering the cost of experiments is a great one. I've been fortunate in that the new launch I've been working on has been thoroughly tested on my own blog and I've proven conceptually that it has demand. I think another thing is that you have to be willing to experiment and "ask for forgiveness, not permission"
  • Experimenting in a safe place (like your blog to prove concept) is a brilliant idea. In fact Hall suggests that we should build one of two types of "good enough" prototypes, those that "look like" or "function like" what we're trying to sell.

    I've heard the "ask for forgiveness, not permission" maxim before, and I always want to add a line to it: "just make sure you're right."
  • The post and Jasons' addition are both on the dot!

    One more tip to help cross over if you're afraid to be rejected..
    I've worked for a multinational and, well... They're often not so interested in innovation unless it earns them instant money. Innovative cost reduction somehow doesn't interest them - they just cut (something from) the budget ;)

    So just go ahead with it. Don't ask for approval. If you feel uncomfortable with that, ask for approval but don't wait for it. Ignore roadblocks, budget jams and all that. If your idea is grand and works out that way, you will get no hussle from your manager, but rather the pat on the back.
  • I can't believe I forgot to mention the "It is better to ask for forgiveness than permission" mantra! It is a gutsy move, but (if you are smart) the risk is well worth the reward. Great addition Bas!
  • Thanks! Never been quoted as being a spiritual leader before ;)
  • Bas,

    Your method requires a lot of hutzpah. If it works, great...but if it fails you're completely on the hook, alone.

    But who ever achieved greatness by doing what's safe, right?

    I appreciate your willingness to put your head down and enact your idea with a less than immediate concern for consequences, but I think there are some things that require support from superiors in order to work.

    For example, I once suggested on this blog that we should get rid of informational meetings and use online forums instead. But if your superiors hold informational meetings, you're stuck going to them until you can convince them to try something different.

    I'm just curious, has your method ever backfired? Maybe I'm just too much of a chicken to be comfortable with it.
  • Are you actually on the hook when it fails? Think of yourself as my manager. Say I'm a marketeer with an annual budget of 30.000 dollar.

    Consider these options:
    A. I spend 10k and 3 days of my time on a regular promotion that gets little result
    B. I try an "on the edge of the box" (see Seth Godin) experiment for two weeks. It fails completely and costs the company 4k

    What's worse? Sucking at your job (option A) or growing beyond your job and trying out new ways (option B)? Even if we take the loss of time in account, option B is still the cheaper way. If the idea is good, but your approach wasn't, you have about 4k left to give it another try before your ass is on the line.

    And as you pointed out yourself, if you are able to keep your idea small and to the point, it won't be a costy business. Hell, to compensate your time you can always stick in the office an hour longer. See if your manager dissaproves of that ;)
  • Alright. Point taken.

    Thanks for helping me think through that.
  • Great points here Andrew. I think the one point that stood out for me (and that I learned the hard way from) is that "Good Enough is... Good Enough". Chasing that remaining 20% of business will likely take up 80% of your resources. It is (almost) never worth it.

    The only action plan anyone should have that early on is a big wad of silly putty because that is the only thing that could possibly be flexible and fluid enough to accommodate the onslaught from C-Level. I have been through this on more than once as well.

    The only way I have found to decrease the 'cost of failure' of ideas at work is to:

    - Split Test- Instead of banking on (what I think is) the top idea, any investor will tell you: DIVERSIFY.

    - Shoot Holes in it yourself- Think of EVERY SINGLE THING C-Level will be concerned about, get second and third opinions before pitching.

    - Simplify, Simplify, Simplify- "Feature Creep" does not only apply to software. Stick to the core issues, don't try to change/fix everything with an all-in-one-the-last-tool-we-will-ever-need-'turnkey'-solution. Focus on one step, one change, one issue at a time. Period.

    Great Post, t(h)ink on.
  • Also, I'm still chewing on your point that "Chasing that remaining 20% of business will likely take up 80% of your resources. It is (almost) never worth it."

    Now I'm all disrupted and not sure what I think. Thanks for that.
  • By the way, everyone should head over to Jason's #FAILweek: http://bit.ly/FAILweek

    I think my subconscious led me to think about failure, and I probably should have plugged you in the post. Sorry for letting that slip.

    Secondly, I'm totally with you on getting second and third opinions. It's important to have people on board with you, who support your idea and who can help you make it better.

    It's easy to say no to one person. It's harder to say no to a department.

    Thanks again for stopping by Jason.
blog comments powered by Disqus