Preparing your software engineering teams for times of financial uncertainty
summary
Panelists recommend small Q&As of 8–10 people, two‑way honesty, and regular all‑hands where the CFO showed charts of revenue so teams see real trajectory. Practical moves include pivoting product lines (TripIt made a free six‑month shift), cutting travel and nonessential SaaS, slowing hires selectively, and running OKRs to save X dollars — one claim: unfairness churn costs ~$16B/year — all intended to preserve headcount and buy time.
AI-written summary · about
chapters (9)
- 0:00Start
- 10:37Approach to Dealing with Known Unknowns
- 10:47How Do You Balance Empathy and Understanding while Keeping the Business Moving Forward
- 13:58What Are some of the More Effective Feedback Loops That Can Be Created between the Business and Product Development Teams
- 18:16What Skills Have Your Teams Had To Acquire during the Financial Downturns and Why
- 20:23What Roles if any Can Data Science and Ai Slash Ml Play in Helping To Build More Resilient Businesses That Can Survive Economic Downturns
- 24:46Slack
- 26:49What Are some of the Other Tools and Strategies Decision Makers Should Consider When Managing through Hard Times
- 40:55Parting Thoughts
related talks
43mLeading teams through times of uncertainty and upheaval
31mGrowth in a downturn
47mThe Resource Conscious CTO Building More with Less
56mLessons from Leading through Uncertain Times
20mHow to keep everyone happy (on a shoestring)?
07mManaging in hard times: How to shift from growth to stability
24mLeading through the downturn
41mNavigating Agile Transformations in a Crisis: From Thunderstorm to Smooth Sailing