...Better to figure out why you're doing what you're doing and figuring it out organically (with some guidance of course) than to copy everyone's homework and pickin' what ya like. (Just my 2 cents)...
You will get lots of good specific advice, but as I do lots of system/process design (I write books on design, trust me!) I say this is the right approach. Okay to get other ideas and take some training as it will get you not necessarily new ideas but start making you all challenge what you do...
...and WHY.
The ideal case (and I know this is lots of work!) would be to have someone (ideally not even on the team, but smart enough and versed enough in the principles of police tactical work) literally just watch you, with a camera and notebook, at the next few training cycles, and if plausible even briefings for and real world ops. Watch body cam footage if legally allowed for this purpose, etc. Write it down, organize it into items done repeated and done one or a few times, and then you all talk through WHY you did that. Specifically with some sort of model consistently applied to all of them such as circumstance, resource, outcome.
Whatever the org, imposed processes (or TTPs) take a lot of effort and often do not work as well as analyzing, documenting, and improving on your own.
(Some caveats if you have a known series of bad outcomes, and want to change specifically, but only some).