Balancing Multiple Projects at Once

If you ever feel like delegating takes longer than doing it yourself, these are the only models you need! Delegation isn’t about giving work away. It’s about creating a system where your team can perform without constant supervision. Here are 5 proven models that make delegation more effective (and less stressful): 1. The Five Levels of Delegation Every task doesn’t need the same level of oversight. Here’s how to choose the right one: Level 1: Do exactly what I ask. Level 2: Research options and bring me a recommendation. Level 3: Decide, then check in before acting. Level 4: Decide and act - keep me informed. Level 5: Take full ownership; I trust your judgment. 2. The DELEGATE Mode Define the task → Empower → Let them know expectations → Establish parameters → Generate commitment → Authorize resources → Track → Evaluate Structure turns delegation into development. 3. The RACI Matrix Clarify roles: Responsible (who does it) Accountable (who owns results) Consulted (who gives input) Informed (who needs updates) It prevents the “too many cooks” problem. 4. The MoSCoW Method Prioritize before delegating: Must-haves, Should-haves, Could-haves, and Won’t-haves. It helps teams stay aligned when everything feels urgent. 5. The Skill-Will Assessment Before delegating, ask two questions: Do they have the skill? (Yes/No) Do they have the will? (Yes/No) High skill + Low will = They need motivation, not instruction Low skill + High will = They need coaching, not criticism The best leaders don’t hoard work. They design systems where others can thrive, and that’s what real influence looks like. P.S. What’s the hardest part of letting go of control for you?

How I Track 10+ Projects at Once as a Program Manager at Amazon It’s a question I get a lot: How do you stay on top of everything without letting something slip? Different teams. Different timelines. Different deliverables. And a lot of noise. Here’s how I keep it all moving…and still make it home for dinner: 1/ I use one central tracking system for everything ↳ One doc, one view. ↳ If it’s not in the tracker, it doesn’t exist. ↳ I update it daily and keep it brutally simple. 2/ I start every week with a 15-minute self check-in ↳ What’s behind? What’s on track? What’s at risk? ↳ If I don’t do this Monday morning, the week runs me instead of the other way around. 3/ I color-code by priority and risk ↳ Green means I don’t need to touch it. ↳ Yellow means it needs a check-in. ↳ Red means I need to escalate or unblock. 4/ I follow up with context, not just reminders ↳ “Just checking in” turns into “We need this by Friday to keep X on track.” ↳ People respond to clarity, not pressure. 5/ I keep a running weekly update for leadership ↳ 3 bullets: what moved, what’s stuck, and what I need help with. ↳ It keeps everyone informed without another meeting. Managing 10+ projects isn’t about multitasking. It’s about systems, focus, and momentum. You don’t need to know everything. You just need to know where to look…and what to move next. How do you track your priorities without getting overwhelmed?

