Sep 28, 2026 • 16 min
But, compliance! A welcome justification for superfluous gates in our IT delivery process, and the go-to excuse for embarrassingly long delays. Compliance is one of those severely under-documented topics in the IT industry that triggers massive overcompensation. Contrary to popular belief, compliance is not a good reason to go slow. The research is clear: going slow for safety is a mistake (Forsgren et al., 2018). It causes friction, decelerates feedback, drives down quality, and brings a team to a grinding halt. On the contrary, Compliance is an excellent foundation for better quality. It enables faster delivery, accelerates feedback, and ultimately produces better, more compliant outcomes.
Sep 27, 2026 • 0 min
Notes from the SoCraTes unconference session on the topic of Continuous Compliance.
Feb 22, 2022 • 13 min
In part 2 of this series - Why do Teams use Feature Branches? - I examined all the possible reasons teams mention for why they use feature branches. There was, however, one reason, I did not mention that people referenced as the ultimate reason: “We use feature branches and pull requests to comply with regulations”. I would like to explore this and show there are other options to comply that do not have the same drawbacks.