Looking for help understanding the order of related events surrounding the usage of threat models made with MITRE ATT&CK

I've learned a lot about MITRE ATT&CK recently, but one thing I have trouble answering definitively is the chain of events that ATT&CK threat modeling is supposed to fit into. A few folks in my org have some... interesting ideas about how to use ATT&CK, and it really feels like we're missing the mark. Currently, we've got architects mapping individual techniques (or sub techniques) and ending up with an output that looks *kind of* like an attack tree or adversary …

amp att ck cybersecurity events mitre mitre att&amp order threat threat models