Project Management Cheat Sheet 1. Key Phases of a Project 1.1. Initiation: Define the project scope, goals, and objectives. Identify stakeholders. Develop a business case or project charter. 1.2. Planning: Create a project plan (scope, timeline, budget, resources). Develop a Work Breakdown Structure (WBS). Identify risks and plan mitigation strategies. 1.3. Execution: Assign tasks to team members. Monitor progress and ensure quality deliverables. Manage stakeholder communication. 1.4. Monitoring & Controlling: Track project performance against KPIs (e.g., cost, time, scope). Manage risks and implement changes. Conduct regular status updates and reviews. 1.5. Closure: Deliver the final product or service. Obtain client or stakeholder sign-off. 2. Common Project Management Methodologies Waterfall: Sequential approach (ideal for predictable projects). Agile: Iterative and flexible (ideal for dynamic projects). Scrum: Framework under Agile with sprints. Kanban: Visual task management using boards. PRINCE2: Process-driven framework focused on control. 3. Essential Documents and Tools 3.1. Documents: Project Charter Project Plan Risk Register Gantt Chart Issue Log Stakeholder Register 3.2. Tools: Task Management: Trello, Asana, Jira Timeline Planning: Microsoft Project, Smartsheet Communication: Slack, Microsoft Teams Collaboration: Google Workspace, Miro 4. Project Management Metrics (KPIs) Schedule Performance Index (SPI): Actual progress vs. planned progress. Cost Performance Index (CPI): Earned value vs. actual costs. Burn Rate: Rate of spending project budget. Milestone Completion: Percentage of milestones completed on time. Customer Satisfaction: Stakeholder or client feedback. 5. Risk Management Process Identify risks (brainstorming, checklists). Assess risks (impact and probability). Plan risk responses (mitigate, transfer, accept, avoid). Monitor and control risks throughout the project. 6. Tips for Effective Project Management Define Clear Objectives: Ensure everyone understands the goals. Communicate Often: Keep stakeholders updated. Prioritize Tasks: Focus on high-value activities. Stay Flexible: Be ready to adapt to changes. Document Everything: Maintain proper records for accountability. Use Technology: Leverage tools to streamline workflows. Evaluate Performance: Regularly review team and project performance. 7. Common Challenges and Solutions 7.1. Scope Creep: Solution: Define scope clearly and use a change management process. 7.2. Poor Communication: Solution: Establish clear communication channels and regular updates. 7.3. Budget Overruns: Solution: Monitor spending closely and manage risks proactively. 7.4. Missed Deadlines: Solution: Use detailed planning and track progress frequently. 7.5. Resource Allocation Issues: Solution: Use resource management tools and prioritize tasks. Keep this cheat sheet handy to ensure you stay on top of your project management responsibilities and deliver successful outcomes!

Frank Slootman built Snowflake by finding "drivers." Keith Rabois scaled multiple companies by hiring "barrels." Different words for the same operator: people who take ownership of hard problems and ship without waiting. Most companies have too few. They add headcount thinking it creates leverage. It does the opposite. Headcount is not leverage. Drivers are. Execution capacity = # of drivers × authority per driver Five drivers can run five initiatives. Add fifty coordinators and you're still stuck at five initiatives. Every hire costs 135 days you can't recover. First Round tracked this: ~45 days to close a candidate, ~90 days before they're productive. Hire the wrong person and you've burned 4.5 months waiting for capacity that never arrives. Here's how to build your startup for drivers: 1. Test for ownership in work trials Give candidates a real problem from your business. Something messy with no obvious answer. Give them a few weeks (or months) and access to your team. Drivers define success without asking you to scope it. They decide and tell you what they decided, not ask what to decide. They ship something real - a prototype, a plan, a first version - not endless meetings. They elevate your team. 2. Structure your drivers as player-coaches, not coordinators Your drivers must stay on the field shipping and leading simultaneously. This keeps decisions close to the work. What this prevents: when drivers stop executing, they become coordinators. More coordinators means more meetings, more alignment, more overhead. But output stays flat because execution still depends on driver count. 3. Assign clear ownership and protect focus Apple puts one Directly Responsible Individual (DRI) on every deliverable. Amazon assigns Single-Threaded Leaders to big bets with protected calendars and full decision rights. Copy both. Write "Driver: [Name]" at the top of every brief. One mission, one owner. If two names appear, neither owns it. Then protect their focus. If your drivers are split across multiple initiatives, the equation breaks. A driver on three projects delivers less than three drivers on one project each. Block their calendars. Limit status updates and meetings. Give them uninterrupted time to execute. Run this audit: List your top 10 projects this quarter. Put one name (the driver) next to each. If you wrote two names, fix it. Verify each driver has real authority to decide and isn't split across projects. Large teams with unclear ownership lose to small teams with concentrated authority. The companies that scale fastest don't have the most people. They have the most drivers with the widest scope.

