Senior to staff engineer curriculum, part 2 of many: Delegation

 Session 1: delegation

Let’s talk about different types of delegation.  Please read:

https://medium.com/@jurgenappelo/the-7-levels-of-delegation-672ec2a48103 


Prompts for discussion

  • When people delegate to you, what level are they using?

  • When you delegate to others, which ones are you using?

    • How is this different for Senior compared to Staff engineers?

  • What happens if you think you’re using one and the other person thinks it’s a different one?

  • How can you tell when you’re at the wrong level? (I.e. micro or macro managing)

  • How do you set up guardrails after you’ve delegated, to make sure things are on track?

  • How is delegating to LLMs different to people?


Homework:

  • The next time you’re delegating, or being delegated to, pause and think about which one of these levels you’re at.  Then, confirm it with the other person and see if you’re right.

Comments

Post a Comment

Popular posts from this blog

Introduction

 Once upon a time there was a whole series of interesting books about leaning programming languages that followed the same loose format: a series of related practical tips for using them well and avoiding pitfalls. This blog is all about Staff+ software engineering and it'll try to follow the same basic format.  Each post will have a concrete tip.  A few things to note: I'll be typing the words here but many of the ideas are from other people.  I'll be linking out to their docs or websites and putting credits wherever I can.  If I miss one then please let me know and I'll fix it. This isn't written by AI, it's just me and a keyboard. This will always be free here. I'm leaving comments off for now as I'm comfortable with this being write-only and don't want to try moderating them. No ads. For fun, here are a few links to some of the books: Effective C++ Effective Java
Read more

Influence, part 4 of 5: Tactical tips

 This is the fourth part of a five part series on influence as a Staff+ Software Engineer ( part 1 ,  part 2 ,  part 3 ,  part 4 ,  part 5 ).  I've ported this here from where I  originally published it on Medium .  Tactical tips Give credit If in doubt, add a credits section to your docs and presentations to thank the people who have worked on something with you. It’s likely that you’ve been talking to them to refine your ideas and make plans, and it’s only polite — they’ll be far more likely to work with you in the future and share ideas. The combined wisdom of these people is likely to be greater than your own. This shouldn’t be a zero sum game, even when it comes to design docs for perf. It’s entirely fair to ask others to also include credits sections. Write the doc and know how to circulate it If you have a good idea then put it into a one page doc. Bonus points if you can actually make it one page long! This is good for a few reason...
Read more