Project Management

Want to stay motivated every single day? Borrow a strategy from Harvard. Then borrow another from stand up comedy. Together, they’re a powerhouse for momentum, motivation, and mastery. Here’s how it works: Let’s start with Harvard. Researcher Teresa Amabile studied 12,000 daily work diaries across 8 companies. She wanted to know: What truly motivates people on a day to day basis? What she found changed how we understand drive. The #1 driver of daily motivation wasn’t: Money Praise Perks It was progress. The days people made progress on meaningful work were the days they felt the best. Progress isn’t a luxury. It’s a psychological necessity. So how do we make progress feel visible especially on days when it’s not? Use a “Progress Ritual.” → At the end of the day, pause. → Write down 3 small ways you moved forward. → That’s it. No fanfare. Just ritual. This works because we rarely notice our progress in real time. It gets buried under busyness, meetings, and mental noise. The act of looking back gives your brain the reward it needs to keep going. Momentum builds from meaning. Now let’s add some comedy. Young Jerry Seinfeld had one goal: write new material every day. To stay on track, he created a brilliant system. Each day he wrote, he put a big red X on his calendar. Soon, a chain of Xs formed. And here’s the key: Don’t break the chain. One red X becomes two. Two becomes ten. Ten becomes identity. Whether you’re writing, coding, or training Daily action + visual chain = long-term motivation. Summary: The Two-Part Motivation System From Harvard: Record 3 ways you made progress each day. From Seinfeld: Mark an X for each day you show up then don’t break the chain. Progress fuels purpose. Consistency fuels confidence. Apply both and you’ll stay on track especially on the tough days. Because when your days get better, your weeks get better. When your weeks get better, your months get better. When your months get better, your life gets better. It starts with one small win today.

Explaining the Evaluation method LLM-as-a-Judge (LLMaaJ). Token-based metrics like BLEU or ROUGE are still useful for structured tasks like translation or summarization. But for open-ended answers, RAG copilots, or complex enterprise prompts, they often miss the bigger picture. That’s where LLMaaJ changes the game. 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗶𝘁? You use a powerful LLM as an evaluator, not a generator. It’s given: - The original question - The generated answer - And the retrieved context or gold answer 𝗧𝗵𝗲𝗻 𝗶𝘁 𝗮𝘀𝘀𝗲𝘀𝘀𝗲𝘀: ✅ Faithfulness to the source ✅ Factual accuracy ✅ Semantic alignment—even if phrased differently 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗺𝗮𝘁𝘁𝗲𝗿𝘀: LLMaaJ captures what traditional metrics can’t. It understands paraphrasing. It flags hallucinations. It mirrors human judgment, which is critical when deploying GenAI systems in the enterprise. 𝗖𝗼𝗺𝗺𝗼𝗻 𝗟𝗟𝗠𝗮𝗮𝗝-𝗯𝗮𝘀𝗲𝗱 𝗺𝗲𝘁𝗿𝗶𝗰𝘀: - Answer correctness - Answer faithfulness - Coherence, tone, and even reasoning quality 📌 If you’re building enterprise-grade copilots or RAG workflows, LLMaaJ is how you scale QA beyond manual reviews. To put LLMaaJ into practice, check out EvalAssist; a new tool from IBM Research. It offers a web-based UI to streamline LLM evaluations: - Refine your criteria iteratively using Unitxt - Generate structured evaluations - Export as Jupyter notebooks to scale effortlessly A powerful way to bring LLM-as-a-Judge into your QA stack. - Get Started guide: https://lnkd.in/g4QP3-Ue - Demo Site: https://lnkd.in/gUSrV65s - Github Repo: https://lnkd.in/gPVEQRtv - Whitepapers: https://lnkd.in/gnHi6SeW

