I have a slight scepticism for anything that "drives" development other than the need to improve customers experience.

This is my take on TDD, once a year I write the tests first, I congratulate myself for solving the puzzle laid out in front of me, filling in the many gaps as I make the tests pass. Trouble is I actually prefer the joke acronym DDT where I write tests to protect my code which is the actual point of the tests.

DDT has no complexity, imagination, or room for interpretation, you test exactly what you have coded, that is quite efficient don't you think?

TTD involves guessing what tests you might need, the tests become pain points to refactor on top of your actual code, if requirements change / or being honest, you misunderstood something. you have to refactor both the test and the code.

In the world of interitive workflows, order matters, choose the path of least resistance, choose what makes sense.