Task Prioritization Methods

I've tried 100s of time management techniques.  This is by far my favourite: I used to work 80 hrs/week and call it "productive." When really I was: - Attending pointless meetings - Fighting countless small fires - Being involved in every decision Now I work less than 70% the time and get 4x as much done. The Eisenhower Matrix helped me get there.  It teaches you to categorise tasks by importance and urgency. Here's how it works: 1. Do It Now (Urgent + Important) Examples: - Finalise pitch deck before investor meeting tomorrow. - Fix website crash during peak customer traffic. - Respond to press interview request before deadline. Best Practices: - Attack these tasks first each morning with full focus. - Set a strict deadline so urgency fuels execution. 2. Schedule It (Important + Not Urgent) Examples: - Plan quarterly strategy session with leadership team. - Map long-term hiring plan for next 18 months. - Build a personal brand content system for LinkedIn. Best Practices: - Protect time blocks in advance. Never leave them floating. - Tie them to measurable outcomes, not vague intentions. 3. Delegate It (Urgent + Not Important) Examples: - Handle inbound customer service queries this week. - Organise travel logistics for upcoming conference. - Update CRM with latest sales call notes. Best Practices: - Build playbooks so your team executes without confusion. - Delegate with deadlines to avoid wasting time. 4. Eliminate It (Not Urgent + Not Important) Examples: - Tweak logo colour palette again for fun. - Attend generic networking events with no ICP fit. - Review endless “best productivity tools” articles. Best Practices: - Audit weekly. Cut anything that doesn’t compound long-term. - Replace low-value busywork with rest, thinking, or selling. If you are always reacting to what feels urgent,   You'll never focus on what matters. Attend to the tasks in quadrant 1 efficiently,  Then spend 60-70% of your time in quadrant 2.    That's work that actually builds your business. Which quadrant are you spending too much time in right now?  Drop your thoughts in the comments. My newsletter, Step By Step, breaks down more frameworks like this. It's designed to help you build smarter without burning out. 200k+ builders use it to develop better systems. Join them here:  https://lnkd.in/eUTCQTWb ♻️ Repost this to help other founders manage their time.  And follow Chris Donnelly for more on building and running businesses. 

Evaluating LLMs is hard. Evaluating agents is even harder. This is one of the most common challenges I see when teams move from using LLMs in isolation to deploying agents that act over time, use tools, interact with APIs, and coordinate across roles. These systems make a series of decisions, not just a single prediction. As a result, success or failure depends on more than whether the final answer is correct. Despite this, many teams still rely on basic task success metrics or manual reviews. Some build internal evaluation dashboards, but most of these efforts are narrowly scoped and miss the bigger picture. Observability tools exist, but they are not enough on their own. Google’s ADK telemetry provides traces of tool use and reasoning chains. LangSmith gives structured logging for LangChain-based workflows. Frameworks like CrewAI, AutoGen, and OpenAgents expose role-specific actions and memory updates. These are helpful for debugging, but they do not tell you how well the agent performed across dimensions like coordination, learning, or adaptability. Two recent research directions offer much-needed structure. One proposes breaking down agent evaluation into behavioral components like plan quality, adaptability, and inter-agent coordination. Another argues for longitudinal tracking, focusing on how agents evolve over time, whether they drift or stabilize, and whether they generalize or forget. If you are evaluating agents today, here are the most important criteria to measure: • 𝗧𝗮𝘀𝗸 𝘀𝘂𝗰𝗰𝗲𝘀𝘀: Did the agent complete the task, and was the outcome verifiable? • 𝗣𝗹𝗮𝗻 𝗾𝘂𝗮𝗹𝗶𝘁𝘆: Was the initial strategy reasonable and efficient? • 𝗔𝗱𝗮𝗽𝘁𝗮𝘁𝗶𝗼𝗻: Did the agent handle tool failures, retry intelligently, or escalate when needed? • 𝗠𝗲𝗺𝗼𝗿𝘆 𝘂𝘀𝗮𝗴𝗲: Was memory referenced meaningfully, or ignored? • 𝗖𝗼𝗼𝗿𝗱𝗶𝗻𝗮𝘁𝗶𝗼𝗻 (𝗳𝗼𝗿 𝗺𝘂𝗹𝘁𝗶-𝗮𝗴𝗲𝗻𝘁 𝘀𝘆𝘀𝘁𝗲𝗺𝘀): Did agents delegate, share information, and avoid redundancy? • 𝗦𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗼𝘃𝗲𝗿 𝘁𝗶𝗺𝗲: Did behavior remain consistent across runs or drift unpredictably? For adaptive agents or those in production, this becomes even more critical. Evaluation systems should be time-aware, tracking changes in behavior, error rates, and success patterns over time. Static accuracy alone will not explain why an agent performs well one day and fails the next. Structured evaluation is not just about dashboards. It is the foundation for improving agent design. Without clear signals, you cannot diagnose whether failure came from the LLM, the plan, the tool, or the orchestration logic. If your agents are planning, adapting, or coordinating across steps or roles, now is the time to move past simple correctness checks and build a robust, multi-dimensional evaluation framework. It is the only way to scale intelligent behavior with confidence.