Should you try Google’s famous “20% time” experiment to encourage innovation? We tried this at Duolingo years ago. It didn’t work. It wasn’t enough time for people to start meaningful projects, and very few people took advantage of it because the framework was pretty vague. I knew there had to be other ways to drive innovation at the company. So, here are 3 other initiatives we’ve tried, what we’ve learned from each, and what we're going to try next. 💡 Innovation Awards: Annual recognition for those who move the needle with boundary-pushing projects. The upside: These awards make our commitment to innovation clear, and offer a well-deserved incentive to those who have done remarkable work. The downside: It’s given to individuals, but we want to incentivize team work. What’s more, it’s not necessarily a framework for coming up with the next big thing. 💻 Hackathon: This is a good framework, and lots of companies do it. Everyone (not just engineers) can take two days to collaborate on and present anything that excites them, as long as it advances our mission or addresses a key business need. The upside: Some of our biggest features grew out of hackathon projects, from the Duolingo English Test (born at our first hackathon in 2013) to our avatar builder. The downside: Other than the time/resource constraint, projects rarely align with our current priorities. The ones that take off hit the elusive combo of right time + a problem that no other team could tackle. 💥 Special Projects: Knowing that ideal equation, we started a new program for fostering innovation, playfully dubbed DARPA (Duolingo Advanced Research Project Agency). The idea: anyone can pitch an idea at any time. If they get consensus on it and if it’s not in the purview of another team, a cross-functional group is formed to bring the project to fruition. The most creative work tends to happen when a problem is not in the clear purview of a particular team; this program creates a path for bringing these kinds of interdisciplinary ideas to life. Our Duo and Lily mascot suits (featured often on our social accounts) came from this, as did our Duo plushie and the merch store. (And if this photo doesn't show why we needed to innovate for new suits, I don't know what will!) The biggest challenge: figuring out how to transition ownership of a successful project after the strike team’s work is done. 👀 What’s next? We’re working on a program that proactively identifies big picture, unassigned problems that we haven’t figured out yet and then incentivizes people to create proposals for solving them. How that will work is still to be determined, but we know there is a lot of fertile ground for it to take root. How does your company create an environment of creativity that encourages true innovation? I'm interested to hear what's worked for you, so please feel free to share in the comments! #duolingo #innovation #hackathon #creativity #bigideas

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

🚨 AI Privacy Risks & Mitigations Large Language Models (LLMs), by Isabel Barberá, is the 107-page report about AI & Privacy you were waiting for! [Bookmark & share below]. Topics covered: - Background "This section introduces Large Language Models, how they work, and their common applications. It also discusses performance evaluation measures, helping readers understand the foundational aspects of LLM systems." - Data Flow and Associated Privacy Risks in LLM Systems "Here, we explore how privacy risks emerge across different LLM service models, emphasizing the importance of understanding data flows throughout the AI lifecycle. This section also identifies risks and mitigations and examines roles and responsibilities under the AI Act and the GDPR." - Data Protection and Privacy Risk Assessment: Risk Identification "This section outlines criteria for identifying risks and provides examples of privacy risks specific to LLM systems. Developers and users can use this section as a starting point for identifying risks in their own systems." - Data Protection and Privacy Risk Assessment: Risk Estimation & Evaluation "Guidance on how to analyse, classify and assess privacy risks is provided here, with criteria for evaluating both the probability and severity of risks. This section explains how to derive a final risk evaluation to prioritize mitigation efforts effectively." - Data Protection and Privacy Risk Control "This section details risk treatment strategies, offering practical mitigation measures for common privacy risks in LLM systems. It also discusses residual risk acceptance and the iterative nature of risk management in AI systems." - Residual Risk Evaluation "Evaluating residual risks after mitigation is essential to ensure risks fall within acceptable thresholds and do not require further action. This section outlines how residual risks are evaluated to determine whether additional mitigation is needed or if the model or LLM system is ready for deployment." - Review & Monitor "This section covers the importance of reviewing risk management activities and maintaining a risk register. It also highlights the importance of continuous monitoring to detect emerging risks, assess real-world impact, and refine mitigation strategies." - Examples of LLM Systems’ Risk Assessments "Three detailed use cases are provided to demonstrate the application of the risk management framework in real-world scenarios. These examples illustrate how risks can be identified, assessed, and mitigated across various contexts." - Reference to Tools, Methodologies, Benchmarks, and Guidance "The final section compiles tools, evaluation metrics, benchmarks, methodologies, and standards to support developers and users in managing risks and evaluating the performance of LLM systems." 👉 Download it below. 👉 NEVER MISS my AI governance updates: join my newsletter's 58,500+ subscribers (below). #AI #AIGovernance #Privacy #DataProtection #AIRegulation #EDPB

