Extracting, Processing, and Relaying Essential Information Only
16 April, 2019
I joined an organization where a person at the top level wanted a daily report from me. It was difficult for me because I had just started and he wanted to know the details on all of the projects. I knew that my job was to extract information, process it, and then pass it along to those who need to make decisions, yet I found it painful because I knew that the information that I was giving him was not being acted upon. I thought it impossible to provide him with every detail of every project in every given state.
I had to reevaluate his expectations from me and his set of responsibilities. What exactly is it that he needed? What kind of problems did he need to solve for which he needs information from me? Based on these reflections I would only provide the necessary information. Sometimes it would be about a product. Other times it would be a very specific project on a product. I would occasionally inform him about a whole team.
Additionally, to know which information to provide, I would ask him to invite me to meetings that he was involved and where he used my information. This meant sitting in on the actual meeting or simply listening in silently on a telephone call. Further still, I would solicit feedback from higher level managers about what was discussed in those meetings so that I could easily understand the level of information he needed, what numbers he was looking for, and/or the progress and results of specific cases.
- If you feed your boss a lot of information, they are likely to get overwhelmed by it. Giving them an abundance of information will only inhibit how they will react to it. Too much and they won't be able to properly handle it all. Instead, give them a certain amount of information and be specific. That allows them to make their decision easier and helps them achieve their goals.
- It's beneficial to you to inquire, investigate, and understand the type of information your manager is looking for. It could be as simple as knowing the status of a project- green, yellow, or orange. Seek out what they need to know and don't give them any other information so they don't have to think too much, because they already have to think a lot.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Based on an awesome book titled "Deep Work" by Cal Newport we provide provide a brief overview of the Rules for Focused Success in a Distracted World.
CEO at Quantum Vision Consulting
Learn about 10 rules from the wisdom of these long-living residents from Ogimi, a small village in Okinawa, Japan. You could interpret the rules as the lifestyle habits that enable the senior residents of Ogami to live long and enjoy their ikigai.
CEO at Quantum Vision Consulting
Oftentimes Engineers work in silos, developing products to specified requirements, while they remain disconnected from the most important of questions - "WHY are we building this?" We'll explore the consequences of this mindset, as well as how to connect your Engineers to the larger Company Vision.
VP of Engineering at ExecThread
Discover the daily struggles, challenges, and moments of delight encountered when delivering banking products around the world. I will share my story candidly and honestly, without filter as much as I am allowed, and offer insights into my approach while providing retrospectives of the results.
Director of CX at FLF PRODUCT DESIGN
Consideration for starting a multi year software infrastructure ( V2 ) project that involves hundreds of globally distributed engineers.
VP Software Engineering at human