Establish mailing lists or other forms of communication that can accommodate other people, and then grow those groups. (The exception is when management needs names for accountability.)

📌 8. Do not make yourself the point of contact

In the same vein as training others, to switch roles you’ll need to replace yourself. Identify who that replacement might be and actively and continuously coach them.

↩️ 6. Identify and train your replacement

The goal is for them to be independent (what is usually considered “seniority” in a typical engineering ladder). Familiarize them with the plans and technologies and make sure they know how to use the documentation.

👩‍🔧 5. Train people around you

Once you have given power to others, included them in groups and meetings, and documented your knowledge, they’ll be ready to take work from you. Delegate work that can make them grow and focus on the things only you can do.

🤝 9. Delegate

Trust them to do the right thing. If you are in a leadership position, don’t make it so people come to you asking for permission. Let them make their own choices. Guide them so that their choices are based on the right data.

🔑 7. Give power to the people

Take the chance to grow your knowledge in any area you are interested in, and keep it fun. Bonus points if that area aligns with the future path you want to take.

🧠 10. Always be learning

People should know what’s coming up in your projects and/or team by looking at those plans, not by relying on you to tell them “in real time”. Plan a few months ahead so, if you leave, your peers won’t be lost from day one.

🏁 2. Document your long-term plans

If not a 1-on-1 and you are the only person from your team attending a meeting, involve someone else. Different perspectives are useful, but more importantly, you are avoiding becoming the only point of contact.

👬 4. Bring others to meetings

Every time someone asks you a question, they are highlighting a gap in the documentation. Take the chance to write the answer down (in a document, sheet, note, code, comment, etc.) so that the next person doesn’t need YOU.

📕 1. Document your knowledge

A good philosophy to live by at work is to “always be quitting”. No, don’t be constantly thinking of leaving your job 😱. But act as if you might leave on short notice 😎.Counterintuitively, this will make you better at what you do and open up growth opportunities.

🤔 Imagine leaving your job on short notice

<ul><li>“Making yourself replaceable”</li><li>“Deprecating yourself”</li><li>"Automating yourself out of your job”</li></ul>In short, being disposable to free yourself to grow into a higher-level role and make it easier to change the projects you work on. Confused still? Here are 10 specific things you can do 👇

🙅‍♂️ What does it mean to "always be quitting"?

Keep (public, within the team) notes for all meetings you attend, listing who was there, what was discussed, and any conclusions. Reference those notes from design documents. Your replacement will need these to catch up.

🎥 3. Document your meetings

A good philosophy to live by at work is to &ldquo;always be quitting&rdquo;. No, don&rsquo;t be constantly thinking of leaving your job 😱. But act as if you might leave on short notice 😎. Counterintuitively, this will make you a better engineer and open up growth opportunities. A thread 👇.


👬 4. Bring others to meetings

Similar ideas to 👬 4. Bring others to meetings

No big meetings

Meetings with too many people

How to Use System 1 and System 2 Thinking Together