> They've seen initiatives come and go, leaders arrive and depart.
Yup, and they may have seen the exact same initiative you're trying, in the exact same conditions, multiple times. With the same results.
You may want to learn from their experience before becoming failed example +1 for the person replacing your replacement.
> Archetype #2: The Passive Resister
> Document agreements in real-time."I'm noting down what we've agreed to. I'll send a quick email after this meeting so we both have the same reference point."
If you're not doing it routinely for everything it means most of the meetings you have are just social ones. Not work ones.
> Archetype #3: The Brilliant Aggressor
I feel like the author is mainly in this category. Their way or the highway.
> Archetype #4: The Perpetual Victim
> Confirmation bias: They actively collect evidence that supports their narrative of being unfairly treated or blocked by others.
The author may never have had to deal with a reluctant "OPS" team. On some projects I ended-up adding 2 weeks to a month for ETA due to having to wait for things like servers or access to be available. Even when tickets were posted at the start of the project.
Some projects die continually because there is no "buy in" not because the project is the incorrect path. The advice on how to get the buy in seems reasonable and probably can be adapted or tweaked depending on the specific circumstances. I think the author is trying to get us out of the confrontation of "exact same initiative you're trying, in the exact same conditions, multiple times. With the same results." and more on the way of getting those employees on board with understanding what pitfalls caused the original plan to fail.
Looking through these examples with the employee lens I can see some of that in myself and can also see how that is not productive.
> They've seen initiatives come and go, leaders arrive and depart.
Yup, and they may have seen the exact same initiative you're trying, in the exact same conditions, multiple times. With the same results.
You may want to learn from their experience before becoming failed example +1 for the person replacing your replacement.
> Archetype #2: The Passive Resister
> Document agreements in real-time."I'm noting down what we've agreed to. I'll send a quick email after this meeting so we both have the same reference point."
If you're not doing it routinely for everything it means most of the meetings you have are just social ones. Not work ones.
> Archetype #3: The Brilliant Aggressor
I feel like the author is mainly in this category. Their way or the highway.
> Archetype #4: The Perpetual Victim
> Confirmation bias: They actively collect evidence that supports their narrative of being unfairly treated or blocked by others.
The author may never have had to deal with a reluctant "OPS" team. On some projects I ended-up adding 2 weeks to a month for ETA due to having to wait for things like servers or access to be available. Even when tickets were posted at the start of the project.