Robert made a good point, “Why don’t we drop this 2.0 business?”
We can’t, because there is something there, something that is fundamentally changing our world. Something that enormous is REALLY hard to understand, but we can see the effects of it every day.
Clayton Christensen has some early definition with his disruptive innovation. You routinely double and triple (or more) your users by offering what they want.
People who don’t understand technology say, “The key must be technology!” This gives me a new understanding of why so many IT projects fail. If the leader doesn’t understand both the business necessity and the technology, they keep trying to join the two together and missing. Think about what happens if you understand just one or the other.
People who don’t understand the changed role of pricing say, “We can’t lower our prices!”
People who don’t understand innovation say, “Let Steve Jobs do it!”
Perhaps the key is understanding what your users will want, what technology will be disruptive, how to make your pricing radically more attractive, and offer something that works much better.
And, as Mr. Loaf says, “Two out of three ain’t bad.”
A blog is a terrible thing to waste! Our next presentation is BlogLab - Improve Your Blogs! Thursday December 8, 8:30 am - 1 pm. Learn more at http://bit.ly/WMRBlogLab
Dick:
ReplyDeleteI can recall (painfully) an IT project including the functional areas of accounting, HR, Payroll, and Financial records. The project took 18 months - the first nine were just for planning.
The steering committee did the planning, the system folks ran parallel for 3 months. When we went live, the first payroll was mostly correct, although one employee got a check for 3 cents for his two-week pay and a person in housekeeping got one for $10,000.
Payroll got cleaned up quickly, but it took about four months to get the bugs out of the rest of the system.
During the planning the committee members were from a silo functional structure and did not know anything about the other areas. They planned multiple silos for an integrated system - glitches evolved from there.
Imagine if the various functional areas worked to integrate their needs before coding a system. That's a World 2.0 approach.