📌 How to do Prioritization as a Product Manager. Product Managers face a problem of plenty. You have so many things to do, many problems, many solutions, and many suggestions, but are always limited by time, bandwidth, and resources. Now you need to obsessively prioritize and filter ideas before you put them in the roadmap. But how do you prioritize? The simplest yet most powerful framework that most PMs rely on is the Impact v/s Effort Framework. The impact is determined by: - Potential revenue estimate, - Customer value, - Alignment with company goals, - Demand from the market, or - Any other relevant metrics that align with product goals. Impact estimation is mostly the responsibility of the product manager. The effort is determined by: - Development complexity, - Engineering efforts, - The time required & cost, - Operations complexity, etc. Effort estimation is mostly done by the delivery teams like engineers, design, ops, etc. This is a collaborative exercise. The next step is to visualize this through an impact v/s effort matrix. Provided that the estimations are done correctly, the low efforts & high impact items are picked at the earliest, & other things are prioritized in a logical order. 📌 3 Tips to take your prioritization game to the next level: 1. Consider tradeoffs at every step: Some high efforts ideas could be of high strategic importance, similarly some low-impact ideas could be critical for customer experience. Understand the situation from all angles. 2. Look out for red flags: All ideas look high impact, or the backlog is completely filled with low effort low impact ideas. This indicates either the PM is not competent at impact estimation or is not considering enough ideas during product discovery before deciding on the best one. 3. Validate high-effort ideas by first converting them into low efforts experiments. For example: Rather than converting your whole website into all Indian languages, try to convert the most popular pages into 3 popular languages, observe the results and then decide to roll back or go all in. 📌 Other frameworks for prioritization: There will be times when you'll need more detailed frameworks to prioritize, some of the other helpful frameworks are: 1. KANO: Puts customer satisfaction at the center and distinguishes between basic expectations, performance attributes, and delighters. 2. MOSCOW: categorizes requirements into four priority levels: Must have, Should have, Could have, and Won't have. 3. RICE: adds to more dimensions of Reach and Confidence to make Impact v/s Effort more reliable and exhaustive. ✨ Prioritization is a supercritical and useful skill for product managers, during their work, stakeholder management, and also during interviews. Do you think this would be helpful for you? I share helpful insights for product managers almost every day, consider connecting here 👉🏽 Ankit Shukla to not miss out. #productmanagement #prioritization

One lesson I learned while building the legal function at DoorDash during our most explosive growth period was that business teams would mark everything as urgent without understanding the ripple effects. Sales said their deal was mission-critical. Marketing needed their campaign reviewed yesterday. HR had a contract that absolutely cannot wait. Every request felt like it was on fire, but they couldn't all actually be emergencies. Business teams couldn't see that approving their "P0" request meant three other departments would have to wait. In fact, the most stressful moments I've experienced in legal were when I was juggling multiple genuine emergencies at once. That's when I realized we needed a system that forces difficult conversations to happen outside of legal. A good prioritization framework does something powerful. It makes the business leader requesting P1 priority go to their peers and explain why their request should jump the line. They need to make the case to other department heads about why their urgent matter trumps everyone else's urgent matters. This creates accountability and transparency that didn't exist before. Business teams start to think twice about what they're actually asking for when they mark something as high priority. In-house legal teams in particular need a prioritization framework that's not just internal. It needs to be socialized across the entire organization. We've made the below framework publicly available on our website. It was originally created by Ilan Hornstein, Global VP at 8x8, who generously shared it so other legal teams could benefit. It creates a common language around urgency that everyone in your organization can understand. I especially dig the airplane analogies! Funny aside - when my Head of Sales described something that in his mind was an urgent situation at the end of a quarter (equal to what he thought was a P1), Ilan laughed and said “that’s a very typical P3 scenario for us, and something that we’d turn around in a couple of days tops” Start socializing a framework like this with your business partners. You'll be amazed how much clearer these conversations become when everyone's working from the same playbook.

