Balancing Multiple Projects at Once

People often ask how we manage complex projects as a team of 100 people in 35 countries, and since I'm currently revamping our documentation on this subject, that info is top of mind. Here's 29 pages of content condensed into 1 LI post for a sneak peek into our DO (Doist Objectives) System 👀 It starts with our annual roadmap, which the leadership team builds in Q4 of the prior year. To execute that plan, we organize our work into four areas of priority (Strategic Priorities, aka SPs), each running multiple initiatives simultaneously in quarterly "cycles", and overseen by a Directly Responsible Doister (DRD): • Brand (DRD: CMO): Marketing campaigns, brand evolution, growth initiatives • Product (DRD: Head of Product): New features, user experience improvements, product strategy • Engineering (DRD: CTO): Platform stability, performance optimization, technical infrastructure • Doist (DRD: 🙋🏻♂️): Internal tools, company operations, team effectiveness Planning kicks off four weeks before each quarter when the CXOs provide the DRDs with general guidance and goals. We respond by proposing general plans for DOs (Doist Objectives; projects/initiatives) in line with our annual roadmap. Two weeks before the new quarter begins, the DOs are agreed upon and the team Heads assign team members to cross-functional "Squads" as "Squad Leaders" and "Squad Members". **See photos below to illustrate the squad infrastructure. Each SP typically runs 2-5 major DOs per quarter, meaning we're executing 12-16 significant projects at any time. The quarter begins with a two-week "Foundation Phase", where squads: • Deep dive into the challenges and opportunities their squad faces • Conduct user research • Create comprehensive specs detailing their proposed solutions • Align on execution approach • This phase ensures we have the space to avoid diving too deep into the upcoming cycle while working on the current cycle From there, squads maintain momentum for the following 10 weeks in the "Execution Phase" through established rituals: • Weekly "snippets" in Twist for progress updates and transparency (our version of an async standup meeting) • Bi-weekly recorded demos to showcase work in-depth • Monthly retrospectives on squad health for continuous improvement • Monthly companywide updates on each strategic priority's DOs • Monthly strategic reviews/adjustments by the leadership team • Expectation = each squad should "ship" something weekly Of course, we manage most of this using Twist for communication and Todoist for project management, but more so than the tools, this system works for us because we emphasize clear ownership/autonomy, transparent communication, and just enough processes to stay coordinated without slowing the team down. That was a lot to digest, but I hope it's helpful. Let me know if I can expand on anything or answer any other questions 👇

Stuck in an endless loop of client changes? Lost track of what revision this constitutes? Yeah. Been there. Done that. The secret? It's not about saying no. It's about saying yes to the right things upfront. Every project that goes sideways starts the same way: Vague agreements. Fuzzy boundaries. Good intentions. Six weeks later you're bleeding money and everyone's frustrated. Here's my framework after 30 years of running two 8-figure businesses: The SOW is your salvation. Not some boilerplate template. A real document that covers: • Exact deliverables (not "design work" but "3 homepage concepts, 2 rounds of revisions") • Hours of operation ("We respond M-F, 9-5 PST. Weekend requests get Monday responses") • Revision rounds spelled out ("Round 1 includes up to 5 changes. Round 2 includes 3.") • Feedback cycles defined ("48-hour turnaround for client feedback or the project may be delayed or additional fees may be incurred") But here's what most people miss— Don't work on client notes immediately. Client sends 37 pieces of feedback at 11pm Friday? Producer sends conflicting notes from the CEO? Marketing wants one thing, sales wants another? Stop. Collect everything first. Resolve the conflicts. Get on the phone and discuss it with your client to get alignment. Separate the "have to haves" from the "nice to haves". Then present unified changes. "Based on all feedback received, here are the 8 changes we'll implement. This constitutes revision round 2 of 3." Watch how fast the random requests stop. No extra work that goes unappreciated. No more feelings of being taken advantage of. Communicate before the crisis, prevents the crisis from happening. "Just so you know, we're entering round 2. You have one more included. After that, it's $X per additional round." No surprises. No awkward money conversations. No resentment. Scope creep isn't a them problem. It's a you problem. And that's good news, because that means you are in control. They're not trying to take advantage. They just don't know where the boundaries are because you never drew them. Draw the lines early. Communicate them clearly. Everyone wins. What's your most painful scope creep story? What boundary would've prevented it? Small Business Builders #projectmanagement #clientmanagement #businessgrowth

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?

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! 😊

