top of page
Search

Decision Dilemma Solved: What to Avoid and Embrace in Solution Choices

Every choice you make has an end result," Zig Ziglar once said. This wisdom perfectly frames the critical decision-making crossroads faced by one of my clients, Client Y, a burgeoning enterprise in the financial and banking sector. Their dilemma: their existing system was not keeping pace with their rapid growth. They stood at a pivotal point, weighing three options, buy and customize a ready-made solution, build a bespoke system from scratch, or refine their current setup. Each path offered distinct benefits and challenges, and the chosen direction would significantly impact their operational efficiency and future scalability.





1. Evaluating the Current System


Our journey began with a thorough analysis of Client Y’s existing system. We dissected its capabilities, identified bottlenecks, and evaluated its scalability. It quickly became apparent that while the current system had served its purpose, it was straining under the growing demands of the business.


2. The Buy Option: Exploring Market Solutions


Our next step was to explore market-available solutions. The 'buy' option promised a quicker deployment with tested reliability. We assessed various platforms, scrutinizing their adaptability to Client Y’s unique workflows and integration capabilities with existing tools. However, the cost of customization and potential dependency on external vendors became a significant consideration.


3. The Build Option: Tailoring from Scratch


Building a custom solution offered an attractive avenue of tailoring every aspect to Client Y’s specific needs. Our team delved into designing a system architecture that would not only resolve current issues but also scale seamlessly with the company's growth. This path, while offering maximum control, posed risks in terms of development time, resource allocation, and the need for ongoing maintenance.


4. Improving What Exists: A Cost-Effective Approach


Improving the existing system emerged as a cost-effective and less disruptive option. We brainstormed enhancements that could elevate its performance to meet immediate needs. This approach, while economically appealing, raised concerns about long-term viability and the possibility of future overhauls.





5. The Decision-Making Process


Our decision-making process was methodical, involving stakeholder interviews, cost-benefit analysis, and forecasting future needs. We held workshops with Client Y’s team to understand their day-to-day challenges and aspirations. These insights, combined with our technical and market analysis, guided us towards a decision.


6. The Verdict and Implementation


Ultimately, we decided to take a phased approach. We started by incrementally improving the existing system to quickly address critical issues, planning a longer-term strategy to develop a custom solution. This approach balanced immediate needs with future-proofing the business, providing Client Y the flexibility to evolve without being hindered by their systems.


7. Reflections and Lessons Learned


This experience with Client Y reinforced a vital lesson: there is no one-size-fits-all answer in product management. The choice between buying, building, or improving is nuanced, dependent on a multitude of factors unique to each business. It highlighted the importance of deep analysis, stakeholder engagement, and strategic foresight.



Navigating the decision of whether to buy, build, or improve is a testament to the complex yet rewarding nature of product management. In Client Y’s case, our journey was not just about solving a problem but setting the stage for sustained growth and adaptability. This process exemplifies the intricate dance of decision-making that defines the heart of effective product management.


Comments


  • LinkedIn
bottom of page