Effective Tech Project Management Techniques

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

It’s easy as a PM to only focus on the upside. But you'll notice: more experienced PMs actually spend more time on the downside. The reason is simple: the more time you’ve spent in Product Management, the more times you’ve been burned. The team releases “the” feature that was supposed to change everything for the product - and everything remains the same. When you reach this stage, product management becomes less about figuring out what new feature could deliver great value, and more about de-risking the choices you have made to deliver the needed impact. -- To do this systematically, I recommend considering Marty Cagan's classical 4 Risks. 𝟭. 𝗩𝗮𝗹𝘂𝗲 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗦𝗼𝘂𝗹 𝗼𝗳 𝘁𝗵𝗲 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 Remember Juicero? They built a $400 Wi-Fi-enabled juicer, only to discover that their value proposition wasn’t compelling. Customers could just as easily squeeze the juice packs with their hands. A hard lesson in value risk. Value Risk asks whether customers care enough to open their wallets or devote their time. It’s the soul of your product. If you can’t be match how much they value their money or time, you’re toast. 𝟮. 𝗨𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗨𝘀𝗲𝗿’𝘀 𝗟𝗲𝗻𝘀 Usability Risk isn't about if customers find value; it's about whether they can even get to that value. Can they navigate your product without wanting to throw their device out the window? Google Glass failed not because of value but usability. People didn’t want to wear something perceived as geeky, or that invaded privacy. Google Glass was a usability nightmare that never got its day in the sun. 𝟯. 𝗙𝗲𝗮𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗔𝗿𝘁 𝗼𝗳 𝘁𝗵𝗲 𝗣𝗼𝘀𝘀𝗶𝗯𝗹𝗲 Feasibility Risk takes a different angle. It's not about the market or the user; it's about you. Can you and your team actually build what you’ve dreamed up? Theranos promised the moon but couldn't deliver. It claimed its technology could run extensive tests with a single drop of blood. The reality? It was scientifically impossible with their tech. They ignored feasibility risk and paid the price. 𝟰. 𝗩𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗠𝘂𝗹𝘁𝗶-𝗗𝗶𝗺𝗲𝗻𝘀𝗶𝗼𝗻𝗮𝗹 𝗖𝗵𝗲𝘀𝘀 𝗚𝗮𝗺𝗲 (Business) Viability Risk is the "grandmaster" of risks. It asks: Does this product make sense within the broader context of your business? Take Kodak for example. They actually invented the digital camera but failed to adapt their business model to this disruptive technology. They held back due to fear it would cannibalize their film business. -- This systematic approach is the best way I have found to help de-risk big launches. How do you like to de-risk?

A PM at Google asked me how I managed 30+ stakeholders. 'More meetings?' Wrong. Here's the RACI framework that cut my meeting load by 60% while increasing influence. 1/ 𝙍𝙚𝙨𝙥𝙤𝙣𝙨𝙞𝙗𝙡𝙚 𝙫𝙨 𝘼𝙘𝙘𝙤𝙪𝙣𝙩𝙖𝙗𝙡𝙚 Most PMs drown because they invite everyone who's "interested." Instead, split your stakeholders into: - R: People doing the work - A: People accountable for success 2/ 𝙏𝙝𝙚 𝘾𝙤𝙣𝙨𝙪𝙡𝙩𝙖𝙩𝙞𝙤𝙣 𝙏𝙧𝙖𝙥 Stop asking for approval from everyone. Create two clear buckets: - C: Must consult before decisions - I: Just keep informed of progress 3/ 𝘿𝙤𝙘𝙪𝙢𝙚𝙣𝙩 > 𝙈𝙚𝙚𝙩𝙞𝙣𝙜 For "Informed" stakeholders, switch to documented updates. They'll actually retain more than in another recurring meeting. 4/ 𝙏𝙝𝙚 𝙈𝙖𝙜𝙞𝙘 𝙋𝙝𝙧𝙖𝙨𝙚 "𝗜𝗳 𝘆𝗼𝘂'𝗿𝗲 𝗻𝗼𝘁 𝗱𝗶𝗿𝗲𝗰𝘁𝗹𝘆 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗹𝗲, 𝗽𝗹𝗲𝗮𝘀𝗲 𝗳𝗼𝗿𝘄𝗮𝗿𝗱 𝘁𝗵𝗶𝘀 𝘁𝗼 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗽𝗲𝗿𝘀𝗼𝗻. 𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝗶𝗻 𝗮𝗱𝘃𝗮𝗻𝗰𝗲." Use this in every email. Watch the right people emerge. 5/ 𝘼𝙥𝙥𝙧𝙤𝙫𝙖𝙡 𝘼𝙧𝙘𝙝𝙞𝙩𝙚𝙘𝙩𝙪𝙧𝙚 Build your approval flows around your R&A stakeholders only. Everyone else gets strategic updates. --- This isn't about excluding people. It's about respecting everyone's time while maintaining momentum. If you found this framework helpful for managing stakeholders: 1. Follow Alex Rechevskiy for more actionable frameworks on product leadership and time management 2. Bookmark and retweet to save these tactics and help other PMs streamline their stakeholder management

