Successful digital transformation is less about a single technology choice and more about how strategy, leadership, and culture come together. Key drivers include: 1. **A clear “north star” narrative** A Deloitte study cited in the article found that a straightforward, compelling north star narrative is critical to success for **38% of executive respondents**. This narrative aligns digital initiatives with the broader enterprise strategy so teams don’t chase the latest hype (AI, cloud, metaverse) without a business anchor. 2. **Active leadership commitment, not just sponsorship** When a chief transformation officer contributed an additional **15% of their time** to the program, the probability of success improved by **about 16%**. Leaders need to invest real time and energy, not just approve budgets. 3. **Meaningful, business-first communication** IT leaders often jump straight into technical requirements. The article warns this creates a “digital trap,” where teams lead with a single technology instead of the business problem. Using a common language around digital imperatives and value measures helps align business, technology, and operations across the C‑suite. 4. **Measured financial commitment** About **50% of surveyed organizations invest between 1% and 5% of annual revenue** in transformation programs. The point isn’t just spending more, but investing consistently in the capabilities that support the strategy. 5. **Data-driven oversight via dashboards** Research from the MIT Center for Information Systems Research highlights that organizations using dashboards to track how value is created over time are more likely to succeed. Dashboards should: - Monitor value and outcomes, not just project status - Track organizational and individual capabilities that enable digital - Be supported with persistent communication about their purpose, to overcome cultural resistance 6. **People, skills, and culture as core levers** Examples from Saatva, Honeywell, Charles River Laboratories, and Arup show that success depends on: - Upskilling existing talent and aggressively training high‑potential employees - Creating safe spaces to experiment and learn (e.g., agile practices, seed funding for cloud experiments) - Empowering teams and removing impediments rather than directing every move 7. **A mindset that transformation is ongoing** Leaders quoted in the article emphasize that transformation is a continuous process. The pace of change means there is no “end state”; organizations need to keep looking for the next way to better serve employees and customers. In short, digital transformation works best when it is guided by a clear strategy, backed by committed leadership, measured with the right data, and enabled by empowered, continuously learning teams.

The article highlights several lessons learned the hard way by organizations that rushed vendor choices or under-specified their needs. Here are practical takeaways: 1. **Vet both the company and the specific product** VIA Metropolitan Transit in San Antonio implemented an AI-powered chatbot and a mobile ticketing app, but initially partnered with the wrong provider. The vendor: - Changed platforms midstream - Delivered a chatbot that didn’t work as expected A key learning: it’s not enough to check that the vendor has a good reputation overall. You also need to validate the **specific product**, especially if it’s new to the market. Actions you can take: - Ask for references specifically for the product and use case you’re buying - Go beyond vendor-provided references and seek independent customer feedback - Confirm the product’s maturity and roadmap 2. **Balance innovation with stability and scale** Both VIA and Saatva’s CDO stress the importance of choosing platforms that can scale and stand up to scrutiny: - Saatva leans toward **namesake platforms** over niche tools, even at a higher price, because they often bring: - Easier IT audits - Better SLAs - Stronger security and compliance - More experienced engineering teams This doesn’t mean avoiding smaller vendors entirely, but it does mean weighing the operational and risk implications carefully. 3. **Write RFPs that tell a story, not just a feature list** VIA changed its RFP approach when looking for a new mobile pass provider: - Instead of a long, itemized checklist, they wrote a **“slim RFP”** that described their vision for a mobility payment platform. - They explicitly asked for a partner with a strong, proven platform and integrations with third parties. Lessons for your RFPs: - Describe the business context, desired outcomes, and how the solution should fit into your ecosystem - Be clear about non-negotiables: performance, integration, security, and pace of delivery - Use narrative to attract partners who can co‑design solutions, not just tick boxes 4. **Assess the vendor’s ability to move at your speed** VIA’s second challenge was a partner that couldn’t move fast enough. They had many requirements and spent too much time waiting for responses. When evaluating vendors, probe for: - Their typical implementation timelines - How they handle change requests - The size and structure of their delivery team - Examples of how they’ve supported customers with similar complexity and pace 5. **Be realistic about risk and customer impact** VIA’s technology leader notes a desire to support small and midsize businesses, but also the need to consider risk to the business and customers. That balance should be explicit in your selection criteria. Overall, a thoughtful vendor and RFP strategy means: - Looking beyond price to long-term stability, integration, and compliance - Validating real-world performance of the specific product - Using RFPs to communicate vision and context, not just requirements - Ensuring your partner can move at the speed your transformation demands.

