How to talk about tech with boards that just don't get it
summary
A concrete method for board buy-in turns nine months of negotiation into a single approval by reframing tech as business outcomes: request 3.5 million pounds to build an over‑the‑air firmware pipeline in 18 months (12 months dev, 6 months rollout), cut a recurring £2M upgrade expense to near zero, and reduce upgrades from six months to one week. Lists specific risks and mitigations (hire experienced hires, industry‑proven stacks used in automotive/healthcare/aviation) and explains why vendor‑supplied firmware is commercially justified.
AI-written summary · about
chapters (4)
- 0:00Why boards reject tech proposals
- 3:40Boards ask wrong questions
- 5:49Speak business not tech
- 9:23Solution in one meeting
related talks
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success
46mStop calling it technical debt and listen to your engineers
31mHow to get everyone to get on board with software security: practical tips and suggestions.
38mPanel discussion - Selecting the right technology for the right challenge
26mTech debt as innovation, reframing this forever problem as an opportunity
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
39mStop Focusing on Tech Debt
57mStrategic Decision-Making for Tech Leaders and Developers