As with most things, I think the answer here is "it depends". Is a similar blocker likely to reappear in the future? Is it one-off task that's unlikely to recu

As with most things, I think the answer here is "it depends". Is a similar blocker likely to reappear in the future? Is it one-off task that's unlikely to recur? Is it something that will have to be maintained by the team? Is it a task that would put you in the "hot path" of your team's project (e.g. could the team get blocked by you if you get sidetracked)? Is there a way for you to turn the task into a learning/growth opportunity for the team? There are some tasks that are worth being picked up by the lead, the hard part is identifying which fall into that category! For myself, I like to pick up tasks only when they meet the following criteria: 1. The team can never be blocked on me (this is a "golden rule" for me, I never violate it) 2. The task is a "force multiplier" (completion of the task will enable the team to do more with less time/effort in the future) 3. The task requires experimentation 4. There are many potential ways to complete the task, but most are likely to be sub-optimal (and, due to 3., it's difficult or impossible to tell them apart!) In my experience, these tasks have a hugely outsized impact on the overall efficacy of the team. Consider my primary role is to make the team run effectively, it's fitting that I should be willing to take on this type of work!