Questions? (877) 643-7244
FutureNow Post
Monday, Sep. 17, 2007 at 7:32 am

“Good, Fast and/or Cheap”? Refuse to Choose!

By The Grok
September 17th, 2007

John Quarto-vonTivadar tells me there’s an old adage among software developers: You can have it Fast, you can have it Good, or you can have it Cheap. Pick Two.

In short, you can’t have it all. Try to have it all and you set yourself up for failure and a dead project.

Funny how we come to accept this as a perfectly valid philosophy when it comes to our development projects — especially funny when the fortunes of our online businesses are at stake.

Given the high project failure rate in our industry — over 70 percent, by some estimates — I wonder if this “Pick Two” philosophy is nothing more than a crutch; a shoot-yourself-in-the-foot way to shift the blame when things go up the Swanee.

Know what I think? It’s time for a “Pick Three” philosophy!

What idiot’s going to ask the customer — the person for whom you are developing a project — which of these three options they can forgo?

Of course the customer wants it Fast. How often do you hear this: “Sally, I see the ACME project (on which the future of this company depends) is 7 months overdue, but don’t worry. Just finish it off whenever you get around to it.”

Of course the customer wants it Good. “Hey, our people are certified with so many acronyms they can’t possible design poorly or write bad code.”

Of course the customer wants it Cheap. Whoever heard of wanting it expensive?

And, of course, no developer wants to end up with egg on his face when he’s linked to the option that was sacrificed.

But why is it that the customer is all too often excluded from the development equation? The clients for whom folks develop projects make decisions every day about balancing resources with needs. Can we really think they simply won’t be able to get it?

When all is said and done, the “Pick Two” philosophy is little more than a handy way to blame a 7-in-10 failure rate on having over-reached by hoping to attain the elusive “Pick Three”.

To add insult to injury, did you know that of the 30 percent of projects considered “successful,” more than 80 percent of their total project costs come in the form of “troubleshooting and maintenance” after the initial release? Which is to say, if you’re successful, your final project costs 5 times whatever you spent on it during development.

Shiver me timbers, mateys. This is madness!

Let me suggest a different approach; a win/win in which everyone plans for success. Forget Fast, Good and Cheap as your relative “success” metrics, and consider instead a project that is “On Purpose”.

This is the heart of Persuasion Architecture™. By sitting down with the customer and defining together what the Purpose of the project will be, we can establish a series of absolute — rather than relative — metrics, and we can clarify the issues of schedule and financial breadth of the project.

Our project will be “good” to the extent we achieve our Purpose. After all, when’s the last time you heard “Well, Tim, the project did everything we wanted it to… guess we should mark it off as a failure”? We guarantee the Purpose is always the focus by Wireframing the project.

Our project will be “fast” because the Purpose outlines a specific schedule for delivering the purposeful goals. Unless you live in Australia, doing sit-ups to show off the new swimsuit is much more effective when you begin in January than it is if you start training in July.

Our project will be “cheap” insofar as the budget allows us to meet those purposeful goal. Not a single line of HTML or code is written until we do all the hard planning and thinking work up-front — from defining Purpose to developing a Prototype (the Prototype itself being the final acceptance test).

By defining Purpose as our metric for success, we can identify exactly how we’ll go about achieving it, how long it will take, and the resources we’ll require before we begin.

My new adage for this approach: “On Time, on Budget, and on Purpose. Pick Three.”

Are your online Marketing projects being developed on purpose?

Add Your Comments

Comments (1)

  1. As a project manager in the software development world, I was taught this ‘magic triangle’ of time –> cost –> scope, and used it often b/c it was the easiest way to get high-paid exec stakeholders to understand that they couldn’t have it all. Of course, you CAN have it all with proper design and planning. But most stakeholders want it all mid-project–when the timelines are already slipping! So I don’t think it’s a crutch, I think it’s a expectation-setting tool.

Add Your Comments

 

Print this Article
Share

More articles from The Grok

Marketing Optimization Blog
FREE Newsletter Sign-Up
send it once every: