> If you say it all out loud, it is obvious, but if you go step by step, each one was somewhat plausible. The step by step at the time vs the "in hindsight" re

> If you say it all out loud, it is obvious, but if you go step by step, each one was somewhat plausible. The step by step at the time vs the "in hindsight" really is a powerful persuasion tool/learning tool. e.g. the below is a real situation that happened at work: - I run a SRE team - We do a short term embed of an SRE member to do some one off dev work for a migration - Dev Mgr to my team member: "oh, since you are touching that code, you should probably also work on this tiny business feature that depends on it" - DM: "Oh, since you worked on that, you should also work on this other feature" - DM: "Oh, since you worked on the above, just take over the whole feature" - DM: "Oh, since you did all THAT, can you talk to the business and figure out the next features??" Again, totally ridiculous overreach but spread out over 6 months in a fast moving, high stress environment, it can go unnoticed.