The Resource Conscious CTO Building More with Less
summary
Panelists trade high-level advice for concrete moves: daily cloud spend emails that surface $1 storage leaks and cut runaway costs, tagging backlogs and tools to measure time in production support, using hierarchical OKRs to force objective scope cuts, halving orgs to remove dependencies, and running experiments with an AI “junior” for a month (no clear wins yet). They keep quality via agreed non‑negotiables and observability, size teams at three–four people, and support laid‑off colleagues with CV reviews.
AI-written summary · about
chapters (9)
- 0:00Introduction of panel
- 3:35Budget cuts and prioritization
- 10:19Engineering budget awareness
- 16:17Lean vs under-resourced
- 28:33AI replacing engineering roles
- 30:20Protecting quality under pressure
- 37:07Rebuilding trust after layoffs
- 42:02Metrics for less delivering more
- 44:33Wrap-up and key takeaways
related talks
43mPreparing your software engineering teams for times of financial uncertainty
43mEverything You Need, Nothing You Don't: How Do You Actually Build a Lean Platform
43mSweat the Small Stuff
42mPanel Discussion: Increasing Team's Performance Through Leadership
30mA framework for ambitious companies
25mLeading through scarcity: Building capacity in the team
45mLet’s Get Strategic! Stop Reacting, Start Leading
39mStop Focusing on Tech Debt