# Should TDD be Mandatory? Why are so few teams using it?

DevFeed: [Should TDD be Mandatory? Why are so few teams using it?](<https://devfeed.tech/articles/should-tdd-be-mandatory-why-are-so-few-teams-using-it-28431.md>)

Original publisher: [Read original article](<https://craftingtechteams.substack.com/p/should-tdd-be-mandatory-why-are-so>)

Author: Denis Čahuk

Published: 2025-07-24T13:33:16Z

Content type: opinion

Language: en

Sources: [Crafting Tech Teams](<https://devfeed.tech/sources/crafting-tech-teams.md>)

Topics: [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Testing](<https://devfeed.tech/topics/testing.md>)

Tags: [culture](<https://devfeed.tech/tags/culture.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experimentation](<https://devfeed.tech/tags/experimentation.md>), [tdd](<https://devfeed.tech/tags/tdd.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

This article argues that TDD should neither be mandatory nor banned. Successful adoption depends more on psychological safety, cultural buy-in, team autonomy, and room for experimentation than on enforcement. It also presents TDD as a way to support earlier feedback and safer delivery under change.

## Source excerpt

Popularity is not a good measure for quality. The best litmus test for engineering culture is an ongoing effort to learn and experiment with a small part of your bets.