How can CTOs maximize the value from vendor partnerships?
Short answer
CTOs can maximize vendor partnerships by clearly defining their needs and allowing vendors to propose tailored solutions. It's crucial to balance the vendor's offerings with the company's specific goals and capabilities.
CTOs can maximize vendor partnerships by clearly defining their needs and allowing vendors to propose tailored solutions. It's crucial to balance the vendor's offerings with the company's specific goals and capabilities.
Understanding Vendor Motivations
One of the first steps in maximizing vendor partnerships is understanding the motivations behind the vendor's offerings. Scott shared an experience with AWS, where they were invited to an executive business conference. The goal was to explore how AWS could support TaskRabbit's growth. "They're practically begging us," Scott noted, highlighting AWS's eagerness to assist ▶ 6:18. This eagerness is driven by AWS's belief that helping their clients succeed will, in turn, benefit AWS through increased usage of their services.
However, it's important to recognize that while vendors are motivated to help, their primary goal is to increase their own business. Brad pointed out, "But even helping me, I still have to do more work" ▶ 13:45. This underscores the need for CTOs to remain vigilant about the actual benefits versus the additional workload that may come with vendor solutions.
Defining Your Needs Clearly
To truly benefit from vendor partnerships, CTOs should clearly define their needs and communicate them effectively to the vendor. Scott emphasized the importance of framing needs in the language of a user story rather than jumping to technical solutions. For instance, rather than specifying a technical overhaul, CTOs might express a need to reduce cloud infrastructure maintenance costs. This approach allows vendors to propose solutions that are aligned with the company's strategic objectives.
Brad and Scott discussed the potential pitfalls of not having a clear understanding of what you want from a vendor. Scott mentioned, "We have to get clear on what's important to us. They'll help us with anything we want help with" ▶ 9:17. This clarity helps in avoiding the trap of being offered solutions that may not be suitable for the company's scale or current needs.
Balancing Vendor Solutions with Company Goals
While vendors may offer cutting-edge solutions, CTOs must evaluate these offerings against their company's specific goals and capabilities. Scott expressed concern about being presented with "level four solutions" when the company might still be grappling with foundational issues ▶ 11:20. It's crucial to ensure that the solutions are appropriate for the company's current stage and resources.
Brad highlighted the risk of vendor lock-in, especially when adopting proprietary technologies that could limit future flexibility. However, he also noted that the benefits of leveraging a vendor's full capabilities might outweigh the risks of lock-in, provided the solutions align well with the company's objectives.
Learning from Past Experiences
Reflecting on past experiences with vendors can provide valuable insights into what works and what doesn't. Both Brad and Scott shared anecdotes of vendor interactions that were less than successful, often due to misaligned objectives or the vendor's competitive interests. Brad noted, "the places where I could have used the most help from a bigger vendor," but often found the vendor's strategic goals conflicted with his company's interests ▶ 38:35.
These experiences underscore the importance of maintaining a clear focus on the company's goals and being cautious about the vendor's long-term intentions. It's essential to engage with vendors in a way that leverages their expertise without compromising the company's strategic direction.
Embracing a Customer Mindset
Scott pointed out the importance of shifting perspective from an engineering mindset to that of a customer. "Maybe I need to stop thinking about this like an engineer and start thinking about this like a customer" ▶ 0:00. This shift allows CTOs to express their needs more clearly, focusing on the outcomes they want rather than the technical specifics.
For example, instead of detailing technical requirements, a CTO might state, "Our cost of maintenance for our cloud infrastructure is too high. Can you help us solve that problem?" This approach invites vendors to propose solutions that are directly aligned with the company's strategic needs, rather than simply offering technical fixes.
Conclusion
Maximizing the value from vendor partnerships requires a strategic approach that balances the vendor's offerings with the company's specific needs and goals. By clearly defining their needs, understanding vendor motivations, and learning from past experiences, CTOs can effectively navigate these partnerships to drive their company's success. As Scott aptly put it, "Maybe I need to stop thinking about this like an engineer and start thinking about this like a customer" ▶ 0:00, emphasizing the shift in mindset required to truly benefit from vendor collaborations.