G6 CIO Dishes on Company’s Build or Buy Strategy
- 3 Questions G6 Asks About Tech for Successful Implementation
- Is it cloud-first?
- Will it create option-value for the business? The tech should help G6 adapt to changes.
- Will it increase speed and agility?
HT: How does G6 determine when a change is necessary?
BURGESS: We always vet technologies against business demands. In the past, someone might say: "Here is a great technology. Find a way to fit it into our business." When you follow that path, the "great technology" might actually generate a lot of overhead, time, and cost. It could even increase complexity and erode key business objectives. So we don't follow that model.
Instead, the first thing we do is look at current business demands, the needs of our user base and the market as a whole—all prior to introducing a technology solution into the discussion. Then we build a Critical to Return assessment and we align our desired business outcomes with the influencing activities that could help drive those outcomes. This is where technology enters the discussion—as a vehicle to influence and enable business results. From there we implement a change or technology – when and wherever it is most impactful – to drive the desired outcome. For all of this to work, we have to define that business outcome really well at the very beginning of the process.
HT: How does G6 decide when to partner with a tech supplier versus building it in-house?
BURGESS: With any tech initiative, we always ask very early on: Should we build or buy? To answer that question we often ask another: Are we going to be the best resource to build this? When the answer is yes, it's because there is a distinct competitive advantage that already exists within our team and that advantage can be enhanced for our business when we build that technology ourselves. That isn't always the case. Some services in the industry have become so commoditized that it just makes sense for the company to buy them. Sometimes bringing in best-in-class partners who specialize in a specific area is a better option than building it in-house.
Recently we rebuilt from scratch and moved to the AWS cloud our entire core platform including our CRS and PMS. Our original CRS was built on a 20+ year old IBM Informix database and our PMS was a 10+-year-old system that we inherited from previous ownership years ago. We decided to partner with AboveProperty and implement their fully-distributed cloud CRS as well as with HotelKey for their cloud-based PMS. We elected to build our core foundational microservices architecture ourselves in the AWS cloud so we would have full control of any components now – or in the future – that would need to be plugged in or unplugged.