Panel discussion - Selecting the right technology for the right challenge
summary
Panel boils down to concrete rules: one company standardises on .NET and Azure PaaS from day one (since 2015) and refuses deviations, another reports 1.4M customers and £8bn AUA to show scale. Recommended practices include a tech radar and guardrails, regular 8‑week cycles with six weeks build, two weeks cooldown, plus investing in a few vendors to align roadmaps rather than spreading thin. Leadership signals matter: decide whether to be a visionary or operational CTO around ~15 engineers and sell new tech to boards via business outcomes and risk mitigation.
AI-written summary · about
chapters (7)
- 0:00Introduction and panel setup
- 3:39Keeping up with tech trends
- 13:31CTO role and hands-on involvement
- 18:22Changing wrong tech choices
- 26:02Strategic partnerships with vendors
- 30:58Communicating tech to the board
- 37:43Closing remarks and Q&A
related talks
43mPanel: The Platform Rock-Paper-Scissors: Build, Adopt, Buy
41mPanel discussion: Agile in the modern age
57mStrategic Decision-Making for Tech Leaders and Developers
31mBuilding an Enduring Culture of Engineering Excellence
36mHow to make technical decisions?
21mFrom fast growth to sustainable growth
26mPanel Discussion Led by – Nicole Forsgren
43mShow Me The Money! Managing Technology Investment