According to MuleSoft, what action should an IT organization take regarding its technology assets in order to close the IT delivery gap?

According to MuleSoft's core philosophy, the "IT delivery gap" is the disparity between business demand for new projects and IT's capacity to deliver them. The recommended strategy to close this gap is to move away from custom, point-to-point projects and towards building an application network of reusable assets (APIs). A central repository, such as Anypoint Exchange, is a critical component of this strategy. It makes these assets discoverable, documented, and easily consumable, enabling developers and lines of business to self-serve and accelerate project delivery through reuse, thus closing the delivery gap.

A. Creating weekly approval meetings introduces bureaucracy and friction, which would slow down development and widen the IT delivery gap, directly contradicting the goal of agility.

C. Hiring more staff is a linear solution to an exponential problem. MuleSoft advocates for increasing efficiency and scalability through asset reuse, not just increasing headcount.

D. Focusing on custom, non-reusable assets is the traditional project-based approach that MuleSoft identifies as a primary cause of the IT delivery gap and technical debt.

---

1. MuleSoft Official Whitepaper, "Closing the IT delivery gap": This document outlines the problem and the solution. It states, "To close the IT delivery gap, IT must shift its role... This is done by exposing the organization’s data and capabilities as a network of APIs that are packaged as discoverable and reusable services." This directly supports the need for a discoverable repository. (See: Section "The solution: API-led connectivity", Paragraph 1).

2. MuleSoft Documentation, "Anypoint Exchange": The official documentation describes Exchange as the central hub for assets. "Exchange is the marketplace for connectors, templates, examples, and APIs... You can use it as a private repository for your organization’s assets, making them easy to find and consume within your organization." This confirms its role as the central repository for discoverability. (See: Anypoint Exchange > About Exchange).

3. MuleSoft Official Blog, "What is API-led connectivity?": This article explains the methodology. "With an API-led approach, these assets are not built as one-off projects. Instead, they are built with the intention of being reused... These APIs are then published to a platform like Anypoint Exchange, where the rest of the organization can discover and use them." (See: Section "How does API-led connectivity work?").