18 Comments
Feb 23Liked by Ryan Peterman

My boss called this, “Being a force multiplier”. If the whole team produces more when you are on it you are a force multiplier. Great post!

Expand full comment
author

Thanks John! "Being a force multiplier" is great way to put it

Expand full comment

Superb article. I think giving tech talks to your team/org is underrated. There have been cases where I refer to a tech talk months after it was given because it became relevant to me later on, which is a huge win for the maker of the talk.

Expand full comment
author

Thanks Leo! Agreed, the slides themselves often become a helpful resource

Expand full comment

I am actually going to share importance of tech talks in few days, you will love it.

Expand full comment

Documenting processes and explanation of data systems on tools such as 'Confluence' have been useful for me at work. It reinforces my knowledge and helps me articulate complex systems to other stakeholders...

Expand full comment

My ex-boss used to tell me that my individual performance was less important than the collective performance of the team

Expand full comment
author
Feb 27·edited Feb 27Author

Agreed with your ex-boss; this is true for more senior engineers

Expand full comment

Thank you for another thought-provoking newsletter, Ryan! The concept of scaling oneself is crucial, and your practical strategies, especially on knowledge sharing and building tooling, are gems for engineers at all levels. Looking forward to more insightful content!

Expand full comment
author

Happy to, thanks!

Expand full comment

Scaling yourself is the only way you can grow yourself (and others). The only sustainable strategy. I have written something similar here - https://open.substack.com/pub/buildtechcareer/p/how-helping-others-skyrockets-your?r=6lkk8&utm_campaign=post&utm_medium=web

Expand full comment

You are absolutely right

Expand full comment

There are some great tips in here, thank you!

Just recently I started recording the onboarding presentations that I'm doing, so that they can be used later on to speed up the process. Next to that, since i'm transitioning into a mid-level / senior role, i'm also trying to spend more time documenting thought processes and design decisions to help the learning of our junior members

Expand full comment
author

> started recording the onboarding presentations that I'm doing, so that they can be used later on to speed up the process

This is great, sounds like a good resource that can be reused many times. Thanks for reading!

Expand full comment

Excellent tips Ryan, especially about building tooling and improving the docs, those can essentially "replace" you and serve others when you're not present. Although, working in small startups all my life, never anyone told me "scale yourself" but "we should clone you". 😃

Expand full comment
author

That resonates; "cloning yourself" is a great way to have more impact

Expand full comment

Do you think that platform teams often have better chances with third option because thats their day to day job.

Expand full comment
author

I think so; It depends on the specific situation but I've seen plenty of examples of infra/platform engineers that have massive impact that way. They have a lot of leverage since they help many engineers move faster.

Expand full comment