For anyone not familiar, a guideline in improv is to avoid saying `Yes, but...` and instead say `Yes, and...`.
While maybe not using those exact words, I find that when I disagree with someone at work I can either set myself up in opposition with them or I can work with them to get to the desired state.
"Is this the doc you are looking for?"
"Yes, but why isn't this in the wiki?" vs "Yes, and let's add a link to it in the wiki".
It's a very simple shift, but it really makes a difference in collaboration.
Whenever I don't understand what's happening, I try to step back and think of open ended (non judgmental) questions.
So depending on the whatifs, in this OC's case, I might ask:
How can I make this better?
Can you help me improve the docs, wiki, readme, whatever?
Additionally, it shifts the "initiative" (for lack of a better term) back onto the eeyore. Meaning, instead of me explaining and defending, by asking for help, I'm shifting the onus back onto them.
I mean, it's just so easy (and lazy) to criticize. Subtly, gently insist the critic put some skin into the game. Over time, they'll step up or bow out; both outcomes which suit me fine.
For anyone not familiar, a guideline in improv is to avoid saying `Yes, but...` and instead say `Yes, and...`.
While maybe not using those exact words, I find that when I disagree with someone at work I can either set myself up in opposition with them or I can work with them to get to the desired state.
"Is this the doc you are looking for?" "Yes, but why isn't this in the wiki?" vs "Yes, and let's add a link to it in the wiki".
It's a very simple shift, but it really makes a difference in collaboration.