As an IT project manager, recent events have led me to rethink who and when a PM is needed, wanted, required, necessary. I had almost always believed that the addition of a PM in a large project could only be good. There are exceptions to this, as I recently learned.
Get along with the Customer at all costs: During the collection of requirements, scope writing and understanding timelines, there will be times where you may not 100% agree with your customer. For their long-term benefit you negotiate an agreement. The customer should understand that this negotiation is for their benefit.
You could use a reciprocating saw (Sawsall) as a manual saw, but why would you? Turn the thing on and let it do all the work. There is no need to go to the expense of buying an electric saw, only to expend energy sawing the thing back and forth, in a manual fashion, off. You are penalized because you have spent money on the saw, the blade is too short for long cuts, and the thing is heavy and unwieldly. This same experience can, and does happen with WordPress, my favorite CMS development tool.
As an experience project manager I often see the planning of projects before they start the actual work. Often I can predict when a project will go off the rails before it actually happens. Small red flags dot my brain and the warning lights go off. If I feel I have a duty, a gentle reminder is extended. Most of the time the leader feels more than capable of running the project to completion. My advice is relegated to the garbage pile of idiot verbiage and life goes on. I then sit back and watch the train wreck become reality. It is all so unnecessary.
