Downloaded 225 times
Uploaded byMuleSoft
The Blueprint for Change: How the Best Are Succeeding in Transformation
The document outlines a balanced approach to organizational transformation that prioritizes both project-led and platform-led strategies to facilitate effective change. It emphasizes the importance of the right operating model, core reusability, and the development of an enablement-centered IT infrastructure to increase delivery capacity and support business transformation. Key elements include establishing a Center for Enablement, leveraging APIs, and fostering a culture of decentralized ownership and agility.
More Related Content
Similar to The Blueprint for Change: How the Best Are Succeeding in Transformation
The Blueprint for Change: How the Best Are Succeeding in Transformation
- 1. The Blueprint forChange: How the Best Are Succeeding in Transformation Brent Grimes – VP Global Customer Success Nils Fernando – Customer Success Director May 2016
- 2. application network =the what operating model = the how
- 3.
- 4. Balanced approach requiresproject & platform accountability
- 5. Technology alone willnot deliver transformation 5 • The right operating model and organizational principles are critical • Two common patterns for successful transformation Balanced Approached Center for Enablement
- 6.
- 7. Balanced approach mostfrequently delivers transformation Option 1: Project-led Option 3: Platform-led Project 1 Project 2 Project 3 A B C D E F Project Timeline Team HW “MVP” P1 P2 P3 Log Audit Secur Platform Timeline Team HW “MVP” Log Audit Secur P1 Platform Components A-F Proj 1 Proj 2 Proj 3 ... P1 P2 P3 ... ... Balanced Deployment Project 1 Project 2 Project 3 A B C Project Timeline Platform Timeline “MVP” P1 P2 P3 Platform Components D-F ... Team HW Log Audit Use discovery process to identify foundational component sequencing
- 8. Balanced approach prioritizescomposability 8 Project-led Approach Balanced Approach
- 9.
- 10. Enables platform evolutionwhile delivering key projects Leverage a simultaneous project focus and platform evolution approach to enable sharing of resources by exposing core functionality via API’s Reference Architecture Project Backlog Proj 1 Proj 2 Proj 3 Core Services A B C Platform Timeline Project 1 Project 2 Project 3 A B C Project Timeline Platform Components D, E, F,… Balanced Deployment Approach Leads to • Embed core reusability via a reference architecture comprising of common patterns, templates, and best practices • Increase maturity with each project by building core business APIs and shared services that make data accessible at the edge of the enterprise for widespread consumption • Increase adoption of core API’s by establishing a repository and practices to share reusable resources Key Considerations
- 11. Every project addsvalue to the application network 11 Devs for next project Developer communities Inventory data Customer data Orders Customers Order data
- 12. IT’s absolute imperativeto change 12 DemandsonIT Time Today IT delivery capacity
- 13. Enabling IT tosupport business transformation 13 DemandsonIT IT delivery capacity Time Today
- 14. Success = materialincrease in IT delivery capacity 14 DemandsonIT Time IT delivery capacity Today Positive growth in delivery capacity Massive growth in delivery capacity Traditional project delivery Balanced, API-led delivery
- 15. Increased delivery capacitydrives increased value 15 Time Capability investment Capability payback Take away • Balanced approach supports capability development alongside project delivery
- 16.
- 17. An approach tounlocking your organization Mainframe FTP, Files Experience Layer: Innovation and digital products Process APIs: Agility and new value creation System APIs: Decentralized access to core assetsCentral IT LoB Dev/IT App Dev Accessibility & Ownership
- 18. The C4E isa new operating model for IT • Enablement over delivery • Not an ivory tower! • Decentralize to scale • Drive multi-modal / multi-speed integration Achieving de-centralization, federation and speed Without losing control Central IT LoB Dev/IT App Dev Accessibility & Ownership
- 19. Shifting the mindset…and why?
- 20. Business Enablement Business Enablement Business Enablement Local Project Leadership Local Project Leadership Local Project Leadership Center 4 Enablement Platform Architects/ DevOps Architects / API Architects / API Evangelists Platform DevOps Team Project Delivery Teams Achieving de-centralization, federation and speed Without losing control
- 21. C4E Capabilities, rolesand skillsets 21 C4E Platform DevOps Team Analysts Coaches and Evangelists Platform & Product Owners API & Platform Architects Lead & Sponsor Capabilities – The ‘What?’ Roles and Skills – Who?
- 22.
- 23. Catalyst Strategic EngagementModel 23 Business Transformation Programs Rapid Start Accelerate • Value mapping and analysis • Benchmarking • Core capabilities • Customer and partner enablement • Production to consumption • Platform scale MuleSoft Catalyst Leadership and advocacy: Customer Success Delivery and IP transfer: Training, Services, Support C4E Operating Model • Capability assessment • C4E Blueprint Planning Execution Outcome-driven engagement
- 24. Enabling a newIT operating model Production Agile Development, SDLC, DevOps, Microservices, APIs publish reusable assets Central IT or LoB IT Consumption Community enablement, asset discovery, self-service feedback and metrics LoB IT, SIs, App Dev
- 25. Think big, startsmall, build fast 25
- 26.
- 27. Enabling a newIT operating model Production Agile Development, SDLC, DevOps, Microservices, APIs publish reusable assets Consumption Community enablement, asset discovery, self-service feedback and metrics