Let’s face it - current headlines spell a recipe for employee stress. Raging inflation, recession worries, international strife, social justice issues, and overall uncertainty pile onto already full work plates. As business leaders, keeping teams motivated despite swirling fears matters more than ever. Here are 5 strategies I lean into to curb burnout and boost morale during turbulent times: 1. Overcommunicate Context and Vision: Proactively address concerns through radical transparency and big picture framing. Our SOP is to hold quarterly all hands and monthly meetings grouped by level cohort and ramp up fireside chats and written memos when there are big changes happening. 2. Enable Flexibility and Choice: Where Possible Empower work-life balance and self-care priorities based on individuals’ needs. This includes our remote work policy and implementing employee engagement tools like Lattice to track feedback loops. 3. Spotlight Impact Through Community Stories: Connect employees to end customers and purpose beyond daily tasks. We leveled up on this over the past 2 years. We provide paid volunteer days to our employees and our People Operations team actively connects our employees with opportunities in their region or remotely to get involved monthly. Recently we added highlighting the social impact by our employees into our internal communications plan. 4. Incentivize Cross-Collaboration: Reduce silos by rewarding team-wide contributions outside core roles. We’ve increased cross team retreats and trainings to spark fresh connections as our employee base grows. 5. Celebrate the Humanity: Profile your employee’s talents beyond work through content spotlight segments. We can’t control the market we operate in, but as leaders we can make an impact on how we foster better collaboration to tackle the headwinds. Keeping spirits and productivity intact requires acknowledging modern anxieties directly while sustaining focus on goals ahead. Reminding your teams why the work matters and that they are valued beyond output unlocks loyalty despite swirling worries. What tactics succeeded at boosting team morale and preventing burnout spikes within your company amidst current volatility?

When engaging with a vendor/product solution on project work, here are things I appreciate working in a high-demand, quick turn time area of a business: 1. Clear, timely, direct communication - whether it's a project plan, updates, collab materials, or coordination, emphasis on good communication is the key to the relationship. 2. Visibility and clear expectations around capacity and bandwidth - the intent is never to burnout our vendor partners, that's no good for anyone. On the client side, it's our responsibility to advocate for the business requirements and get the value we paid for out of the engagement. Sometimes, this means we may ask for a lot, and we don't have visibility to the capacity and bandwidth management of the resources doing the work. We do not manage the workload and resources for the vendor, we rely on them to take care of their people. If the ask exceeds capacity, please tell us. Please help us manage expectations and timelines on our side. You can tell me, "that's not possible," as long as you tell me why and when it will be. That gives us something to work with if reprioritization or securing more resources is necessary. 3. Accuracy and expertise - I assume that no one knows their area of expertise more than the vendor/solution. And I deeply appreciate when that level of knowledge is proactively brought to the table through the lens of our unique business application. 4. Accountability - when mistakes happen or things fall through the cracks, as they do, I will always ask for an after action review and hold partners accountable by requesting a plan for mitigation of future mistakes. Especially, because in my line of work, mistakes are often public and with a high level of business risk. Proactively providing this after action review is always a positive to building credibility and trust.

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!

I am constantly thinking about how to foster innovation in my product organization. Building teams that are experts at execution is the easy part—when there’s a clear problem, product orgs are great at coming up with smart solutions. But it’s impossible to optimize your way into innovation. You can’t only rely on incremental improvement to keep growing. You need to come up with new problem spaces, rather than just finding better solutions to the same old problems. So, how do we come up with those new spaces? Here are a few things I’m trying at Duolingo: 1. Innovation needs a high-energy environment, and a slow process will kill a great idea. So I always ask myself: Can we remove some of the organizational barriers here? Do managers from seven different teams really need to say yes on every project? Seeking consensus across the company—rather than just keeping everyone informed—can be a major deterrent to innovation. 2. Similarly, beware of defaulting to “following up.” If product meetings are on a weekly cadence, every time you do this, you are allocating seven days to a task that might only need two. We try to avoid this and promote a sense of urgency, which is essential for innovative ideas to turn into successes. 3. Figure out the right incentive. Most product orgs reward team members whose ideas have measurable business impact, which works in most contexts. But once you’ve found product-market fit, it is often easiest to generate impact through smaller wins. So, naturally, if your org tends to only reward impact, you have effectively incentivized constant optimization of existing features instead of innovation. In the short term things will look great, but over time your product becomes stale. I try to show my teams that we value and reward bigger ideas. If someone sticks their neck out on a new concept, we should highlight that—even if it didn’t pan out. Big swings should be celebrated, even if we didn’t win, because there are valuable learnings there. 4. Look for innovative thinkers with a history of zero-to-one feature work. There are lots of amazing product managers out there, but not many focus on new problem domains. If a PM has created something new from scratch and done it well, that’s a good sign. An even better sign: if they show excitement about and gravitate toward that kind of work. If that sounds like you—if you’re a product manager who wants to think big picture and try out big ideas in a fast-paced environment with a stellar mission—we want you on our team. We’re hiring a Director of Product Management: https://lnkd.in/dQnWqmDZ #productthoughts #innovation #productmanagement #zerotoone

