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

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

Teams will increasingly include both humans and AI agents. We need to learn how best to configure them. A new Stanford University paper "ChatCollab: Exploring Collaboration Between Humans and AI Agents in Software Teams" reveals a range of useful insights. A few highlights: 💡 Human-AI Role Differentiation Fosters Collaboration. Assigning distinct roles to AI agents and humans in teams, such as CEO, Product Manager, and Developer, mirrors traditional team dynamics. This structure helps define responsibilities, ensures alignment with workflows, and allows humans to seamlessly integrate by adopting any role. This fosters a peer-like collaboration environment where humans can both guide and learn from AI agents. 🎯 Prompts Shape Team Interaction Styles. The configuration of AI agent prompts significantly influences collaboration dynamics. For example, emphasizing "asking for opinions" in prompts increased such interactions by 600%. This demonstrates that thoughtfully designed role-specific and behavioral prompts can fine-tune team dynamics, enabling targeted improvements in communication and decision-making efficiency. 🔄 Iterative Feedback Mechanisms Improve Team Performance. Human team members in roles such as clients or supervisors can provide real-time feedback to AI agents. This iterative process ensures agents refine their output, ask pertinent questions, and follow expected workflows. Such interaction not only improves project outcomes but also builds trust and adaptability in mixed teams. 🌟 Autonomy Balances Initiative and Dependence. ChatCollab’s AI agents exhibit autonomy by independently deciding when to act or wait based on their roles. For example, developers wait for PRDs before coding, avoiding redundant work. Ensuring that agents understand role-specific dependencies and workflows optimizes productivity while maintaining alignment with human expectations. 📊 Tailored Role Assignments Enhance Human Learning. Humans in teams can act as coaches, mentors, or peers to AI agents. This dynamic enables human participants to refine leadership and communication skills, while AI agents serve as practice partners or mentees. Configuring teams to simulate these dynamics provides dual benefits: skill development for humans and improved agent outputs through feedback. 🔍 Measurable Dynamics Enable Continuous Improvement. Collaboration analysis using frameworks like Bales’ Interaction Process reveals actionable patterns in human-AI interactions. For example, tracking increases in opinion-sharing and other key metrics allows iterative configuration and optimization of combined teams. 💬 Transparent Communication Channels Empower Humans. Using shared platforms like Slack for all human and AI interactions ensures transparency and inclusivity. Humans can easily observe agent reasoning and intervene when necessary, while agents remain responsive to human queries. Link to paper in comments.

🌱 Set Up UX Office Hours To Scale Up Your UX Impact (https://lnkd.in/eevRpdng), a neat idea to scale up UX impact when PM and Engineering teams outnumber designers — to help product teams that might not have direct access to design expertise and spread the value of UX across the entire organization. Neatly put together by Raquel Piqueras Herrero from Microsoft. 🤔 Designers are often outnumbered by PMs and engineers. 🚫 Non-designers across teams have little to no exposure to UX. 🚫 The outcome: poor, fragile end-to-end UX of siloed products. ✅ With UX office hours, we make UX available to other teams. ✅ It’s consultations for products without dedicated UX support. ✅ Set up 1h weekly meetings: recurrent, time-protected slots. ✅ Allow teams to book 20 mins to get feedback and UX support. ✅ Schedule meetings mid-week to allow for issues to emerge. ✅ Send a “how-it-works” email with sample topics/questions. ↳ E.g. accessibility, checkbox vs. radio, design system, mobile. 🚫 Some requests are full-feature work → you’ll need to pre-approve. ✅ Ask for product name, feature, PM, desired feedback, docs, links. ✅ In Jira, delegate small consults to UX office hours with tags/flags. ✅ Keep an archive of requests and solutions in a single Figma file. ✅ Keep tabs on similar patterns or issues emerging across teams. As designers, we are often reluctant to invite engineers or PMs to design meetings because they don’t really “get” UX. But nobody wants to create a poor UX intentionally. It happens because UX never gets a chance to be a part of a conversation. And too often there is no established line of communication to early flag critical design mistakes before they reach production. But just like designers need technical feedback to avoid late implementation challenges, engineers need UX feedback to avoid complaints and regressions. They want to optimize user efficiency and customer satisfaction, just like they want to optimize code quality and team workflow. Instead of building walls, invite teams to build bridges. But what if you set up UX hours — and absolutely nothing happens? I would try to move the needle by sprinkling a bit of UX within the QA process. For consistency, efficiency and compliance. Embed accessibility and usability as a part of the testing suite to reduce maintenance work and drive efficiency. As Raquel Piqueras Herrero noted, “typically there is a clear need for clarity and a strong appetite for quality work.” I can only wholeheartedly agree with it. I’m yet to try out UX Office Hours, but you shouldn’t be surprised if, once set up, your UX office hours will be fully booked before you even blink. Useful resources: The Power Of Office Hours, by Alex Jones https://lnkd.in/eQCSdikV [continues in comments ↓]

Over the years, I've discovered the truth: Game-changing products won't succeed unless they have a unified vision across sales, marketing, and product teams. When these key functions pull in different directions, it's a death knell for go-to-market execution. Without alignment on positioning and buyer messaging, we fail to communicate value and create disjointed experiences. So, how do I foster collaboration across these functions? 1) Set shared goals and incentivize unity towards that North Star metric, be it revenue, activations, or retention. 2) Encourage team members to work closely together, building empathy rather than skepticism of other groups' intentions and contributions. 3) Regularly conduct cross-functional roadmapping sessions to cascade priorities across departments and highlight dependencies. 4) Create an environment where teams can constructively debate assumptions and strategies without politics or blame. 5) Provide clarity for sales on target personas and value propositions to equip them for deal conversations. 6) Involve all functions early in establishing positioning and messaging frameworks. Co-create when possible. By rallying together around customers’ needs, we block and tackle as one team towards product-market fit. The magic truly happens when teams unite towards a shared mission to delight users!

