CharlieKey takeaways from your favorite podcasts
← 6 October 2026In Depth

The most expensive mistake in outsourcing your tech stack | Jay Parikh (EVP CoreAI, Microsoft)

Jay Parikh argues that great engineering leadership treats people, strategy and technology as one system, built around speed of learning, small empowered teams, parallel big bets, and owning critical layers of the stack.

Watch on YouTube ↗

Charlie's summary

  1. Shrink the learning loop: as companies grow, learning slows, so the job is to fight that expansion

    Jay pictures an organization as a circle where each revolution is one unit of learning. As a company grows and succeeds, the circle's diameter widens and each lap gets slower. His answer is to keep adjusting ways of working, such as returning from 40-person meetings to eight-person ones. He rejects process for its own sake but backs the right structure, and he treats failures and outages as curiosity. If you can learn 2x, 5x or 10x faster than competitors, he likes your chances.

    ▶ 9:44
  2. Toil is an effect; the cause is a culture of learned helplessness, and culture rate-limits everything else

    Jay lists five elements of leadership: team, strategy at the right altitude, a weekly execution drumbeat, fighting toil, and culture. He says toil piles up where leaders say “we would fix that if we had more people”. The fix is to change the culture and leader incentives. That is why he says culture often rate limits the other four. He means prescriptive ways of working and behaviors, not snacks and swag.

    ▶ 6:29
  3. To speed up a slow team, measure focus time and ship in crawl-walk-run steps rather than by edict

    Jay's Core AI team collected anecdotes and quantitative data on how builders spend time, defined focus time, and put dashboards in front of every engineering leader. He warns that demanding August 15 instead of September 30 works once or twice but is not durable. Instead, ask Socratic questions, find the assumptions, and shave weeks off each release. Facebook went from a daily ship of the core product to three times a day, then continual deployment, backed by investment in automation.

    ▶ 15:40
  4. Replace the org chart with a work chart of tiny teams with a clear DRI, and escalate within 24 hours

    Jay says large teams cannot move fast. He wants very small, high-talent teams with a clear directly responsible individual who has context and agency, guided by metrics. He tells teams that if they are stuck for more than 24 hours, they should call him rather than wait two weeks for the issue to climb the management chain. He also says to make the call quickly when the wrong person is in the lead role.

    ▶ 20:50

Give your email to unlock the rest of the key points — for every episode.

Do more with Charlie

Free — sign in with your email, no password.