1. Have a level of cultural and organizational maturity that supports SOA goals
2. Ensure there is an appropriate balance of investment in shared assets and activities that might only realize benefits in the longer term
3. Organizational separation between provisioning and solution assembly
4. Create a Service Portfolio that is the inventory of enterprise assets from which projects source the capabilities they require
5. Continually assess where you are on the SOA Maturity curve and other appropriate process maturity models
6. Put clear management direction in place for SOA
7. Enjoy the luxury of already having a portfolio of modular systems, built on an inventory of shared components
8. Promote sound software engineering discipline that ensures reuse, consistency and traceability and applied best practices such as component-based development (CBD)
9. Focus SOA attention based on a real compelling event, such as a merger or terminal decline, that instigates strong motivation to re-engineer the portfolio
10. Put a good IT governance framework in place

Things companies can do from the outset to successfully map their way through a mashup:

• Discover business needs in terms of data intersections.
• Build relationships with trusted third-parties from which services, data, and UI artifacts can be shared.
• Involve sales, marketing, and executive management in the process of understanding how your organization’s mashups can be applied.
• Think in terms of flexibility, governance, and security throughout every step of the development process.
• Put into place a process for continuous evaluation and refactoring of mashup components.