30 60 90 Day Plans can be a very useful and simple method to drive specific process improvement projects or initiatives I generally use them to plan out specific projects and goals within an overall Continuous Improvement (CI) approach. 💠 I start with identifying a specific issue, and then breaking down the plan into three phases- 30 days, 60 days and 90 days. That's all kept very high-level, as in the visual below. 💠 The first 30 days are usually focused on learning and planning, the next 30 days are focused on implementation and monitoring and the final 30 days are focused on evaluation and optimization. The whole approach is kept in line with Lean Six Sigma thinking: PDSA- Plan Do Study Act and DMAIC- Define, Measure, Analyze, Improve, Control. 💠 Beyond the high-level plan, it's important to get into the nitty gritty details of improvement. This involves setting specific milestones for the end of each of the 30 day periods and agreeing roles and responsibilities with each team member. 💠 It is REALLY important to have systems and processes that support scheduled check-ins. If you are using cycle planning, the team must agree how they will communicate and collaborate. It may be a mixture of daily huddles, weekly team meetings, 1:1's or something else. 💠 It helps to use simple project management tools (e.g. Trello, Asana, or Microsoft Project) to visualize progress and manage tasks. Just make sure that support is high if people are unfamiliar with the technology as technology could be barrier otherwise! 💠 I like to keep it simple and at the end of each 30-day period, review the progress made towards the milestones. Discuss what worked well and what didn’t, and use these insights to improve the next phase. 💠 Remember to recognize all efforts and celebrate the achievements at each milestone. 💠 And when it comes to evaluation, conduct a thorough review of the entire initiative at the end of 90 days. Assess the outcomes against the original objectives. Gather feedback from the team on the process and outcomes to inform future projects. 💠 Really importantly, build in a continuous improvement approach to your process management. Establish a routine of regular feedback, monitoring, and adaptation to continually improve the process. Have you any experience with cycle planning? Have you any tips for people? Leave your thoughts in the comments 🙏 #changemanagement #strategicplanning #goals #continuousimprovement #cycleplanning #projectmanagement

🏗 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! 🎉🥳

How to Use Earned Value Management (EVM) for Project Tracking and Execution :- _______________________________ Earned Value Management (EVM) is a powerful tool for project managers to monitor, assess, and control the progress of projects. It provides a clear picture of project performance and enables timely corrective actions, ensuring projects stay on track to meet objectives. 🎯 The Power of EVM :- EVM allows project managers to measure project performance by integrating three key metrics:- 1️⃣ Planned Value (PV) :- The budgeted cost for work scheduled. 2️⃣ Earned Value (EV) :- The value of the work actually performed. 3️⃣ Actual Cost (AC) :- The actual cost incurred for the work performed. ✅️ By comparing these metrics, project managers can calculate crucial indicators like :- 4️⃣ Cost Performance Index (CPI) :EV / AC. 5️⃣ Schedule Performance Index (SPI) : EV / PV. ✅️ These indices provide actionable insights :- ✔️- CPI > 1 indicates the project is under budget. ✔️- SPI > 1 indicates the project is ahead of schedule. 💡 Real Case Study :- For a mega infrastructure project in the Middle East, a leading construction firm applied EVM during its execution phase. Using EVM for performance tracking, the project manager identified early discrepancies between planned and actual progress, preventing potential cost overruns and delays. By identifying areas of improvement, they managed to increase project efficiency by (12%), ensuring the project completed on time and (5%) below budget. 📊 Key Statistics :- ✔️- (75%) of successful projects in the construction industry use EVM for project tracking and performance management. ✔️- (58%) of projects that do not use EVM tools report delays and budget overruns. 🔆 By adopting EVM early in the project lifecycle, companies can reduce risks and improve the likelihood of achieving both scope and financial goals. 🎯 Best Practice Tip :- ➡️ To fully harness the power of EVM, integrate it into your project management processes from the start, track progress regularly, and use it to make data-driven decisions to stay within scope, time, and cost constraints. 🚨 EVM isn't just about tracking performance – it's about transforming data into actionable insights for better project execution. --------------- ➡️ If you found this post useful, feel free to like 👍, comment 💬, or share ♻️ — and follow me for more insights on Projects and Contracts Management. #EmadRamadan. #IMPM.

