Oracle AppsLab: Why 2.0 Didn’t Start in the Enterprise
Phil
· 2 years ago
Excellent description of this issue. I'd add a couple more things:
1) Enterprise software is a long train. It's 2 to 3 years from when work starts on a product until it ships to customers. What did wikis and blogs look like 3 years ago?
2) Enterprise software can't fail in the marketplace -- for a large company like Oracle, if your products are good, they can't be great because there's more risk in being great. Apple didn't release revolutionary OS X until MacOS 9 became terrible, Microsoft didn't release revolutionary Office 12 until most of there customers were still on Office 2000 (we are). It's not gutsy for MS, it's necessary to stay alive. For every 1 good wiki, there are 10 terrible ones, so not having one is better than having a terrible one if it's not something your customers demanded when you started development.
Gordon Taylor
· 2 years ago
Thanks Paul,
Having just left the world of enterprise software to try to 'code the new world', your post summed up pretty much everything that led me here.
All Comments
1) Enterprise software is a long train. It's 2 to 3 years from when work starts on a product until it ships to customers. What did wikis and blogs look like 3 years ago?
2) Enterprise software can't fail in the marketplace -- for a large company like Oracle, if your products are good, they can't be great because there's more risk in being great. Apple didn't release revolutionary OS X until MacOS 9 became terrible, Microsoft didn't release revolutionary Office 12 until most of there customers were still on Office 2000 (we are). It's not gutsy for MS, it's necessary to stay alive. For every 1 good wiki, there are 10 terrible ones, so not having one is better than having a terrible one if it's not something your customers demanded when you started development.
Having just left the world of enterprise software to try to 'code the new world', your post summed up pretty much everything that led me here.
Gordon :)