This project might be considered a success; it was launched on time, on budget, and has the correct functionality. But then the sales team, who are often on the road, are demanding that this functionality be available on their mobile phones. So, the IT team is now tasked with building a mobile app. But the developers building the app aren’t able to use any of the work that was done for previous projects. So they have to redo all the work, which in itself is not a great outcome.
Even though the developers know this is likely a short-sighted approach, they justify it given the typically intense time pressures. If there are consultants involved (as is typical), the problem gets worse, as they have little incentive to think about the long term. Over time, changes become very expensive or near impossible to make. But as change is constant, agility is now made very difficult. As you can see below, the familiar “spaghetti code” pattern begins to take shape.
This is fine, so long as you’re a rational actor making the trade offs and prioritizing.
Original source: What is API-led Connectivity?