Part IV · Transformation, Governance and Resilience
Chapter 12Technology Is a Business Transformation
Technology becomes CFO work when the question is whether the organisation will perform work differently and realise measurable value. This chapter covers process redesign, group standards, local variation, investment cases, vendor challenge, pilots, data, access, interfaces, adoption and post-go-live accountability.
Questions this chapter helps answer
- • How can a technology need be described without starting with a product name?
- • Why should the process be redesigned before it is automated?
- • How should group standards and legitimate local variation be balanced?
- • How can a CFO test whether promised technology value appeared after go-live?
Key concepts
- • business transformation
- • process redesign
- • technology investment case
- • group standards
- • master data and interfaces
- • adoption and realised value
Technology becomes CFO work when the question is whether the organisation will perform work differently and realise measurable value. This chapter covers process redesign, group standards, local variation, investment cases, vendor challenge, pilots, data, access, interfaces, adoption and post-go-live accountability.
Chapter-end learning
Apply, check, and remember
Apply it to your situation
Connect the chapter to a real hotel decision
As you answer, think about where this issue appears in your own property, team, report, meeting, or control process. Work through one item at a time, check the result, and then continue.
Open learning preview: the quiz and flashcards are available to everyone. Answers are checked immediately, while the detailed reasoning remains in the complete chapter. Sign in to save quiz attempts and flashcard confidence.
Knowledge check
Question 1 of 6
Memory practice
Flashcard 1 of 4
Reveal the answer, decide how confident you are, and then move to the next card.
Continue the discussion
Share how this applies in practice
Respond to either prompt, or connect both prompts in one practical response.
Discussion prompt 1
The chapter requires problem definition, controlled source data, common definitions, ownership, human review, auditability and a measurable use case before scaling AI.
A hotel group wants AI-generated monthly performance commentary, but property reports contain inconsistent definitions and several manual adjustments. What should the CFO require before approving the pilot?
Define the decision and baseline; standardise the metric definitions; identify authoritative sources and owners; close or document manual adjustments; protect confidential data; define human sign-off and correction tracking; pilot on a limited period; measure preparation time, error/correction rate and management usefulness; stop or redesign if source reliability remains weak.
Discussion prompt 2
The chapter treats a pilot as a learning stage, not merely the first go-live, and separates installed from adopted, operating and verified value.
An ERP pilot is technically live in one hotel, but users still keep shadow spreadsheets and the monthly close improved only slightly. Should the group scale immediately?
Review why shadow systems remain, whether the future process is practical, which interfaces or data are unreliable, whether training/support are sufficient, whether controls work and what benefit has actually improved. Scale only the stable parts; pause or redesign unresolved elements before multiplying the problem across the portfolio.
Sign in to contribute to this discussion.
0 responses
Responses are public and may be moderated to keep the exchange professional and useful.
No responses yet. Start the discussion with a practical example or a question raised by the chapter.