The article shares several concrete examples of how organizations are rethinking talent, culture, and work practices to support digital change. 1. **Shift internal roles to higher-value work** At Saatva, a luxury sleep company, digital transformation involved adopting more cloud-based and third-party services. This changed the nature of IT work: - Teams became **managers of services** rather than creators of everything in-house. - They moved from traditional QA to **crowdsourced QA** worldwide, giving them an “army of testers.” - The internal QA team now focuses entirely on **automated testing** and managing the crowdsourced queue. This freed internal resources to focus on higher-level, more strategic tasks. 2. **Invest aggressively in training and upskilling** Saatva’s CDO emphasizes being “aggressive with training” to get more from existing IT talent: - High-IQ employees can learn complex new skills if you invest in them. - Upskilling helps avoid turnover costs and preserves institutional knowledge. The takeaway: treat training as a core part of your transformation budget, not a nice-to-have. 3. **Embed agile as a culture, not just a process** Charles River Laboratories is using agile to change how work gets done: - They aim to bring technology to market faster in **iterative pieces**, using betas to test, learn, and improve. - Agile is framed as a way to **identify the right problem**, break it into small parts, and stay close to the customer through constant feedback. Their CIO stresses that: - Even the best technologies don’t implement themselves; you need skilled people who are continuously learning. - Teams must have a **safe space to experiment** and be empowered to use their skills. - Leaders should focus on **removing impediments**, not dictating solutions. 4. **Normalize collaboration tools and new ways of working** Honeywell’s chief digital technology officer oversaw a rapid shift to remote work for tens of thousands of employees just before the pandemic: - Everyone, including senior leaders, had to adopt tools like Zoom. - Over time, these tools became part of the culture, enabling new practices such as: - Virtual demos and presentations - Vendor meetings over video - A customer advisory board that leverages collaborative tech As offices reopen, Honeywell is balancing in-person interaction (e.g., relationship-building, first-time meetings) with thoughtful use of video to avoid unnecessary travel. 5. **Create structured experimentation with clear value reporting** At Arup, a global engineering firm, leadership wanted all 1,800 employees in the Americas region to feel part of the digital journey. They: - Introduced a design methodology based on four Ds: **discover, define, develop, deliver**. - Offered **seed funding** (from a few thousand dollars up to **$25,000**) for employees to experiment with cloud-based ideas, such as automation or new tools. - Removed friction by covering cloud costs (Azure, AWS) so employees could focus on learning and innovation. The only requirement: participants must produce a **value report** at the end, showing: - Time savings - New efficiencies - New skills gained - Potential reuse in other areas or projects This approach has led to: - Tools that replace manual, spreadsheet-heavy work with code - Use of high-performance computing to deliver some projects in **hours instead of days** 6. **Adopt a learning and experimentation mindset** Leaders quoted in the article highlight a few cultural principles: - Be willing to “screw up,” admit when something didn’t work, and move on. - Recognize that what you think customers want may not match reality; use feedback to adjust. - Accept that transformation is ongoing; there is no final destination. In practice, building the right digital culture means: - Redesigning roles so internal teams focus on higher-value work - Funding and rewarding experimentation with clear value metrics - Treating agile as a mindset centered on learning and customer feedback - Using collaboration tools to reimagine how work gets done - Leading with humility and a long-term view that digital change is continuous.