The thing that feels implicit, yet false, in all of this is that workflows are static. People evolve, learn, change. Teams even more so. The most important pro

The thing that feels implicit, yet false, in all of this is that workflows are static. People evolve, learn, change. Teams even more so. The most important process I implement with teams is retrospection and its use as a mechanism to modify process in a principled way. So as you learn about your own process, your tools can either fall away and be replaced, or flex with you and stick around for longer. My guess is that flexibility is slightly better than fixity, as it'll let you live within one ecosystem for a little longer. The other way of interaction is to be inspired by new tools to modify your process. This feels pretty off to me, at first, in that it means that you're moving your process do to exogenous things as opposed to endogenous learning. But that sort of work can be really valuable too. It's good to learn other people's methods. It forms an impulse that can get you out of local optima. It's an important part of the learning process.