Center for Enablement (C4E) is a cross-functional team that is charged with enabling their organization to consume and get full value from their integration projects and assets. Learn the step-by-step guide on rolling out a C4E within your organization by following a successful customer example.

1. All contents © MuleSoft Inc.
Implementation Best Practices
Center for Enablement

2. All contents © MuleSoft Inc.
Agenda
2
• What is a Center for Enablement (C4E) and why do I need
one?
• What are the benefits of a C4E?
• How to set up a C4E?

3. All contents © MuleSoft Inc.
What is a C4E?

4. All contents © MuleSoft Inc.
Why do integration projects fail to realize full benefits?
4
Integration strategy
is often an
afterthought
Siloed project
execution
Limited focus on
building
organization-wide
capability in
integration
1 2 3
Projects run over
budget
Minimal reusability Low integration
maturity overall

5. All contents © MuleSoft Inc.
C4E: organizing differently to drive benefits of API-
led connectivity
5
Production
Reusable
assets
Central IT / LoB IT
Consumption
Feedback and
usage metrics
LoB IT, developers
Discoverable
Self-service
● Enables IT and business teams
● From Production-based model to
production-and-consumption-based
model
● Productize, publish and consume
reusable assets
● Encourage collaboration and self-
reliance while improving through
feedback

6. All contents © MuleSoft Inc.
What are the benefits of a C4E?

7. All contents © MuleSoft Inc.
Key benefits of a C4E
7
Shorter delivery cycles, i.e.,
time to market
Better adherence to
standards and best practices
Improved deliverable quality
Reduced project risk
1 2
3 4

8. All contents © MuleSoft Inc.
How to set up a C4E?

9. All contents © MuleSoft Inc.
Case study: Initiative background
9
● Create new revenue
channels, and increase
current customer
retention by modernizing
how the company
connects with customers
and partners
● Expose core business
services externally in a
secure, scalable manner
using APIs
● Use MuleSoft to deliver
APIs, transformations and
orchestrations
Business outcomes Technology initiative

10. All contents © MuleSoft Inc.
C4E Approach
10
1. Assess the
org
integration
capabilities
2. Establish
the C4E
operating
model
3. Build &
publish
foundational
assets
4.Evangelize
C4E
5. Drive
consumption,
and refine
based on
feedback
6. Measure
C4E KPIs
MuleSoft’s C4E approach

11. All contents © MuleSoft Inc.
1. Assess capability maturity
11
MuleSoft Capability Maturity Assessment for Customer
Governance
Community &
Evangelism
4
Operations
5
Architecture &
Standards
6
Delivery
7
Strategy
1
Organization
2
ProcessTechnologyPeople
3

12. All contents © MuleSoft Inc.
2.Establish the C4E operating model
12
Decentralization, increasing agile/devops and API-led maturity
C4
E
Project
A
Project
B
Project
C
C4
E
Project
A
Project
B
Project
C
C4E /
CoE
Model 1: Centralized
Integration
Model 2: Decentralized
Delivery
Model 3: Decentralized
Delivery & Devops
C4E Deliver & manage projects;
operate the platform
Enable projects to deliver; harvest and
drive consumption of assets; operate the
platform
Enables projects to deliver and
operate; harvest and drive
consumption of assets.
Project
Teams
Projects are ‘delivered to’ by
the C4E
Deliver and manage delivery Deliver, manage delivery AND
operate/own a federated platform
C4
E
Project
A
Project
B
Project
C
Core C4E Team
C4E Lead
C4E Architect
C4E
Developers/Ops
Executive Sponsor
API Team #1
Product Owner
Scrum Master
Business Analyst
Architect
Integration
Developer
Developers/Testers
API Team #2
ApI Team N
API Team #3
Virtual Team
3-4 FTEs
Customer Example

13. All contents © MuleSoft Inc.
2. Establish the C4E operating model (cont’d.)
13
● Staffing model: Virtual vs. Dedicated FTEs
● Funding model: LOB or central IT
● Architecture definition: C4E or project teams
● Production/Consumption model: define what a reusable
asset is, who produces it, who productizes it, who
consumes it
Additional Operating model elements

14. All contents © MuleSoft Inc.
3. Build & publish foundational assets
14
• Coding standards and guidelines
• Catalog of common API patterns
• First steps, onboarding, developer guides
• Performance tuning, profiling
• Microservices approach
Best practices and guides
• System API template
• Process API template
• Experience API template
• Security, encryption
• Logging, error handling
Templates
• Locations API
• Appointment API
• Orders API
• Other process APIs
APIs

15. All contents © MuleSoft Inc.
4&5. Evangelize C4E, drive consumption and refine
based on feedback
15
Webinars/
Brown bags
C4E Hackathons C4E surveys

16. All contents © MuleSoft Inc.
6. Measure C4E KPIs
16
Asset Creation &
Reuse
Developer
Engagement
Productivity
1 2 3
No. of assets produced
No. of assets downloaded
….
No. of projects using C4E assets
produced
No. of developers trained
….
Avg. time to delivery APIs
Total no. of defects
….

17. All contents © MuleSoft Inc.
How MuleSoft can help?

18. All contents © MuleSoft Inc.
Mulesoft has a service offering to help customers build the
C4E foundation
18
Catalyst Launch
● Align on business outcomes
● Deploy Anypoint Platform
● Projects delivered
● C4E foundation
● Talent foundation
● Internal support model

19. All contents © MuleSoft Inc.
Don’t forget the survey
19
• Why take the survey?
– Takes less than 2 minutes
– We value your feedback and apply it when deciding next year’s content and
speakers
– Surveys = Prizes!! Earn 55 points for a chance to win $250 in cash prizes
• See “Play To Win” in the Mobile App for details
• Where’s my survey?
– Log into the mobile app
– Click “Surveys” on the Tool Bar
– Find the relevant survey for this session slot

20. All contents © MuleSoft Inc.
Thank you!

21. All contents © MuleSoft Inc.
Establish the foundation Build to scalePlan for success Measure impact
Business
outcomes
Technology
delivery
Org
enablement
Catalyst Launch
Catalyst C4E Foundation
Catalyst Talent Foundation
Catalyst Scale Catalyst
Optimize
Catalyst C4E
Scaling
Catalyst Talent
Scaling
Catalyst C4E
Assessment
Catalyst Skills
Assessment