> I'm getting old, I've been doing this for going on 20 years, I've been doing this since before fad workflows were really embedded in the culture. They were ar

> I'm getting old, I've been doing this for going on 20 years, I've been doing this since before fad workflows were really embedded in the culture. They were around but not nearly as common. Me too (many decades), and we still manage things the same way I was taught when I started: Pragmatic and flexible analysis of the project, and mapping out how best to approach this particular project or set of tasks. Projects are not all the same and different methods or approaches are required for different situations (e.g. whs with complex conveyor execution system+multiple app systems that can only go live in a big bang fashion, vs incremental improvements to ordering and order routing processes that can be chipped away at). Generally it results in breaking it down into some major phases, (e.g. this qtr or year we tackle x,y and z, next qtr or year we tackle x', y' and z' and d,e and f). Within a phase of work we talk about how to break it down, what needs to be designed up front, what can be handled as we go, which areas are we unfamiliar with and need to do some prototyping, etc. Then we work, meet regularly, check progress, adjust our plan, adjust design where needed, decide when to divert some attention to going live and things like conversions/training/change mgmt, etc., lather, rinse, repeat.