Here are some realistic KPIs that project managers can actually track : 1. Schedule Management 🔹 Average Delay Per Milestone – Instead of just tracking whether a project is on time or not, measure how many days/weeks each milestone is getting delayed. 🔹 Number of Change Requests Affecting the Schedule – Count how many changes impacted the original timeline. If the number is high, the planning phase needs improvement. 🔹 Planned vs. Actual Work Hours – Compare how many hours were planned per task vs. actual hours logged. 2. Cost Management 🔹 Budget Creep Per Phase – Instead of just tracking overall budget variance, break it down per phase to catch overruns early. 🔹 Cost to Complete Remaining Work – Forecast how much more is needed to finish the project, based on real-time spending trends. 🔹 % of Work Completed vs. % of Budget Spent – If 50% of the budget is spent but only 30% of work is completed, there's a financial risk. 3. Quality & Delivery 🔹 Number of Rework Cycles – How many times did a deliverable go back for corrections? High numbers indicate poor initial quality. 🔹 Number of Late Defect Reports – If defects are found late in the project (e.g., during UAT instead of development), it increases risk. 🔹 First Pass Acceptance Rate – Measures how often stakeholders approve deliverables on the first submission. 4. Resource & Team Management 🔹 Average Workload per Team Member – Tracks who is overloaded vs. underloaded to ensure fair distribution. 🔹 Unplanned Leaves Per Month – A rise in unplanned leaves might indicate burnout or dissatisfaction. 🔹 Number of Internal Conflicts Logged – Measures how often team members escalate conflicts affecting productivity. 5. Risk & Issue Management 🔹 % of Risks That Turned into Actual Issues – Helps evaluate how well risks are being identified and mitigated. 🔹 Resolution Time for High-Priority Issues – Tracks how quickly critical issues get fixed. 🔹 Escalation Rate to Senior Management – If too many issues are getting escalated, it means the PM or team lacks decision-making authority. 6. Stakeholder & Client Satisfaction 🔹 Number of Unanswered Client Queries – If clients are waiting too long for responses, it could lead to dissatisfaction. 🔹 Client Revisions Per Deliverable – High revision cycles mean expectations were not aligned from the start. 🔹 Frequency of Executive Status Updates – If stakeholders are always asking for updates, the communication process might be weak. 7. Agile Scrum-Specific KPIs 🔹 Story Points Completed vs. Committed – If a team commits to 50 points per sprint but completes only 30, they are overestimating capacity. 🔹 Sprint Goal Success Rate – Tracks how many sprints successfully met their goal without major spillovers. 🔹 Number of Bugs Found in Production – Helps measure the effectiveness of testing. PS: Forget CPI and SPI - I just check time, budget, and happiness. Simple and effective! 😊

Scope Clarity for managing complex projects Your project is delayed after the scope blew up again, misalignments revealed themselves late on and people can't agree on what matters. To avoid this from happening it's important to clarify the scope early and often during projects. 1. Define what success looks like Kick off the project by asking key decision-makers: • What do you expect from the project? • What is the ideal outcome? • What does success look like? This will help set a target that you can measure against throughout the project. 2. Seek out disagreement Write down the scope - everything you think is needed to fulfil the goals. Pass your notes around in a brief, readable format and directly ask your stakeholders: • Did I get anything wrong? • Is there anything missing? This way you’ll bring up important details or adjustments that would otherwise be missed. 3. Ship small and check in often When you start delivering, divide your work up into small packages and get feedback regularly before moving too far ahead. Ask explicitly: “Does this help us reach the goal we talked about?” Get this feedback weekly, minimum.

