Finding value in a C4E
Often, MuleSoft practitioners, architects, and delivery organizations will either dismiss the C4E or – best case – consider it a secondary or even tertiary concern. It is easy to understand why in the following cases:
- Higher priorities have been identified in the statement of work
- Budgets have been set and fixed during annual financial meetings
- The accounting department isn’t asking for much; they just want good data they can include on the salary reports
These short-term projects, the tactical fire drills, the siren call of the shiny object, and the drudgery of yet another governance project (YAGP) are more than enough to distract an organization from putting any effort into something that starts with “Center.”
Ironically, when companies disregard not just C4E but the activities and actions it recommends, an organization may exacerbate the problems they sought to fix through the adoption of an API...