Leader Standard Work- it's just a fancy schedule right? What's the big deal? 🤷♀️ Leader Standard Work (LSW) might look like a schedule on the surface, but it’s so much more than that. It’s a strategic framework designed to help leaders focus on what really matters: proactive tasks that support their team, improve processes, and drive long-term success. The “big deal” is that LSW bridges the gap between leadership intentions and daily actions. It’s not just about organizing your time—it’s about aligning your efforts with organizational goals, creating consistency in your leadership, and ensuring that you’re spending your time where it delivers the most value. In other words, it’s not just about having a plan; it’s about having the right plan. It's a great tool, but like many tools, its success depends on how it’s implemented. There's a right way and a wrong way. Here's my approach: 1️⃣ Understand Current Work: Assess your routine tasks (use your calendar to help you) and categorize them into Essential, Enhance and Eliminate (That's my 3 E's framework) 2️⃣ Identify Key Activities for Your Role: Ask yourself what am I not doing that I should be doing? How often should I do these? (Here you could look at introducing time for strategic planning, Gemba Walks. 1:1 check ins with people...and all the other really important tasks that often get pushed to the side!! Feedback really helps here! 3️⃣ Create an IDEAL standard schedule. This is your vision of the way you would like to work daily, weekly and monthly- if there were no distractions! 4️⃣ Create a REALISTIC Standard Schedule: Develop a practical daily, weekly, and monthly plan that incorporates some improvements to the way you currently work, while balancing your current workload. It's probably not going to look like your ideal version so the next step is really important. 5️⃣ Create your Development Plan: Identify actions to gradually reduce distractions and time spent on activities you feel you shouldn't be doing, freeing up more time for high-impact work. This often means actively working on skills like prioritization and delegation. 6️⃣ Track, Assess and Reflect: Do this regularly to adjust as needed, and focus on consistently improving how you spend your time. Get feedback from trusted people to understand your impact. The question isn’t whether LSW works; it’s whether you’re willing to work at it! Sometimes, this is the sole focus of my leadership coaching sessions for weeks and months. It's not something we can rush. It needs to be done right! 💡Imagine everyone on your team having a #LeaderStandardWork schedule by Q1 2025 and actively working on improving it. Well, it's possible! PS I don't just teach the theory- I actively create LSW schedules with people. I work on-site with companies in Ireland and the UK to make this happen. Contact if you would like to meet up and talk it through!

Want to tackle the most impactful data projects? Use the RICE scoring model to sort them by priority! RICE stands for Reach, Impact, Confidence, and Effort. It’s a useful framework to prioritize tasks and projects effectively. 1. 𝗥𝗲𝗮𝗰𝗵: Estimate how many people your project will affect. For example, how many teams will make decisions based on my results?     2. 𝗜𝗺𝗽𝗮𝗰𝘁: Estimate the potential benefit. Will this project bring significant improvements or minor enhancements? Rate it on a scale e.g., 1 to 5.     3. 𝗖𝗼𝗻𝗳𝗶𝗱𝗲𝗻𝗰𝗲: Assess how confident you are in your estimates. High confidence boosts the project’s score, while low confidence lowers it. Be honest about your uncertainties regarding data quality and model complexity (0.0 to 1.0).     4. 𝗘𝗳𝗳𝗼𝗿𝘁: Calculate the time and resources required to complete the project. Measure it in person-hours or team-days. Less effort means a higher score. C͟a͟l͟c͟u͟l͟a͟t͟i͟o͟n͟ 𝗥𝗜𝗖𝗘 𝗦𝗰𝗼𝗿𝗲 = (Reach × Impact × Confidence) / Effort E͟x͟a͟m͟p͟l͟e͟ You will reach 50 sales managers with your model and estimate an impact of 4 out 5 on their work. You're fairly certain about achieving your goal with a rate of 0.8. It will take you about 80 hours of work to build the model. 𝗥𝗜𝗖𝗘 𝗦𝗰𝗼𝗿𝗲 = (50 × 4 × 0.8) / 80 𝗥𝗜𝗖𝗘 𝗦𝗰𝗼𝗿𝗲 =  2 You can compare this score of 2 versus the other project scores and select the one with the highest value. Use the RICE model to sort and prioritize your data projects. It ensures you’re focusing on high-impact tasks that require reasonable effort and have solid confidence behind them. Regularly revisit and adjust your scores as new data or insights become available. This keeps your priorities aligned with changing business goals. By applying the RICE scoring model, you’ll increase the efficiency of your project management, ensuring you’re working on what truly matters. How do you currently prioritize your data projects? ---------------- ♻️ Share if you find this post useful ➕ Follow for more daily insights on how to grow your career in the data field #dataanalytics #datascience #rice #projectmanagement #prioritization

