Which brings me to the title of this article… accepting what you can’t change, but also changing what you can’t accept. What does that really mean?
The customer wants what they want
This is the accepting what you can’t change part. I had a project customer on a very technical project where the customer lead was the head of human resources. He didn’t want to see a project schedule or Gantt Chart or anything like that. He didn’t want to see a detailed project status report. He wanted an issues list – that’s it. And he was stubborn about it. So that’s what I gave him. It’s not how I managed the overall project and the project team, but it is exactly what we used to drive every project meeting and he was elated. In the end, we had a very successful project and our project sponsor never felt overloaded with the PM tool pieces and reporting structure that he didn’t understand and didn’t want to understand.