Last Updated on 21 September 2023 at 23:10
Every technology investment should ideally translate to tangible business benefits: increased sales, improved customer experience, or enhanced operational efficiency. From a holistic organizational perspective, every technological initiative must, or should, directly or indirectly contribute to the business’s success.
Tools like ROI calculators or performance metrics can help quantify the impact of technology initiatives.
For example, after implementing a new CRM system, a retail company might track metrics like customer engagement levels, repeat purchase rates, and customer feedback to gauge the system’s effectiveness. However, not all technology benefits can be quantified, especially when it comes to innovations that are ahead of their time. While this is true, having clear metrics still provides direction and helps in making informed decisions.
Vendor Selection — One Step at a Time
Selecting the right technology, however, is not a straightforward task. It requires a systematic approach that aligns with the organization’s unique needs and goals. In my years of consulting, I have seen businesses thrive or suffer based on their vendor choices. It is not a decision to be taken lightly. The right partner can be a catalyst for growth, while the wrong one can become a persistent and annoying bottleneck.
Choosing a technology vendor is a critical decision. Beyond the immediate functionality of their products or services, factors like vendor reliability, support, scalability, and integration capabilities play a crucial role. A classic example is the early days of Customer Relationship Management (CRM) systems. Many companies invested heavily in CRMs only to find them too complex and cumbersome for their needs.
So, it is essential to look beyond the sales pitch. Engage with current clients of the vendor, conduct pilot tests, and ensure that the solution can scale with your organization’s needs. Then, select technology solutions that align with your requirements. For instance, a global e-commerce giant like Amazon requires robust cloud infrastructure, while a local boutique might prioritize a user-friendly point-of-sale system.
The right technology partner can indeed be a catalyst for growth. They can provide not just a product but ongoing support, insights, and collaboration that enhance the organization’s capabilities.
For example, Salesforce’s partnership with companies across various industries has often led to increased efficiency and customer engagement, driving growth not only for themselves but also for their client base.
Here is a generalist blueprint to guide you through this critical process.
1. Needs Assessment: Understanding What You Really Need
- Defining Objectives: Start by defining what you want to achieve with the new technology. Is it to enhance efficiency, improve customer experience, and foster innovation ?
- Gathering Data: Utilize surveys, focus group discussions, SWOT analyses, and other methods to understand the specific technology and operational needs and challenges of different departments.
Most successful projects are those grounded in robust data. It is the difference between shooting in the dark and taking a calculated informed shot.
2. Vendor Evaluation: Choosing the Right Partner
- Reputation and Reliability: Look beyond the price tag. Investigate vendor reputations, customer testimonials, and track records.
- Alignment with Needs: Ensure that the vendor’s product aligns with your specific needs and organizational culture.
It is important to look beyond glossy marketing materials. I advise you to investigate vendor reputations through independent reviews, customer testimonials, case studies, and real discussions based on your challenges and needs. While reputation is a strong indicator, it is also essential to consider the vendor’s responsiveness, flexibility, and willingness to adapt.
Ensure that the vendor’s product can be tailored to your specific needs. For example, a CRM system might be feature-rich, but if it does not integrate seamlessly with your existing systems and processes, then its utility diminishes.
Sometimes, instead of finding a vendor that aligns with current needs, organizations should look for vendors that challenge them and introduce them to new ways of thinking. While this approach can lead to innovation, it is important to ensure the organization is ready for such a shift. Over the years, I have observed that most successful vendor and technology partnerships are built on mutual respect, transparent communication, understanding of different points of view, and a shared vision for the future. It is not just about the product or the solution — it might also be about shared growth and evolution.
3. Proof of Concept (PoC): Testing Before Implementing
- Small-Scale Testing: Before a full-scale implementation, testing the chosen solution on a smaller scale can provide valuable insights.
- Identifying Challenges: This stage helps identify potential challenges and assess whether the solution delivers the expected benefits.
Sometimes, this step is seen as an unnecessary delay in implementation. However, as the adage goes, ‘Measure twice, cut once.’ The slight delay at the onset can prevent significant setbacks later on.
The insights gained by the use of small-scale testing can prevent costly mistakes and ensure a smoother rollout. Indeed, the Proof of Concept (PoC) stands as a sentinel, ensuring that organizations do not dive headfirst into potentially costly implementations. Organizations must see this as a bridge between a theoretical solution and its practical application, offering a glimpse into the project’s future.
For instance, before SpaceX launched its Falcon Heavy rocket, numerous small-scale tests and simulations were conducted to predict and ensure its successful launch.
When Tesla was developing its self-driving technology, extensive testing helped identify challenges related to sensor reliability, decision-making algorithms, and real-world traffic conditions. This proactive approach allowed them to refine the technology before launching it to the public.
Every technology solution, no matter how perfect it seems on paper, will have its set of challenges and failures. The PoC stage serves as a diagnostic tool, helping organizations identify potential pitfalls, bottlenecks, or inefficiencies. For example, when introducing a new software solution within an organization, a PoC can reveal compatibility issues with existing systems or potential training needs for staff.
This stage is not just about identifying problems but also about understanding whether the technology truly delivers the anticipated benefits. It is mostly about a reality check, ensuring the technology solution aligns with organizational goals and delivers tangible value.
📥 Download eBook, pdf, or receive a print paperback
This post is a concise extract from our latest business publication.
We recommend acquiring the complete book “The Business Snyergy Blueprint — Creating a Powerful Ecosystem for Organizational Growth“. This book is for you if you seek actionable insights and industry-specific strategies. Dive into detailed case studies, expert analyses, and proven methodologies tailored for today’s dynamic business landscape.
You can download this book as a .pdf or Kindle format or receive a print paperback format.
FinTech Wealth Management expert with 30 years of successful track record, from Unicible/BCV to Odyssey and Temenos, plus hundreds of important banks across EMEA, APAC, and NAM.
► Background — from C-language code to C-suite in 30 years
• WealthSuite Triple’A Temenos TAP Plus expert
• crisis & change management
• complex multi-level project – program – portfolio management
• process architecture & governance, process optimization, BPO
• financial services software engineering FS FinTech
Career start as an innovative software engineer in startups â–º to strategic advisory & turnaround for Tier1 & Tier2 Banks at senior C-level.
• T-shaped mastery of the latest key technologies, business, and operational practices in retail banking, asset management, core banking, PMS.
• Keen focus on improving productivity, client retention, and revenues through expertise in Program Management, Process Governance, and Optimized Delivery, augmented by know-how in complex issue resolution and value-driven E2E end-to-end implementations.
Temenos Practitioner accredited across WealthSuite and FrontOffice domains (FO, PM, TTI). Certified modules include Scripts & Formats, Implementation Methodology (T3TIM), Channels PM, APA Attribution, Constraint Management, Order Management, Data Security, WealthSuite Portfolio Management, and T24 Triple’A Interface. The Practitioner status anchors Didier’s capacity to operate as a Transformation Director, bridging certified product mastery with execution governance and program recovery.
Disclaimer —
The views and opinions expressed in this publication are those of the author, Didier Debbaut, and do not represent the views, positions, or policies of Temenos AG, its affiliates, clients, or partners. All information is shared in good faith and in the spirit of professional exchange, as part of an open, constructive contribution to the FinTech and WealthTech community.
Any technical references, opinions, or analyses are based solely on publicly available information and the author’s independent field expertise. They are offered for general informational and educational purposes only.
No confidential, proprietary, or non-public information related to Temenos products, clients, or business operations is disclosed or implied.
© Didier Debbaut — All rights reserved.
Learn when to choose High Availability, Fault Tolerance, or Disaster Recovery in Azure. Didier Debbaut maps costs, risks, and execution trade-offs.
Mixing #Agile with #Waterfall ? Think of it as a cake with the chocolatey structure of Waterfall and the creamy flexibility of Agile. The cherry on the cake is the best of both worlds, and this is how you can win at #software #development and #project #management.
The debate between Agile and Waterfall is not a zero-sum game. Each methodology has its merits and drawbacks, and the choice between the two is often dictated by the specific requirements and constraints of a project or program. However, for projects that demand both structure and flexibility, a hybrid approach can offer a balanced solution.
In practice, it is not about choosing between Waterfall and Agile; it’s about knowing when to use each. Structure and flexibility are complementary and not mutually exclusive. So, the next time someone tries to sell you on the “one true methodology”, remember: the most innovative solutions often come from combining the best of multiple worlds. It’s not about only waterfall or agile, but a lot of other methodologies, too.
Our latest publication explore the complex world of FinTech, focusing on the role of DevOps. Written by Didier Debbaut and Elena Debbaut, both experts in Software Wealth Management and Turnaround & Crisis Management, the piece aims to offer a comprehensive and nuanced understanding of DevOps’ strategic imperatives in the FinTech sector.
