Change

an unplanned, but seemingly necessary follow up to that thing I did

First - thank you to all the new subscribers. I have a longer post I'll share in a few days, but since a lot of you don't know me I want to give some context on the last post before I move on.

Nearly nine years ago, Brent Jensen and I began the AB Testing Podcast because we saw changes happening with the way teams build and delivered software, and how testing was changing. We talk about many other things on the podcast (one could say we talk about too many things), but that primary theme has remained. We’re not inventing anything, and we’re not telling anyone what to do - our goal is to help teams (especially - but not limited to testers) handle this change and grow. Change is hard, and people generally avoid it. We’ve seen a lot of teams attempt to change and fail miserably. We have also seen teams that have learned how to tighten feedback loops, improve quality, and accelerate their businesses.

The words in my last post aren’t a prescription. They are describing something I’ve seen wo…