Introduction
Organizations often jump directly into building new solutions.
Before doing so, it may be helpful to pause and ask a few important questions.
1. Does a Solution Already Exist?
The fastest solution is often the one that's already available.
Before building something new, investigate whether an existing solution can meet the need.
2. Can an Existing Solution Be Extended?
A solution may not meet every requirement today.
However, a small enhancement may be easier and less expensive than creating a completely new system.
3. Can Components Be Reused?
Many organizations possess valuable building blocks.
Workflows, reports, databases, templates, and integrations may already exist.
Reuse is often more efficient than recreation.
4. Is the Problem Clearly Understood?
If stakeholders cannot clearly explain the problem, development should probably not begin.
An unclear problem almost always leads to an unclear solution.
5. Is Custom Development Really Necessary?
Custom development introduces long-term responsibilities.
Someone must support, maintain, secure, and update the system.
In many cases, configuration may be preferable to customization.
Closing Thoughts
Building something new should be the last question, not the first.
