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

🔥

Back to resources

How to Improve Remote Work Environment

Collaboration
Roadmap
Data Team

15 September, 2021

Bertrand Dubaut
Bertrand Dubaut

Director of Engineering at Zivver

Bertrand Dubaut, Director of Engineering at Zivver, explains his strategies and plans to improve the office environment and how to work faster even when working remotely.

Problem

As a director, or even as a manager, it is important to periodically review your team’s morale. My team’s morale was exponentially deteriorating, the whole business side of the company was not happy with the deliveries, and the quality was going down. After I arrived on the team, I realized that these people were brilliant and knew what they were doing, and they needed some guidance.

Then I opened the project management system, and 26 items were in progress. Nothing was getting done, and the customer success cycle kept on adding more things. They were overwhelmed by overly lengthy plans, but they had paused the roadmap for twelve weeks. At that point, sales and marketing teams were unhappy about it. Again, the team itself was striking. They had no idea how they got to this point but I knew why that was happening.

Actions taken

The first thing that I did, and I try to do this every time I am faced with a problem, was to make sure I highlighted the actual issue with data. We began gathering data together as a team, limited our work in progress, and started to track our unplanned work more diligently. After a couple of months, we managed to recover a more constant pace of delivery for the team who now understood how unplanned work is a killer for productivity. We went from a 6-month release cycle to a 4-week team much happily, and now stakeholders were much more comfortable.

In order to help a team understand the value of limiting the work in progress and the benefits of a constant delivery pace, there is a small exercise I like to do with my teams (this works better in a non-remote environment). Set the team around a large table, and give 10 coins to the person at one end of the table. The goal is to pass those coins from one end of the table to the other end as quickly as possible by passing the coins to the team member next to them. However, there is a catch: every person that touches the coins needs to count them when they receive them. The team started counting from 1 to 10 and passed all 10 coins at once. WeI intended to teach them the notion of restricting working progress, which implied that doing less simultaneously means that we will be faster in the end, even though it feels slower. To do that, they passed all the 10 items at once. We timed it. Then, I asked them to pass the coins 1 by 1. Surprise! the time it took to have all the coins go across the table was much faster! This showed the team the value of having a WiP limit.

Lessons learned

  • Engineers might not be “pro” when it comes to collaboration or teamwork. Collaboration is something that is never really taught to engineers (after all, I do not know a lot of people who went into software engineering because they liked people). It’s important to spend time understanding the team and how to make this group of individuals work together, so their impact can be greater than the sum of its parts.

Discover Plato

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


Related stories

Specialization vs. Wearing Many Hats

23 November

William Bajzek, Director of Engineering at Sapphire Digital, compares and contrasts a team structure that utilized siloed skill sets and one where everybody’s duties overlap at the edges.

Internal Communication
Collaboration
William Bajzek

William Bajzek

Director of Engineering at Sapphire Digital

Mergers and Acquisitions: Collaboration tools hold a key to bringing cultures together

23 November

Neelima Annam, Sr Director Information Technology at Outmatch, shares how something as minor as collaboration tools can be a BIG issue during mergers and acquisitions.

Acquisition / Integration
Internal Communication
Collaboration
Neelima Annam

Neelima Annam

Sr. Director Information Technology at Outmatch HCM

How to Build Rapport With an Introverted Manager

17 November

Piyush Dubey, Senior Software Engineer at Microsoft, shares his journey of climbing up the career ladder through awkward times dealing with an introverted manager.

Managing Expectations
Internal Communication
Collaboration
Coaching / Training / Mentorship
Juniors
Piyush Dubey

Piyush Dubey

Senior Software Engineer at Microsoft

The Benefits of Stakeholder Communication

17 November

Piyush Dubey, Senior Software Engineer at Microsoft, shares how to understand the stakeholder communication process better and why it is essential.

Meetings
Internal Communication
Collaboration
Ownership
Stakeholders
Piyush Dubey

Piyush Dubey

Senior Software Engineer at Microsoft

How to Work With People Who Are Different Than You

11 November

Rajesh Agarwal, VP & Head of Engineering at Syncro, shares how effectively he collaborated with a newly-joined team as a diverse candidate.

Acquisition / Integration
Leadership
Collaboration
Cultural Differences
Rajesh Agarwal

Rajesh Agarwal

VP and Head of Engineering at Syncro

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.