Frameworks
Operational design
The practice of making your model of the work explicit before you reach for software.
What is a unit of work here? When is it done? Who holds its state, and where does that state live when nobody is looking at it? Those are design questions, and they have to be answered in your own language before any tool can help.
Teams skip this because tools already encode the answers, so adopting software feels like deciding. It is not: you inherit a shape from whatever you adopted first, then spend years contorting the work to fit it.