As a CTO who has successfully scaled AI and tech products, I’ve refined productivity strategies that can transform your leadership workflow and enhance your team’s output. If you’re leading in the tech industry, and grappling with overwhelming demands, the 3 targeted tactics I’m about to share are tailored for the unique challenges you face. My guiding principle each week is the 'Rule of Three': identifying three top priorities that serve as my North Star. These aren't just scribbled in a planner but physically placed on my office wall, a constant visual reminder of my core focus. This practice not only keeps me centered amidst the whirlwind of daily tasks but also ensures that every action is a step toward our most critical goals. Sharing these priorities with my direct reports does more than foster transparency — it aligns our efforts, synchronizes our strides, and forms the bedrock of our collective pursuit. It's a simple yet profoundly effective strategy that has continually steered us toward meaningful progress and impactful results. Next, time blocking has been a critical strategy. Carving out dedicated blocks for deep work, meetings, and even unexpected tasks allows me to create a rhythm amidst the chaos. This isn't just about sticking to a schedule; it's about allocating mental space and ensuring that high-priority projects get the uninterrupted attention they deserve. I always check each Friday that my time blocked schedule appropriately reflects the work I need to accomplish for my top three priorities. Lastly, I leverage automation and delegation. By automating routine tasks and delegating effectively, I maintain focus on what truly requires my expertise. It's not just about offloading work; it's about empowering my team by entrusting them with responsibilities that aid their growth while freeing me to lead more effectively. A framework I really like using is the Eisenhower matrix around categorizing work based on its urgency and importance. I try and focus as much of my work as I can on the important and urgent tasks. Implementing these strategies hasn’t just boosted my personal productivity; it sets a precedent for the whole team. When leaders manage their time effectively, it cascades down, fostering a culture of efficiency and clarity. Remember, in the world of tech and AI, where the ground shifts daily, these strategies aren't just nice-to-have—they're essential for survival and success. If you're leading in this space and looking to refine your approach to productivity, let's connect and share insights that propel us forward! #techleadership #productivitytools #teamleader

"Siloed development” has come up again and again in our latest research. It’s a quiet killer of innovation, especially in hybrid organizations. Right now, teams solve the same problems in parallel. This can manifest itself in a variety of ways, from data being trapped in departments to AI tools being used to amplify isolation instead of alignment. That’s why today, in an age where AI is being used to accelerate every function in the workplace, the organizations that connect rather than compartmentalize will be the ones that succeed. In order to do that, Teamship needs to be brought in. In Never Lead Alone, I define Teamship as cross-functional collaboration without hierarchy. In other terms, this means trust is more important than titles and peers co-elevate one another toward a shared mission. Teamship the foundation of a new AI + Human Leadership Playbook, one built on: 1. Peer-to-peer accountability: Teams hold each other responsible for outcomes and deliverables. 2. Co-created intelligence: AI helps surface insights across functions and humans connect the dots. 3. Architected hybrid patterns: Intentional design of when and how teams intersect, so collaboration becomes more of a habit. Breaking silos is a behavioral and relational challenge as much as it is a structural one. And it starts with leaders who replace “my team” with “our team.”

