I was going to write the same. Also, it implies (rightly) that changing high-impact theories should be left to experts who have fully explored the domain and the mechanisms.
There are times to disregard inconvenient aspects of theory:
Quick-and-dirty development: If you are building an passenger jet, yes stick to theory. But if you are hacking together a quick tool that won't be used past the end of the week and which will have little impact, then just get it done!
Early stage development: You're in an experimental stage anyway. Better to experiment more than to perfect the product. You can address theory later when your concept has matured.
For low-impact development, I think it's often better to encourage people to experiment, explore, and learn - to have agency - than to worry about theories. That's how people learn and engage best.
Comments
I was going to write the same. Also, it implies (rightly) that changing high-impact theories should be left to experts who have fully explored the domain and the mechanisms.
There are times to disregard inconvenient aspects of theory:
Quick-and-dirty development: If you are building an passenger jet, yes stick to theory. But if you are hacking together a quick tool that won't be used past the end of the week and which will have little impact, then just get it done!
Early stage development: You're in an experimental stage anyway. Better to experiment more than to perfect the product. You can address theory later when your concept has matured.
For low-impact development, I think it's often better to encourage people to experiment, explore, and learn - to have agency - than to worry about theories. That's how people learn and engage best.