🏗 How To Tackle Large, Complex Projects. With practical techniques to meet the desired outcome, without being disrupted or derailed along the way ↓ 🤔 99% of large projects don’t finish on budget and on time. 🤔 Projects rarely fail because of poor skills or execution. ✅ They fail because of optimism and insufficient planning. ✅ Also because of poor risk assessment, discovery, politics. 🎯 Best strategy: Think Slow (detailed planning) + Act Fast. ✅ Allocate 20–45% of total project effort for planning. ✅ Riskier and larger projects always require more planning. ✅ Think Right → Left: start from end goal, work backwards. ✅ For each goal, consider immediate previous steps/events. ✅ Set up milestones, prioritize key components for each. ✅ Consider stakeholders, users, risks, constraints, metrics. 🚫 Don’t underestimate unknown domain, blockers, deps. ✅ Compare vs. similar projects (reference class forecasting). ✅ Set up an “execution mode” to defer/minimize disruptions. 🚫 Nothing hurts productivity more than unplanned work. Over the last few years, I've been using the technique called “Event Storming” suggested by Matteo Cavucci to capture user’s experience moments through the lens of business needs. With it, we focus on the desired business outcome, and then use research insights to project events that users will be going through towards that outcome. On that journey, we identify key milestones and break user’s events into 2 main buckets: user’s success moments (which we want to dial up) and user’s pain points or frustrations (which we want to dial down). We then break out into groups of 3–4 people to separately prioritize these events and estimate their impact and effort on Effort vs. Value curves (https://lnkd.in/evrKJUEy). The next step is identifying key stakeholders to engage with, risks to consider (e.g. legacy systems, 3rd-party dependency etc.), resources and tooling. We reserve special timing to identify key blockers and constraints that endanger successful outcome or slow us down. If possible, we also set up UX metrics to track how successful we actually are in improving the current state of UX. When speaking to business, usually I speak about better discovery and scoping as the best way to mitigate risk. We can of course throw ideas into the market and run endless experiments. But not for critical projects that get a lot of visibility — e.g. replacing legacy systems or launching a new product. They require thorough planning to prevent big disasters and urgent rollbacks. If you’d like to learn more, I can only highly recommend "How Big Things Get Done" (https://lnkd.in/erhcBuxE), a wonderful book by Prof. Bent Flyvbjerg and Dan Gardner who have conducted a vast amount of research on when big projects fail and succeed. A wonderful book worth reading! Happy planning, everyone! 🎉🥳

Used right, OKRs can be the most powerful product process. But most orgs completely mess them up. From driving empowerment to becoming tools for control… Here’s what you need to know about when to add or remove OKRs: — 𝗧𝗵𝗲 𝗗𝗲𝗯𝗮𝘁𝗲 𝗔𝗿𝗼𝘂𝗻𝗱 𝗢𝗞𝗥𝘀: 𝗔 𝗗𝗲𝗲𝗽𝗲𝗿 𝗧𝗿𝘂𝘁𝗵 𝗔𝗯𝗼𝘂𝘁 𝗔𝗹𝗶𝗴𝗻𝗺𝗲𝗻𝘁 The conversation around OKRs reveals a fundamental truth: Alignment mechanisms aren’t one-size-fits-all. Take Ramp, for example. They built a $10B company without OKRs. Their secret? → Exceptional product sense. → Metrics so clear that every team understood what success looked like without needing a formal framework. Now look at Google. They lean heavily on OKRs to manage their complex operations across multiple stakeholders. Without OKRs, their vast ecosystem would fall out of sync. — 𝗖𝗼𝗿𝗲 𝗣𝗿𝗶𝗻𝗰𝗶𝗽𝗹𝗲𝘀 The best OKRs are built on three simple principles: Measurable → Clear metrics that actually track progress. If you can’t measure it, it’s not a key result. Aligned → Tied directly to company goals. Teams rowing in different directions only create chaos. Ambitious → Stretch goals that inspire action, not just check-the-box deliverables. Now let’s unwind it all with an example: — 𝗔 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗘𝘅𝗮𝗺𝗽𝗹𝗲 Objective: Establish our product as the go-to solution for enterprise customers. Key Results: → Expand the enterprise customer base by 50%. → Attain a 95% satisfaction rating from enterprise users. → Roll out 3 enterprise-specific features with an adoption rate of at least 80%. — 𝗧𝗶𝗽𝘀 𝗳𝗼𝗿 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝘄𝗶𝘁𝗵 𝗢𝗞𝗥𝘀 To make OKRs work for your team, focus on execution, clarity, and simplicity. Here’s how: → Review and adapt regularly OKRs aren’t “set it and forget it.” Treat them like a product roadmap. Revisit them often to ensure relevance and make adjustments as priorities evolve. → Keep objectives aspirational but grounded Objectives should inspire, but don’t make them so lofty they feel unattainable. Balance ambition with realism to keep teams motivated and focused. → Make key results measurable and meaningful A good key result isn’t just measurable; it’s directly tied to your objective’s success. Avoid vanity metrics and focus on outcomes that genuinely reflect progress. → Tie OKRs to the bigger picture Ensure every team’s OKRs are aligned with company-wide goals. Without alignment, you’ll have teams running in different directions. — 𝗧𝗶𝗺𝗶𝗻𝗴 𝗳𝗼𝗿 𝗢𝗞𝗥𝘀 → Quarterly OKRs Create a cadence that fits your team’s execution cycle and allows for focus. → Monthly Check-ins Use these to measure progress, uncover blockers, and course-correct as needed. → End-of-Quarter Retrospectives Reflect on what worked, what didn’t, and how to improve OKRs for the next cycle. — Want to learn how OKRs work and uncover the 11 other most important product processes from three product leaders... Go here: https://lnkd.in/e9f-mDzr

