In keeping with my wildly popular Service-Averse Architecture concept, which has been blogged about in French and Italian, searched in Google Japanese, not to mentioned blogged about twice on ZdNet by Joe McKendrick and once by Todd Biske, I note that the road to hell is paved with good intentions.
So I hereby present you my five ways to ruin your service-oriented architecture before it's even built, and some explicit instructions that will ensure that your organization is service-averse:
1. Don't ask the people who work at your company what applications they like and what they need and expect from their technology.
2. Don't commit enough resources to fully assess what legacy applications you have, and what works and doesn't work.
3. Add a new tool every time you need to generate a new kind of data.
4. Don't consider the open source community's excellent agility tools that are now finding their way into the enterprise.
5. Don't do SOA next week and not the week after. To quote Burton Group's Anne Thomas Manes, who did this great podcast with me and Joe McKendrick last week: "If you are unprepared to make the big changes that will need to be made in your organization, then you have to scale back your investment."