Correcting my poor communication
Last year I read Behind Closed Doors: Secrets of Great Management by Johanna Rothman and Esther Derby. The book is well written and is told in an interesting way. In the back of the book, there is a section titled Techniques for Practicing Great Management. In that section, I found a list of questions designed to help managers make the progress of any project contributor more visible. You might try asking questions like the following:
When I finished reading this list, I noticed that some of these questions were eerily familiar. In fact, a past manager had asked me those questions before. I remember thinking about why he would be asking me those questions because I always report my progress.
After reflecting on the questions a bit more, I began to recognize that I had not been effectively communicating my progress. Without even being aware I was doing it, I had stopped. Not only have I not been communicating progress, I haven't even been telling my manager what I've been working on.
I see three reasons as to why this might have been:
1. I didn't yet really understand the scope of the work I was doing. I knew what I wanted to do, and I knew how I wanted to do it, but I was still trying to work out the steps to get from point A to point B. Because I didn't truly understand the work yet, I couldn't think of a way to explain my tasks to my manager yet. When he asked what I'd been doing and what I planed to do, he was looking for a level of precision that I just didn't have yet.
As you can see, I was very vague.
2. My manager was new (to me). The old manager just rolled off the project and this manager had not yet been 'tested in battle.' We didn't yet have a history or a working relationship. It's hard to develop a working relationship with a new manager. We didn't know to communicate yet and we both had different expectations for what the person in our roles should be doing.
Therefore, much of what he asked me smacked of micromanagement. When in truth, it was more likely that he truly didn't know what I was doing and he was just trying to learn the only way he knew how - asking questions. Nothing wrong with that...
3. Finally, I was moving off the project in the near future (or at least my status with the project was rapidly changing). That meant that I didn't really want to take the time to build the relationship like I normally would have. It's hard work getting to know how to work with someone new and I just didn't want to put in that effort.
Once I recognized my behavior, I needed to fix it.
Starting the Monday after I finished the book, I took the time to invest in the new relationship. It was not his fault he was new, I was just being silly (to put it nicely). I worked with him to provide more visibility to my tasks and progress. I struggled with him to understand the work. I included him in my brainstorming sessions and talked with him more about the nature of the testing I was planning.
Oddly enough, that process of explaining it to someone else helped me better understand the problem. The investment was worth it.
- How will you know when you're done with that?
- What steps will you take?
- Which part will you work on first?
- Can you provide a picture or a measurement of work to date?
- Do you need to collaborate with anyone else on this?
- How will you know you're making progress?
- Who needs to be in the loop if you are unable to finish this on time or run into problems?
When I finished reading this list, I noticed that some of these questions were eerily familiar. In fact, a past manager had asked me those questions before. I remember thinking about why he would be asking me those questions because I always report my progress.
After reflecting on the questions a bit more, I began to recognize that I had not been effectively communicating my progress. Without even being aware I was doing it, I had stopped. Not only have I not been communicating progress, I haven't even been telling my manager what I've been working on.
I see three reasons as to why this might have been:
1. I didn't yet really understand the scope of the work I was doing. I knew what I wanted to do, and I knew how I wanted to do it, but I was still trying to work out the steps to get from point A to point B. Because I didn't truly understand the work yet, I couldn't think of a way to explain my tasks to my manager yet. When he asked what I'd been doing and what I planed to do, he was looking for a level of precision that I just didn't have yet.
Mark: "Which part will you work on first?"
Me: "I don't really know what the parts are yet. I'm still trying to figure that out."
Mark: "How will you know when you're done with it?"
Me: "I don't know yet. I'm still not sure what 'done' means. It's a complex set of tests and I still don't know what they will look like."
Mark: "Do you need to collaborate with anyone else on this?"
Me: "Of course, I just don't know who yet."
As you can see, I was very vague.
2. My manager was new (to me). The old manager just rolled off the project and this manager had not yet been 'tested in battle.' We didn't yet have a history or a working relationship. It's hard to develop a working relationship with a new manager. We didn't know to communicate yet and we both had different expectations for what the person in our roles should be doing.
Therefore, much of what he asked me smacked of micromanagement. When in truth, it was more likely that he truly didn't know what I was doing and he was just trying to learn the only way he knew how - asking questions. Nothing wrong with that...
3. Finally, I was moving off the project in the near future (or at least my status with the project was rapidly changing). That meant that I didn't really want to take the time to build the relationship like I normally would have. It's hard work getting to know how to work with someone new and I just didn't want to put in that effort.
Once I recognized my behavior, I needed to fix it.
Starting the Monday after I finished the book, I took the time to invest in the new relationship. It was not his fault he was new, I was just being silly (to put it nicely). I worked with him to provide more visibility to my tasks and progress. I struggled with him to understand the work. I included him in my brainstorming sessions and talked with him more about the nature of the testing I was planning.
Oddly enough, that process of explaining it to someone else helped me better understand the problem. The investment was worth it.