Click the diagram to open the interactive DA Browser, where you can learn more about the decision points and options of this goal.
Why This is Important
There are several reasons why this goal is important:
- A lot of good work has occurred before us. There is a wide range of assets within our organization that our team can leverage. Sometimes we will discover that we need to first evolve the existing asset so that it meets our needs, which often proves faster and less expensive than building it from scratch.
- We can reduce overall technical debt. The unfortunate reality is that many organizations struggle under significant technical debt loads—poor-quality code, poor-quality data, and a lack of automated regression tests are all too common. By choosing to reuse existing assets, and investing in paying down some of the technical debt that we run into when doing so, we’ll slowly dig our way out of the technical debt trap that we find ourselves in.
- We can provide greater value quicker. Increased reuse enables us to focus on implementing new functionality to delight our customers instead of just reinventing what we’re already offering them. By paying down technical debt we increase the underlying quality of the infrastructure upon which we’re building, enabling us to deliver new functionality faster over time.
Important Questions to Consider
- What guidelines should we adopt and follow?
- What technical assets, such as services and legacy systems, can we reuse?
- What existing data sources can we access?
- What practices and procedures can we adopt?
- What can we give back to the rest of our organization?
- Greater levels of reuse lead to lower costs, quicker time to market, and higher levels of quality.
- Reuse is hard—really hard.
- Paying down technical debt is critical to your organization’s long-term success.