Eran Arkin
4y ago
Visit me to learn about Tech Careers, Product Management More. Experienced operator; Beginner online writer. Dad.
Humans evolve to multitask (i.e., breastfeed while walking), but multitasking isn't suitable for tasks with a high cognitive load.
There's contradictory advice in popular productivity books: Eating the frog popularized the idea of doing one thing at a time (with the most difficult first!). Yet Getting Things Done argues for doing any task that comes if it takes less than two minutes.
Research shows that you shouldn't try to do two things at the same "atomic unit of time" (participate in a meeting while attempting to finish PRD for another project), which will increase the error rate and waste time. BUT the reality of a product manager's work is that they are part of multiple project teams.
"Great things in business are never done by one person, They are done by a team"
Since our job is interdependence, it's impossible to do one project at a time. PMs often wait for other functions to complete their work or an experiment to end. Finally, there are some real benefits of working on a few things:
Allows your mind to process things offline and develop better ideas.
Some tasks are inherently easier than others, so switching provides a mental break from difficult tasks.
Here's how to be productive while driving multiple projects:
First, ruthlessly prioritize limiting the number of projects. Align with your teams & manager on these high-priority projects. If there are still too many, discuss who can drive the project. You'll be pleasantly surprised as teammates will step up!
Shreyas proposed the 3-5-7 framework: each individual has three main projects they are working on. Research shows that individual and team performance has benefited from a limited number of multiple team memberships, particularly for more experienced employees, due to an increased focus on working efficiently, and transfer of learning experiences.
Once you decide on the highest priority projects, here are a few more tips:
Tip #1: Preserve your state in writing. Much like memory-cache helps computers retrieve the information they are likely to need faster. Writing enables you to create your memory cache to minimize switching costs after you are done working on a specific project and BEFORE you switch jot down where you are.
Tip #2: Have a system to review all projects weekly. Set a time to check status (Friday afternoon is my favorite time since it allows me to preserve state for next week).
Tip #3: Set deadlines for dependencies Deadlines contribute to accelerating the pace of group work. Use them effectively to understand when to switch.
Tip #4: Allocate thinking time per project. When I worked on Google Travel, I ran two big initiatives with multiple projects. Over time I learned to allocate a few half days every week to each separately, which was immensely helpful.
To recap - As a Product Manager, you have to switch between tasks & projects effectively. I laid some ideas that worked well for me, and I would love to learn what worked for you!