Time is the one thing you can’t buy. But how you manage it makes all the difference. Managing time effectively isn’t about doing more—it’s about focusing on what matters. Over my career, Stephen Covey’s Four-Quadrant Time Management Model has proven invaluable in helping me structure my priorities: 👉 Urgent & Important: These are crises and pressing problems—tasks that must be tackled immediately. 👉 Important but Not Urgent: Strategic thinking, relationship building, and planning belong here. They don’t demand attention now but drive long-term success. 👉 Not Important but Urgent: Delegate these—routine emails, some meetings, and minor distractions. 👉 Not Important & Not Urgent: Remove the trivia and time-wasters altogether. Beyond the quadrants, structuring your time is key. For me, this means: ✅ Daily 20-minute team meetings: These short check-ins help prioritise tasks and avoid wasted time. ✅ A streamlined email system: Using three folders—“Action,” “For Information,” and “Day File”—keeps my focus where it’s needed. ✅ Efficient meetings: Clear agendas, materials sent in advance, and decisions at the centre. It’s not just about managing my own time—it’s also about enabling those around me to do the same. Two-thirds of a leader’s time is spent with direct reports, so helping them be productive has a multiplier effect. Ultimately, the goal isn’t to pack more into each day—it’s to free up time for the things that matter most, like family, friends, and personal well-being. Time is precious. Managing it well can make all the difference.

𝐉𝐮𝐠𝐠𝐥𝐢𝐧𝐠 𝟒 𝐏𝐫𝐨𝐣𝐞𝐜𝐭𝐬 𝐚𝐭 𝐎𝐧𝐜𝐞? 𝐇𝐞𝐫𝐞’𝐬 𝐖𝐡𝐚𝐭 𝐈 𝐋𝐞𝐚𝐫𝐧𝐞𝐝.🎭 One month, I found myself handling 4 projects at the same time. Different deadlines. Different team members. Different expectations. At first, I thought: “I got this!” By Week 2, I was overwhelmed. 💬 Teams notifications piling up 📧 Emails left unread 📝 Deadlines creeping closer It was chaos. But here’s what I learned that helped me not just survive—but actually deliver all four projects successfully. 🔹 𝟭. 𝗡𝗼𝘁 𝗘𝘃𝗲𝗿𝘆 𝗧𝗮𝘀𝗸 𝗗𝗲𝘀𝗲𝗿𝘃𝗲𝘀 𝘁𝗵𝗲 𝗦𝗮𝗺𝗲 𝗘𝗻𝗲𝗿𝗴𝘆 I used to treat all tasks equally—huge mistake. Instead, I started prioritizing like a CEO: Impact vs. Urgency → What moves the needle the most? Tasks I can delegate vs. Tasks I MUST own 🔹 𝟮. 𝗦𝘁𝗼𝗽 𝗢𝘃𝗲𝗿𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗻𝗴. 𝗦𝘁𝗮𝗿𝘁 𝗦𝗺𝗮𝗿𝘁 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗻𝗴 Handling different teams meant tons of calls, updates, and meetings. Solution? I grouped discussions into structured updates instead of responding to every little thing. Weekly syncs → Big picture Asynchronous updates → For non-urgent matters 🔹 𝟯. 𝗧𝗶𝗺𝗲-𝗕𝗹𝗼𝗰𝗸𝗶𝗻𝗴 𝗖𝗵𝗮𝗻𝗴𝗲𝗱 𝘁𝗵𝗲 𝗚𝗮𝗺𝗲 I used to jump between projects all day. It was exhausting. Then, I started: ⏳ Morning = Deep work on Project A ⏳ Afternoon = Meetings + Project B ⏳ Evening = Reviewing & planning for tomorrow This stopped my brain from context-switching every 10 minutes. 🔹 𝟰. 𝗬𝗼𝘂𝗿 𝗖𝗮𝗹𝗲𝗻𝗱𝗮𝗿 𝗦𝗵𝗼𝘂𝗹𝗱 𝗦𝗰𝗮𝗿𝗲 𝗬𝗼𝘂 𝗮 𝗟𝗶𝘁𝘁𝗹𝗲 (𝗕𝘂𝘁 𝗡𝗼𝘁 𝗧𝗼𝗼 𝗠𝘂𝗰𝗵) I learned the power of scheduling everything. Even my ‘thinking time.’ Because if you don’t control your calendar, your calendar will control you. 📌 Lesson? Multitasking isn’t the flex. Managing your time is. You can’t give 100% to everything—but you can be 100% present in what you’re doing right now. Ever been in a situation like this? How do YOU manage multiple projects without losing your mind? Drop your best tips below! 👇 #TimeManagement #Productivity #CareerGrowth

