Yesterday I was reviewing a doc that I wasn't really happy with. On the way to the review meeting I realised I was about to make a stupid mistake.
I was thinking I was going to go in and explain how the doc failed in many ways and didn' follow best practices. Essentially I was going in with the mindset to be an obstacle.
Before I sat down I realised that I needed to approach this from a different perspective.
Was it good enough to work with? Probably. Did everything need to be tight and perfect for me to be able to move on? No it didn't.
And it would have harmed an already fragile team espirit de corp.
It's more important to be able to communicate openly and work together than to address problematic documentation.
Back to the concept of satsficing. Satisfy + sufficient.
Instead of looking at the shortcomings as obstancles or risks to manage right now, I decided to instead to assess whether it was good enough to work with. And then to highlight the risk areas and try to resolve them in a positive way on the room.
We still have a business case doc that has loose terms of refernece and ambigous staements about what needs to be done, but as a team we can work through these issues down the line.
What's the message here?
Put people ahead of processes.