There are 7 different high-priority issues we're supposed to cover. Stakeholders expect your team to deliver on the roadmap, deal with technical design, do the code reviews, fix critical bugs and support cases, while taking care of the teammates 1:1s, hiring, education, you name it.

At our #8 meetup, we'll cover one of the most repeating topics coming from mentees: Mastering the priority battle.

I want to share a Team Lead Daily Priority Guide I created at Mews for 30+ teams. Why? If followed, it navigates my teams to make the right decision while protecting them and making me, the leader, responsible for the priority.