Everyone loves a game or sports. To play, to watch, to comment, to admire - you might like all or some, but I can bet you like games. The question is why do we like games or sports. It has clear rules, you complete a game when the rules say you complete a game. There is no ambiguity about it, no underlying intangibles. You score, you win. Some games are team games and some are solo games but each type definitely has one thing in common - a goal and of course a way to measure the goal. Game-set-match, number of points, score, goals, time, runs etc.

I like to (not easy) convert each project (a feature or a product) to a game - "What does winning look like in this game (or round)?". There are larger goals and there are smaller goals. Like in football - the larger goal is to score more goals than the opposition to win a game, but the smaller goals are more tactical - successful passes, goal shots, defense etc. Like that, a project goal can be adoption or cost savings to customers and smaller goals could be intuitiveness, reliability, load time etc. Once you have these goals of the project and what the scoreboard (and the rules) looks like, the choices become easy.

Second, the thing about thinking of work as a team game is that you understand that you have to pass the ball to other players who are good at their specific 'jobs' to move forward towards the goal post or basket (basketball).
- You are the PM; you spend time in research and write the PRD (PM dribbles)
- You pass the PRD to Engg (the ball is with engg)
- Engg has questions in the PRD (ball is back with you)
- you answer, unblock the team and pass the ball back.
- while this is happening, you and the team are making progress towards the basket.
You can't always have the ball with you at all times. You do what you do best and when your role is done, you pass the ball to the other player who is good at the next phase.

Make progress everyday towards your goal(s)! Be sure to understand the rules and have a scoreboard.