Every task that comes to me is urgent and important. Sound familiar? This is a challenge many of us face daily. Early in my career, prioritization was relatively straightforward—my manager told me what to focus on. But as I grew, the game changed. Suddenly, I was managing a flood of requests, far more than I could handle, and the signals from others weren’t helpful. Everything was “important.” Everything was “urgent.” Often, it was both. To handle this effectively, I realized I needed to develop an internal prioritization compass. It wasn’t easy, but it was transformative. Here are 6 strategies to help you build your own: 1/ Be crystal clear on key goals Start by understanding your organization’s goals—at the company, department, and team levels. Attend organizational forums, departmental reviews, or leadership updates to stay informed. When in doubt, use your 1:1s with leaders to ask: What does success look like? 2/ Deeply understand KPIs Metrics guide decision-making, but not all metrics are equally valuable. Take the time to understand your team's or function's key performance indicators (KPIs). Know what they measure, what they mean, and how to assess their impact. 3/ Be assertive to protect priorities Not every task deserves your attention. Practice saying “no” or deferring requests that don’t align with key goals or metrics. Assertiveness is not about being inflexible—it’s about protecting your capacity to focus on what truly matters. 4/ Set and reset expectations Priorities change, and that’s okay. What’s not okay is working on misaligned tasks. Keep open communication with your manager and stakeholders about evolving priorities. When new demands arise, clarify and reset expectations. 5/ Use 1:1s to align with your manager Leverage your 1:1s as a strategic tool. Share your current priorities, validate them against your manager’s expectations, and discuss any conflicts or challenges. 6/ Clarify the escalation process When priorities conflict, don’t let disagreements linger. If you can’t agree quickly, escalate the issue to your manager. This avoids unnecessary churn, ensures trust remains intact, and keeps momentum focused on results. PS: You won’t always get it right—and that’s okay. Treat each misstep as an opportunity to refine your compass. What’s one tip you’ve used to prioritize when everything feels urgent? --- Follow me, tap the (🔔) Omar Halabieh for daily Leadership and Career posts.

Unlocking Focus: A Simple Framework To Prioritise The Initiatives That Matter I facilitated a workshop with the leadership team of one of my technology clients yesterday, where we focused on a critical challenge: how do we prioritise outcomes over hours to maximise effectiveness? The solution? A simple but powerful tool I've relied on for years, which I learned during my time at General Electric (GE) - the Ease/Impact Matrix. Here's why it works so brilliantly: We often gravitate toward quick wins without considering their actual value. This matrix forces the team to evaluate everything through two critical lenses: ✅ High Impact + High Ease = Quick Wins (do immediately, gain momentum) ✅ High Impact + Low Ease = Long-term Bets (worth the investment) ❌ Low Impact + Low Ease = Avoid at All Costs ❓ Low Impact + High Ease = Question Why (just because we can, should we?) By reorienting around impact, we focused on what will truly benefit their business both immediately and in the long run. Sometimes the simplest tools create the most profound shifts. What frameworks have you found most valuable for prioritisation? #OutcomesOverHours