That’s the thing about feedback—you can’t just ask for it once and call it a day. I learned this the hard way. Early on, I’d send out surveys after product launches, thinking I was doing enough. But here’s what happened: responses trickled in, and the insights felt either outdated or too general by the time we acted on them. It hit me: feedback isn’t a one-time event—it’s an ongoing process, and that’s where feedback loops come into play. A feedback loop is a system where you consistently collect, analyze, and act on customer insights. It’s not just about gathering input but creating an ongoing dialogue that shapes your product, service, or messaging architecture in real-time. When done right, feedback loops build emotional resonance with your audience. They show customers you’re not just listening—you’re evolving based on what they need. How can you build effective feedback loops? → Embed feedback opportunities into the customer journey: Don’t wait until the end of a cycle to ask for input. Include feedback points within key moments—like after onboarding, post-purchase, or following customer support interactions. These micro-moments keep the loop alive and relevant. → Leverage multiple channels for input: People share feedback differently. Use a mix of surveys, live chat, community polls, and social media listening to capture diverse perspectives. This enriches your feedback loop with varied insights. → Automate small, actionable nudges: Implement automated follow-ups asking users to rate their experience or suggest improvements. This not only gathers real-time data but also fosters a culture of continuous improvement. But here’s the challenge—feedback loops can easily become overwhelming. When you’re swimming in data, it’s tough to decide what to act on, and there’s always the risk of analysis paralysis. Here’s how you manage it: → Define the building blocks of useful feedback: Prioritize feedback that aligns with your brand’s goals or messaging architecture. Not every suggestion needs action—focus on trends that impact customer experience or growth. → Close the loop publicly: When customers see their input being acted upon, they feel heard. Announce product improvements or service changes driven by customer feedback. It builds trust and strengthens emotional resonance. → Involve your team in the loop: Feedback isn’t just for customer support or marketing—it’s a company-wide asset. Use feedback loops to align cross-functional teams, ensuring insights flow seamlessly between product, marketing, and operations. When feedback becomes a living system, it shifts from being a reactive task to a proactive strategy. It’s not just about gathering opinions—it’s about creating a continuous conversation that shapes your brand in real-time. And as we’ve learned, that’s where real value lies—building something dynamic, adaptive, and truly connected to your audience. #storytelling #marketing #customermarketing

One of the most important relationships at any tech company: engineering and design. When this partnership falters, brilliant ideas die on the vine. When it thrives, just about anything is possible. Since I joined in 2015, we've tested many ways to partner across disciplines. The traditional "designers create, then throw specs over the wall to engineers" approach? That’s long gone. Here's what works for us: 1. Erase the handoff mentality entirely Our strongest teams have designers and engineers working in parallel from day one. Engineers join design discussions early, providing technical guidance while concepts are still fluid. This prevents the scenario of a beautiful design proves technically impossible after weeks of work. 2. Create rapid feedback loops Julie Wang is an engineer on our team who has partnered really well with design. A tip she shared recently: "I send screen recordings at all milestones so designers can critique early." The earlier this partnership starts, the more time engineers have to fix bugs, too. 3. Value hybrid skills Our most successful products come from teams where engineers understand visual principles and designers grasp technical constraints. When team members can translate between these worlds, implementation remains true to the vision. 4. Communicate constantly – not just at milestones We've use dedicated Slack channels where work-in-progress is shared continuously. Questions are answered in minutes, not days. 5. V1s, not MVPs We've officially banned the term "MVP" at Duolingo – a policy that received spontaneous applause when I mentioned it at #Config2025 recently. Instead, we focus on shipping "V1s" that genuinely meet our quality standards. Your first version should be something you're proud of, not something you're apologizing for. Big picture: if the relationship between engineering and design is strong and fluid – and everyone has a sense of ownership – there is no ceiling to what you can build. 

Hey Data Lovers! 👋 One mistake I see on projects is using the same approach to gather requirements every single time. But the right elicitation technique depends on the situation. Need deep insights from a business owner or SME? Go for a one-on-one interview. Need Finance, Sales, and Operations to align on a common process? Run a workshop. Rolling out a new report or dashboard to a large user base? A survey can help you gather feedback at scale. If users keep saying, ‘We’ll know it when we see it,’ stop debating and build a prototype. It’s often the fastest way to refine requirements. And if you want to understand how work really gets done, don’t just ask. Observe the process. You’ll often uncover pain points that never come up in meetings. Interestingly, frameworks like PMI-PBA emphasize that there is no single best elicitation technique. The key is choosing the one that best fits the context. That’s what separates requirement gathering from real business analysis. See you in the next one! #BusinessAnalysis #ProjectManagementInstitute #PMI #PBI #ProjectManagement