Scope creep can come from anywhere, and when it hits, it can derail any project and push it to its doom. How to avoid this? We’ve all been there. The scope was “finalized,” everyone agreed on it, and yet suddenly… new bells and whistles sneak in. But where does it come from? Surely we don't want to change the rules of the game in the middle of it? 1) Late stakeholder requests A senior leader suddenly remembers “just one more thing” they promised to a client. The team has no real option but to fit it in, even if it wasn’t in the original plan. 2) Last-second product ideas Somebody on the product side gets a brainwave halfway through execution. It’s often exciting, but it hijacks the team’s focus and kills momentum. 3) Uncovered technical difficulties Reality bites. That “simple” feature suddenly needs a full redesign because the existing architecture can’t support it. 4) Planned dependencies or external tech collapse The API you counted on? Deprecated. The partner you relied on? Pulled out. Suddenly, your scope balloons just to keep things working. 5) A dramatic shift in the market Competitors launch something new or a regulation lands from nowhere, and your project needs to adapt fast. Scope change is fine as an exception. But when it becomes the rule, it’s no longer iteration — it’s feature bloat. How to avoid it? A) Plan the requests as iterations after the MVP release Don’t cram everything in upfront. Launch the core, validate, then add in the extras with intention. B) Put everything in the ROI context. Every new idea should be measured against the cost of delay and potential business return. If it doesn’t move the needle, it waits. C) At least don’t add anything mid-sprint Discipline matters. Mid-sprint additions break flow, demotivate teams, and turn velocity into chaos. D) Remember, you build products to hit goals, not for product excellence’s sake A “perfect” product nobody uses is just wasted time. Always tie scope back to business and user impact. E) Document and communicate scope changes visibly When every change is tracked, it forces accountability. Suddenly, “just one more thing” becomes a conscious trade-off, not a casual ask. Remember: adapting to change is being Agile. Pleasing everyone with no end in sight? That’s toxic, and it will end poorly. Have you ever seen a project’s scope rise beyond any expectations? Let me know in the comments :) #productmanagement #productmanager #agile  

When you’re in the weeds. You lose sight of the forest. As a PM or PMO leader, it’s easy to get lost in the weeds of tasks and meetings. Here are 5 ways to maintain your balance: 1. Set Clear, Measurable Goals → Align your daily tasks with strategic outcomes. → E.g. for PMs: Break down large strategic goals into clear, actionable project deliverables that tie back to company growth. → E.g. for PMO Leaders: Set quarterly KPIs that reflect both project performance and alignment with overall business objectives, ensuring every project contributes to the organization’s strategy. 2. Prioritize Based on Impact → Focus on the projects that move the needle. → E.g. for PMs: Use a scoring model to evaluate project value against resources and impact, ensuring priority is given to high-value tasks. → E.g. for PMO Leaders: Evaluate portfolio health regularly to ensure the most strategically important projects are prioritized across all teams and resources are allocated effectively. 3. Communicate the Vision Regularly → Help your team see the bigger picture. → E.g. for PMs: Take time during project kickoffs to connect each task to a larger business goal, helping the team understand the “why” behind their work. → E.g. for PMO Leaders: Hold quarterly strategy sessions to remind teams of the larger vision and how each department's efforts align with the overall business strategy. 4. Make Data-Driven Adjustments → Use metrics to guide both strategy and execution. → E.g. for PMs: Track project performance through regular checkpoints and adjust execution strategies when metrics show a shift in progress. → E.g. for PMO Leaders: Implement dashboards to continuously measure both project outcomes and alignment with strategic goals, adjusting resource allocation as necessary to keep on track. 5. Create Cross-Functional Collaboration → Break silos and encourage communication. → E.g. for PMs: Involve stakeholders from different departments early in the process to ensure project deliverables meet cross-departmental needs and expectations. → E.g. for PMO Leaders: Facilitate regular cross-functional reviews to ensure all teams are aligned with the long-term vision and that execution strategies are adaptable to shifting organizational priorities. Strategic vision without tactical execution is just a plan. Tactical execution without strategic vision is wasted effort. Strike the balance, and you’ll achieve real, impactful success. -- 👍 + ♻️ Like + Repost if this resonates with you. 🔔 Follow me (Hussain Bandukwala) for more content like this.