Always be quitting - jmmv.dev - Deepstash
Always be quitting - jmmv.dev

Always be quitting - jmmv.dev

Curated from: jmmv.dev

Ideas, facts & insights covering these topics:

12 ideas

·

1.05K reads

4

Explore the World's Best Ideas

Join today and uncover 100+ curated journeys from 50+ topics. Unlock access to our mobile app with extensive features.

🤔 Imagine leaving your job on short notice

🤔 Imagine leaving your job on short notice

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.

21

487 reads

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

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

  • “Making yourself replaceable”
  • “Deprecating yourself”
  • "Automating yourself out of your job”

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 👇

20

97 reads

📕 1. Document your knowledge

📕 1. Document your knowledge

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.

21

77 reads

🏁 2. Document your long-term plans

🏁 2. Document your long-term plans

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.

20

52 reads

🎥 3. Document your meetings

🎥 3. Document your meetings

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.

19

56 reads

👬 4. Bring others to meetings

👬 4. Bring others to meetings

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.

19

43 reads

👩‍🔧 5. Train people around you

👩‍🔧 5. Train people around you

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.

19

43 reads

↩️ 6. Identify and train your replacement

↩️ 6. Identify and train your replacement

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.

18

37 reads

🔑 7. Give power to the people

🔑 7. Give power to the people

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.

19

31 reads

📌 8. Do not make yourself the point of contact

📌 8. Do not make yourself the point of contact

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.)

18

46 reads

🤝 9. Delegate

🤝 9. Delegate

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.

19

35 reads

🧠 10. Always be learning

🧠 10. Always be learning

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.

19

50 reads

IDEAS CURATED BY

heisenberg

Digital marketing at dentsu. Invested in the symbiosis of marketing, psychology, and design. Photographer at heart.

Pranav P.'s ideas are part of this journey:

How to properly read a book

Learn more about personaldevelopment with this collection

How to synthesize information from multiple books

How to analyze a book

How to set reading goals

Related collections

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Personalized microlearning

100+ Learning Journeys

Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates