Plato Elevate Winter Summit has been announced (Dec 7th-8th)

🔥

Back to resources

Increasing Visibility When Doing Well

Impact
Team Processes

16 March, 2021

Sami Touil
Sami Touil

VP of Engineering at Onfido

Sami Touil, Senior Engineering Manager at Spendesk, explains how he increased his visibility as a manager who was doing well and whose good performance went unnoticed.

Problem

For as long as I can remember -- or more accurately, as long as I have been a manager -- I struggled to increase visibility on what I was doing and providing to the team. While they would be able to grasp what I was providing to them individually, they couldn’t understand what I did for the team on a broader scale. My actions went without any turbulence, smooth and seamless, and that made them unnoticeable. If I would create problems for the team or cause disruption of any kind, surely they would notice that and react.

Actions taken

What didn’t work

At first, I tried detailing all the things I did as a manager in standups. It didn’t work for me. I felt like I was justifying myself and seeking approval for doing things the way I did. Also, I felt I was disrupting standups because all ICs would discuss things directly related to the product and features they were building, and I would be talking about external stakeholders and things only remotely relatable to what they were working on. In addition, I tried telling my direct reports in one-on-ones what I was doing for the team, but that was not good either because one-on-ones should be about them, not about me.

What worked

However, what worked well from the start was my initiative to publish a weekly newsletter named the Engineering Manager Report. The EM Report would showcase what EMs were doing in the past week; EMs would present the new metrics they introduced or announce hiring that was underway. It was done without bragging and with an intent to shed light on things that EMs were doing on a broader scale and that were invisible to most of the team. The Report provided up-to-date information on subjects the team was unaware of due to the nature of their day-to-day work. It also provided them with an opportunity to get insights into what was happening across the engineering department as a whole.

On a personal level, the process of compiling the newsletter was rather stimulating. It forced me to reflect and evaluate all the things I did throughout a week. Oftentimes I would lose track of some of the smaller projects as those larger ones apparently took most of my time and effort. But, when I was producing the Report, I would list down all the projects, aggregating all the smaller ones and connecting them to a bigger picture.

The EM report had lateral benefits apart from the increased visibility I achieved. People on the team became aware of all the different things managers -- including myself -- do, but my managers also gained an accurate insight into what we were doing a level or two down and were able to track our progress.

Lessons learned

  • Taking an indirect route is sometimes the shortest way to go. In this particular case, though people on the team were unaware of what I was doing, approaching them directly and telling them straightforwardly about all the work I was doing for the team could have been counter-productive.
  • People are mostly curious about what it is that you do. But you have to find the right format to instigate that curiosity. I also had to get rid of the feeling that they were only curious because they wondered if I was of any use at all. No, people were asking those questions within the sphere of their own interest and knowledge. If you want them to ask questions outside of their day-to-day work, provide them with visibility into those areas.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Building a New Team in a Foreign Country

23 November

Adam Hawkins, Site Reliability Engineer at Skillshare, went all the way across the world to build a brand new team who worked very differently than he was used to.

Team Processes
Adam Hawkins

Adam Hawkins

Site Reliability Engineer at Skillshare

What It Takes to Understand Other’s Perspective

23 November

Nicholas Cheever, Divisional Vice President, Global Supply Chain Technology at Trimble Transportation, shares how to really understand someone else’s point of view.

Team Processes
Nicholas Cheever

Nicholas Cheever

Divisional Vice President, Global Supply Chain Technology at Trimble Transportation

How to Handle Team Collaboration After a Merger?

23 November

Nicholas Cheever, Divisional Vice President, Global Supply Chain Technology at Trimble Transportation, shares how he helped the acquired company’s team members understand the business mission and give them focus.

Acquisition / Integration
Team Processes
Nicholas Cheever

Nicholas Cheever

Divisional Vice President, Global Supply Chain Technology at Trimble Transportation

Surefire Ways to Boost Team Morale

11 November

Rajesh Agarwal, VP & Head of Engineering at Syncro, talks about effective ways to boost team morale when stepping in as a new manager in the team.

Motivation
Team Processes
Rajesh Agarwal

Rajesh Agarwal

VP and Head of Engineering at Syncro

How an Empathetic Approach Can Solve Problems

10 November

Han Wang, Director of Engineering at Sonder Inc., shares how he changed a manager’s viewpoint for achieving better results and improved team coordination.

Goal Setting
Personal Growth
Leadership
Coaching / Training / Mentorship
Team Processes
Han Wang

Han Wang

Director of Engineering at Sonder Inc

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.