In my case it was driven by need but I found it very quick and easy to learn.

"We don't have a fourth branch of government called Elon Musk, and that's going to become real clear." -Jamie Raskin

Hey Richard, thanks for the shout-out! Unfortunately, you guys didn't talk about me immediately, so I lost interest and had to turn it off...j/k!

Good conversation and glad to have listened, especially since I might be on soon and will need to find a few rare topics you guys didn't cover.

Same with Prince and Minnesota.

I don't need to browbeat or filibuster, or worse, meekly succumb to these pointless wastes of times. I can't imagine how many hours I wasted doing just that.

Our leadership group discusses priorities and then projects are assigned to cross-functional teams that execute. We do a few stakeholder check-ins, roll in some GTM activities, and that's basically it.

It had been a while since I thought about that, so I had to go and look at it. I'd say it's worth a read for anybody stuck in a rut, but for us, I think our approach is simpler.

Dump your SDLC.

We also shipped a hell of a lot more with smaller teams, and had a higher success rate.

Rh1+

Yeah same. Complaining helps AWS make it better :)

More evidence that complaining works :D

Always fail fast when introducing new workloads to your stack. Waste is driven by an inefficient process becoming the new normal.

In the past year, my team has launched a fleet of new services built mostly on serverless technologies. Some of these become core features. Some of them we just deleted.