The Power of Enablement

At Storyblok, our fantastic QA team supported the development team by carrying out a lot of repetitive manual tasks, such as validating new features and bug fixes, and ensuring that our functionality did not regress.

While this team was doing great work, there were a few negative side effects. As developers relied heavily on QA for validating every change, big or small, they also somehow offloaded ownership of ensuring that their features were working properly and not breaking anything. Obviously, QA became a bottleneck and productivity decreased.

With Matheus, we turned this around, making the developers responsible for validating small changes and bug fixes. This allowed QA to focus on the bigger picture and prepare complex test plans for larger features. This also gave QA time to focus on automation and enablement.

The QA team started improving their testing environment, giving developers access to more complex setups and enabling them to test these themselves. They also automated a large part of their testing process using a suite of end-to-end tests written with Playwright.

The impact was clear: bug fixes and small features were turned around faster, and reliability increased thanks to test automation.