Your team just spent 3 weeks studying how users navigate your checkout flow. Plot twist: Someone already did this study 6 months ago. 😅 Redundant research is a silent productivity killer. Here are 5 tips to avoid it.  🔁 Check existing data first Before jumping into a new study, ask around. Someone in your org might already have the answers you need. Go into support tickets, analytics data, sales call recordings and previous research studies. 📍Map research to product areas Building your checkout flow? Tag all studies that touched on payment. Creating an onboarding? Link every study about new users. At least keep a simple spreadsheet connecting features to research. Next time someone asks, you'll know exactly where to look. 🗓️ Do 'Research Retros' quarterly Get teams in a room. Share what everyone's been studying. Spot overlaps before they happen. Bonus: Great for cross-team learning! ⚡ Build a "Frequently Asked Research Questions" list What do stakeholders keep asking about? Where are the repetitive requests coming from? Update this living doc regularly. Share it before kick-off meetings. 🏮 MOST IMPORTANTLY, build a repository. The ultimate solution to prevent duplicate work. Store everything in one place. Make it searchable. Find insights in seconds. Get started with this definitive guide to building and maintaining a research repository here: https://bit.ly/3ExoGwR Also, here’s a repository tool that lets you do Google-like search for data snippets across projects.  https://bit.ly/4aWpqI7

Have you ever spent endless hours on a project just to end up realising that a more straightforward method would have been more effective? This common mistake, referred to as over-engineering, can cause needless complexity and inefficiency when developing new products. Understanding Over-engineering > Over-engineering happens when a solution gets more difficult than it needs to be, usually by adding features or functionalities that do not directly meet the needs of customers. > This can lead to higher costs, longer development cycles, and less user-friendly products. Real-World Example: The Juicero The Juicero, a high-tech juicing machine, was released in 2016. It cost $700 and was designed to squeeze proprietary juice packets with considerable force. Later on, though, it was found that the costly machine was not essential because the same juice bags could be squeezed by hand. The company was eventually shut down as a result of the public outcry following this disclosure. My Own Story: The Overly Complex Website I was in a team early in my career that was assigned with creating a company website. We included the newest interactive elements and design trends in an effort to wow. Feedback received after the launch, however, indicated that visitors found the website overwhelming and challenging to use. In our pursuit of innovation, we had failed to realise the website's main purpose, which is to provide easily comprehensible information. I learnt the importance of simplicity and user-centred design from this experience. Useful Tips to Prevent Over-Engineering 1. Pay attention to the essential needs: Focus on key features that meet user needs and clearly explain the issue you're trying to solve. Don't include features that aren't directly useful. 2. Adopt Incremental Development: Begin with an MVP that satisfies the fundamental specifications. By using this method, you may get user input and decide on new features with knowledge. 3. Put Simplicity First: Use the KISS philosophy, which stands for "Keep It Simple, Stupid." Simpler designs are frequently easier to use and more efficient. 4. Verify Assumptions: Talk to users to learn about their wants and needs. This guarantees that the things you create will actually be useful to them. 5. Promote Open Communication: Create an environment where team members are at ease sharing thoughts and possible difficulties. Over-engineering tendencies can be recognised and avoided with the support of this collaborative environment. Have any of your initiatives involved over-engineering? How did you respond to it? Post your thoughts and experiences in the comments section below!