Creating a virtuous cycle of communication and motivation with your reports
18 July, 2018
As a leader of a growing organization it becomes increasingly difficult to know what is happening across your team. I was responsible for work streams spanning product engineering, infrastructure, DevOps, IT, as well as organizational projects such as hiring, performance evaluation, and leadership development. I had to report on status of this work to the exec team every monday morning and felt I didn't have enough context to honor the hard work of the teams.
To start with I asked team leads to send me a weekly update every Friday. I asked them to provide 5 things:
- updates on metrics you are tracking
- what happened
- what's next
- challenges and risks
- lessons learned My plan was to read them over the weekend, identify the patterns and trends, and synthesize highlights for the exec team. Getting people to send these reports felt like pulling teeth. Thinking through Duhigg's habit cycle — cue > behavior > reward — I realized we had a cue (an email from me) but no reward. There wasn't enough intrinsic motivation to make the habit sticky and there wasn't the ability to learn from each other by seeing what others were writing. I shifted things to a two-week cycle and started synthesizing a report to send to the whole company. Each team would have their own section and if they didn't send me an update there'd be a "no update this cycle" placeholder. Folks across the company said they loved getting the update on what the engineering teams were doing and the teams felt like they were getting more recognition for their work.
When trying to create new habits and adjust behaviors, think through motivations and rewards. Requiring compliance is not good enough for quality work. Look for ways that a behavior can satisfy multiple needs.
Kevin Perko, Head of Applied Research and Data Science at Scribd, discusses how he made his employee successful by helping them transition into a more suitable and challenging role.
Head of Applied Research / Data Science at Scribd
Matt Pillar, VP of Engineering at OneSignal, recalls how he helped merge two engineering teams at two different locations and how legal and cultural context made all the difference.
VP Engineering at OneSignal
Jackson Dowell, Engineering Manager at Asana, explains how he moved his project forward by coming up with a clear model of the system and problem that provided guidance to the team and helped communicate their efforts outward.
Engineering Manager at Asana
Ido Cohen, Head of Product at Permutive, discusses the importance of solving the right problems and how failing to identify them can lead to misuse of resources and lost opportunities.
Head of Product at Permutive
Toby Delamore, Product Manager at Xero, explains how skip-level conversations and maintaining an attentive relationship with engineers enabled him to keep a finger on the pulse of the team.
Product Manager at Xero
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.