Did you hear me? Before coding, listen first
“What was the question? I was multi-tasking.” This is a common refrain in remote work. We half-attend meetings. Our Spidey sense is listening for our name as we work on other things. It seems to be the norm. I am just as guilty as the next person.
There is a funny definition of multi-tasking. It defines it as “Screwing up several things at once.” Honestly, that sounds about right. Technology has enabled us to “be” two places at once. We can be home working and folding clothes too.
Tune In
I am old enough to have had a transistor radio. Mine was in the shape of Snoopy. Although you weren’t wondering, I am sure. It had to be tuned in precisely or you would pick up static.
When you are listening to someone you need to tune in and listen to more than their words. What does their tone and inflection say? What is their purpose in sharing this?
For instance, an old roommate of mine in college liked to share his opinion. Even if you didn’t ask. After a while, I realized this made him feel validated.
Interruptions
When you have something to say, you may get impatient to say it. Wait your turn. Of course, you can signal them or “Raise your Hand” in Zoom or Teams.
Allow them to complete their thought. Give them space. Once they have completed feel free to jump in. They should respect your time too. If they don’t let them know and finish your thought.
Don’t prescribe
This is a hard one for me to overcome. I want to tell them what to do. We can’t judge what they say. Although we may want to jump ahead and start thinking about our response.
Ask questions
Clarify what they want. As a developer, I can start thinking about the solution. It helps to ask a few questions to see if you understand their ask.
Earlier in my career, I put together a solution that took a long time to develop. When I brought it back to the stakeholders they said, “Wow, that is not even close to what I asked for.” A few questions would have saved me weeks of work.