Consider this quote from Guy Kawasaki's "Rules for Revolutionaries"...
"As a rule of thumb, revolutionaries should strive to make the optimal solution feasible -- as opposed to making the feasible solution optimal."
Get it out there. Iterate. Learn as you go. The common mistake to interpreting this basic concept is to think that it's ok to put crap out in your market. Whether your market happens to be a paying consumer base or an internal corporate associate group is irrelevant. This is the power of an Agile development lifecycle -- making possibilities real. Over 50% of software functionality is wasted! That being true, then move away from the natural calling for a perfect, turnkey solution. Defined well, perfection doesn't exist. Churn. Try. Learn & Burn. Whatever you want to call it, live the waffle mantra (just do it -- ok, a stretch on the obscure reference.)
The concept here is critical and I can't stress enough the application of this learning to things above and beyond software development. Consider your stereotypical "project management" approach to any initiative that you may take...gather all requirements; understand and document all that your customer wants; translate that into a perfect solution; start execution. Waste. It's an enabler to those that are uncomfortable with uncertainty and trust. Push thinking to the highest priority that is needed, build it, and reassess. You'll make that optimal solution feasible by making something happen. Don't wait. When it comes to value to market, remember what is true in the long run...
Comments