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

🔥

Back to resources

Influencing People and Getting Your Items Into Their Backlog

Convincing

3 August, 2020

Damian Schenkelman
Damian Schenkelman

Principal Engineer at Auth0

Damian Schenkelman, Principal Engineer at Auth0, discusses how to influence managers and executives to have their teams work on projects that you believe are important.

Problem

As a senior IC, you don't have a team of engineers. Instead, you will have to influence other people to make things happen. While your seniority helps provide some "respect" and a positive halo you still have to make your case to PMs, EMs, and execs. Sometimes what you believe would be beneficial is very different from their current priorities. They are the ones accountable for their team's execution, while you are -- in spite of your seniority -- more of an influencer.

I was interested in having our teams work on a few reliability-related initiatives that I thought would be valuable for us and our customers. What I was lacking were engineers to make my ideas a reality.

Actions taken

First I looked at the data trying to understand what the problem was and understand potential solutions. I analyzed past incidents, the overall state of our system, and customer tickets. I summarized the problem and tailored my message to different audiences: Product Managers (PM) and Engineering Managers(EM), and executives/directors.

When approaching PMs to convince them to add my proposed initiative to the backlog I would typically say: If you do this, you will have fewer interruptions and be able to work on your product backlog for a longer -- and undistracted -- period of time. Also, your customers will be happier because your product will be working all the time.

When talking to EMs I would usually explain how this would reduce reactive work and continuous fire fighting and would result in a more stable product, which means engineers are happier and more productive.

When engaging in conversation with executives I would talk about brand damage, negative impact for the company, and how the system's reliability needs to be on par with other features. I borrowed a hugely persuasive argument from one of my peers, Reliability is the one feature that everyone uses -- if our system is down no other feature is working.

Being aware that teams are usually time-constrained I would pitch solutions in iterative steps, following the 80/20 rule. Instead of just throwing the problem at them, I proposed solutions that would dissect the problem into incremental parts that they could progressively address and that would not consume most of their quarter. With a concrete plan in place, I met with each individual team explaining what we specifically needed from them and also told them I would be available for all of their questions throughout their work on the project.

Lessons learned

  • Align your own goals with the organization’s planning cadence. In our case, it happens quarterly. We discovered much of the problem close to the beginning of the planning cycle and thus were a bit late with presenting it to the teams, which made it harder for them to include it in their backlogs. The sooner you can present the problem to the teams, the better. You want to get to quarterly planning with them knowing about your important work.
  • Whenever you are talking about improvements to "non-functional requirements" it is advisable to tie things to business outcomes and customers’ needs. I would frame the problem around faster and more confident delivery, making customers happy and even upsell add-ons we could offer. I pitched a business case for the add-ons and provided an example longer-term roadmap. Attaching reliability improvements to tangible things like $$ makes it easier to make a case for them.
  • Talk to all stakeholders separately. When lumped together, people tend to behave with a mob mentality and are more likely to resist changes to plans.
  • Don’t leave any of the stakeholders out. If anyone is missing, people will start to speculate why that is the case. That almost happened to me, but then I rushed to talk to a person that I thought I could omit.
  • Don't just talk the talk, walk the walk. If something is important to make yourself available. I would block time in my calendar and would reassure people that they can ping me anytime. If it wasn’t important enough for me, I can't expect that it would be important for them.

Discover Plato

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


Related stories

How to Increase Engagement Using the Right Metrics

11 November

Richard Maraschi, VP of Data Products and Insights at WarnerMedia, speaks on how he increased user engagement using measurements and experimentation.

Alignment
Mission / Vision / Charter
Conflict Solving
Convincing
Team Processes
Data Team
Richard Maraschi

Richard Maraschi

VP Data Product Management at WarnerMedia

How Technical is Your Conversation?

3 November

Sambit Kumar Dash, Founding Director at Lenatics, shares an analogy-based technical conversation.

Managing Expectations
Product
Convincing
Users
Sambit Kumar Dash

Sambit Kumar Dash

Founding Director at Lenatics

How to Successfully Complete A Major Reorganization

4 November

Kirk Gray, VP of Engineering at McGraw-Hill, recalls his experiences performing major reorganizations of departments, including successful techniques to ensure a smooth transition.

Alignment
Convincing
Reorganization
Roadmap
Fairness
Kirk Gray

Kirk Gray

VP Engineering at McGraw Hill

Strategic Ways to Stop Losing Customers

13 October

Mary Fisher, Software Engineering Manager at DrChrono, shares how diligently she worked with teams within her organization to retain customers.

Alignment
Innovation / Experiment
Product
Dev Processes
Convincing
Tech Debt
Prioritization
Mary Fisher

Mary Fisher

Software Engineering Manager at DrChrono

There Is No Commitment Without Disagreement

4 October

Claudio Bartolini, Fellow, Technology and Architecture, Office of the CTO at Equinix, describes how one of his best performers suddenly became disengaged after disagreeing with management over the direction their team would be taking.

Convincing
Team Processes
Claudio Bartolini

Claudio Bartolini

Fellow office of the CTO at Equinix

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.