If You Can’t Explain Budgeting Like This, You’re Not Ready for FP&A Interviews. Let’s assume I ask you the budget for fuel (petrol/diesel) expenses that you are going to incur next year in 2026. How would you budget using the below techniques: 1. Incremental / Traditional Budgeting You take into account the expenses on fuel you made this year. Assuming that amount is INR 50,000. Considering inflation, fuel price changes, and usage patterns, you estimate a 20% increase. Accordingly, your fuel budget for next year will be INR 60,000 (50,000 + 20%) 2. Zero-Based Budgeting Instead of taking current year’s expenses, you start from scratch. You estimate how much your car will travel next year. Then factor in expected fuel price and mileage of your vehicle. Based on this, you calculate a reasonable estimate of fuel expenses for next year 3. Activity-Based Budgeting Let’s say you use the car only to commute to and from office. For each round trip, your car consumes fuel worth INR 500. Your budgeting would be based on this activity (number of trips taken in a year). If you go to office twice a week, total trips = 52 × 2 = 104. Hence, your fuel budget = 500 × 104 = INR 52,000. 4. Flexible Budgeting Your fuel cost depends on how frequently you travel. Instead of one fixed budget, you prepare multiple scenarios. Example: 2 days/week → INR 52,000 4 days/week → INR 104,000 Your actual budget will depend on actual usage during the year. 5. Rolling (Continuous) Budgeting You don’t fix the budget once for the entire year. You keep revising it periodically (monthly/quarterly). Example: if fuel prices increase mid-year or your travel increases, you update the remaining budget accordingly. 6. Top-Down vs Bottom-Up Budgeting Top-Down: You decide a cap (say INR 55,000) and adjust your usage to stay within it Bottom-Up: You calculate expected usage (like ABB/ZBB) and arrive at the number logically 7. Value Proposition Budgeting (using the same example) Instead of focusing only on cost, you evaluate whether the expense creates value. You analyse each type of travel: Office commute - necessary Leisure / unnecessary trips - optional You may reduce or eliminate low-value trips, carpool, or use alternative transport. Hence, your budget is driven by value derived rather than just estimated usage. This way, the same fuel expense can give you very different budgets depending on the approach you use.

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

My S.C.O.P.E. Framework Your essential project management approach. 🌟 S - Specify Requirements • Define project requirements. • Document expectations. • Set a solid foundation. • Understand stakeholder needs. • Establish clear goals. C - Clarify Objectives • Set measurable objectives. • Align with project goals. • Use SMART criteria. • Ensure clarity and relevance. • Achieve project alignment. O - Outline Boundaries • Define project scope. • Specify inclusions and exclusions. • Manage expectations. • Prevent scope creep. • Establish clear limits. P - Plan for Changes • Prepare for changes. • Set up change processes. • Assess change requests. • Approve and implement changes. • Adapt to evolving needs. E - Evaluate Progress • Regularly review progress. • Measure against scope. • Ensure project stays on track. • Address deviations promptly. • Maintain project integrity. Download and save this framework. Use it to enhance your project planning and execution. 🌟 Thank you for reading!

Compliance isn’t choosing one framework, it’s understanding how they work together. Many organizations view SOC 2, ISO 27001, and GDPR as competing obligations, but the reality is far more integrated. SOC 2 validates data security controls for US-based service providers voluntary but expected by enterprise clients. ISO 27001 provides a globally recognized ISMS foundation with comprehensive risk management and continuous improvement. GDPR legally enforces personal data protection for EU citizens with significant financial penalties for non-compliance. The strategic advantage lies in their overlap: access controls, incident response, vendor risk management, encryption, and breach notification requirements align across all three. Organizations that map controls once and satisfy multiple frameworks simultaneously reduce audit fatigue while strengthening their overall security posture. Rather than treating compliance as separate silos, mature GRC programs build unified control environments that address shared requirements, turning regulatory burden into operational excellence. What’s your approach to managing overlapping compliance frameworks? #GRC #SOC2 #ISO27001 #GDPR #Compliance #InformationSecurity #DataProtection

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.