Conflict gets a bad rap in the workplace. Early in my career, I believed conflict had no place in a healthy workplace. As I progressed, I realized that it was quite the contrary. The lack of conflict isn't a sign of a healthy work culture, rather it is an indication that important debates, discussions and differing viewpoints are being disregarded or suppressed. This insight revealed another key aspect: high-performing teams do not shy away from conflict. They embrace it, leveraging diverse opinions to drive optimal outcomes for customers. What sets these teams apart is their ability to handle conflict constructively. So how can this be achieved? I reached out to my friend Andrea Stone, Leadership Coach and Founder of Stone Leadership, for some tips on effectively managing conflict in the workplace. Here's the valuable guidance she provided: 1. Pause: Take a moment to assess your feelings in the heat of the moment. Be curious about your emotions, resist immediate reactions, and take the time to understand the why behind your feelings. 2. Seek the Other Perspective: Engage genuinely, listen intently, show real interest, and ask pertinent questions. Remember to leave your preconceived judgments at the door. 3. Acknowledge Their Perspective: Express your understanding of their viewpoint. If their arguments have altered your perspective, don't hesitate to share this with them. 4. Express Your Viewpoint: If your opinion remains unswayed, seek permission to explain your perspective and experiences. Remember to speak from your viewpoint using "I" statements. 5. Discuss the Bigger Objective: Identify common grounds and goals. Understand that each person might have a different, bigger picture in mind. This process can be taxing, so prepare beforehand. In prolonged conflict situations, don't hesitate to suggest breaks to refresh and refuel mentally, physically, and emotionally. 6. Know Your Limits: If the issue is of significant importance to you, be aware of your boundaries. For those familiar with negotiation tactics, know your BATNA (Best Alternative to a Negotiated Agreement). 7. Finalize Agreements: Once an agreement has been reached, continue the engagement to agree on responsibilities and timeframes. This ensures clarity on the outcome and commitments made. PS: Approach such situations with curiosity and assume others are trying to do the right thing. 🔁 Useful? I would appreciate a repost. Image Credit: Hari Haralambiev ----- Follow me, tap the (🔔) Omar Halabieh for daily Leadership and Career posts.

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 👇

Product managers & designers working with AI face a unique challenge: designing a delightful product experience that cannot fully be predicted. Traditionally, product development followed a linear path. A PM defines the problem, a designer draws the solution, and the software teams code the product. The outcome was largely predictable, and the user experience was consistent. However, with AI, the rules have changed. Non-deterministic ML models introduce uncertainty & chaotic behavior. The same question asked four times produces different outputs. Asking the same question in different ways - even just an extra space in the question - elicits different results. How does one design a product experience in the fog of AI? The answer lies in embracing the unpredictable nature of AI and adapting your design approach. Here are a few strategies to consider: 1. Fast feedback loops : Great machine learning products elicit user feedback passively. Just click on the first result of a Google search and come back to the second one. That’s a great signal for Google to know that the first result is not optimal - without tying a word. 2. Evaluation : before products launch, it’s critical to run the machine learning systems through a battery of tests to understand in the most likely use cases, how the LLM will respond. 3. Over-measurement : It’s unclear what will matter in product experiences today, so measuring as much as possible in the user experience, whether it’s session times, conversation topic analysis, sentiment scores, or other numbers. 4. Couple with deterministic systems : Some startups are using large language models to suggest ideas that are evaluated with deterministic or classic machine learning systems. This design pattern can quash some of the chaotic and non-deterministic nature of LLMs. 5. Smaller models : smaller models that are tuned or optimized for use cases will produce narrower output, controlling the experience. The goal is not to eliminate unpredictability altogether but to design a product that can adapt and learn alongside its users. Just as much as the technology has changed products, our design processes must evolve as well.