The key is choosing a thin slice of workload that can be deployed through production to start delivering value, while meeting non-functional requirements and building skills. We (the IBM Garage team) have adapted our approach to develop innovative minimal viable products (MVPs) to apply to all types of new technology adoption. Too often, I’ve seen companies adopt a new technology platform with a ‘build it and they will come’ approach, and, for a variety of reasons, the planned-for workload never comes. ![]() My recommendation for adopting new technology is to focus on getting an initial workload deployed to production on the technology to prove its effectiveness, start deriving value from the technology quickly, and build skills, confidence, and buy-in towards its adoption. My conclusion, after probing deeper, is that companies shouldn’t hesitate to consider using mission critical workloads to pilot new technology as long as certain conditions are met and there are measurable advantages to be gained. His statement made me reconsider and seek input on my usual, industry-standard recommendation to avoid mission critical workloads as the first on a new technology. In a discussion with the CTO of a bank on getting the company’s first workload onto the IBM Cloud Pak® for Integration, he surprised me by saying that they always prefer mission critical workloads as the first workload for new technologies. What type of initial workload should you focus on when adopting new technology? I'll explain why you shouldn’t quickly rule out mission critical.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |