AI Tools for Project Management

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.

Four software waves built our stovepipes—AI demands we break them. Unlocking AI's true potential requires dismantling the legacy structures holding us back. What history built • Mainframe — central IT kingdoms and quarterly batch releases • Client-server — matrix teams, ticket queues, and fragmented systems • ERP — process rigidity locked behind program offices and change boards • SaaS — API glue, shadow IT, and layers of invisible debt Each era solved real constraints—but left behind a structural fossil. Today, AI ideas crawl through those layers of approvals, brittle code, and siloed data. It feels like swimming in peanut butter. The signal 💡 Ethan Mollick highlights teams pulling senior engineers out of the silo and embedding them next to domain experts. Prototypes ship in days, not quarters. I have seen this firsthand. Proof at Hitachi • HMAX — Hitachi Rail’s AI-enabled platform pairs engineers and operators at the edge. The result: up to 20% fewer service delays, 30% fewer overhauls. • AI Center of Excellence — Launched in early 2024, cross-functional pods across industries are already piloting factory line optimization and grid intelligence—in months, not quarters. The AI-first blueprint 🏗️ • Platform core — shared models, vector store, data contracts, and guardrails as self-service APIs • Outcome pods — two engineers, one domain lead, one product owner delivering weekly outcomes • Shift-left compliance — bias, privacy, and security checks run on every commit • Data as product — critical datasets get owners, live contracts, and real-time lineage • Talent marketplace — engineers rotate pods, spreading reusable patterns and surfacing hidden debt • Product-led mindset — each pod includes a product leader who owns the user experience end-to-end—reflecting what AI-native companies like those Aishwarya Naresh Reganti highlights are showing us: innovation now lives in the product, not just the model What to do next • Launch three pioneer pods with a 90-day target in high-friction business areas • Expose your 10 most valuable datasets via contract-backed APIs before coding • Automate guardrails so low-risk changes never wait for a meeting • Share every win and every tech-debt pay-down loudly across the org Bottom line 🎯 Each past wave delivered real value—and embedded real drag. AI rewards those who keep the lessons but refuse the fossils. Build a lean, automated platform at the core. Unleash fast, outcome-driven pods at the edge. And let product—not hierarchy—be where value compounds.

I found the missing piece for building AI agent teams that actually collaborate! Common Ground is an open-source framework for creating teams of AI agents that tackle complex research and analysis tasks through true collaboration. Think of it as simulating a real consulting team: a Partner agent handles user interaction, a Principal agent breaks down complex problems, and specialized Associate agents execute the work. Key Features: • Advanced multi-agent architecture with Partner-Principal-Associate roles • Full observability with real-time Flow, Kanban, and Timeline views • Model agnostic with built-in Gemini integration via LiteLLM • Extensible tooling through Model Context Protocol (MCP) • Built-in project management and auto-updating RAG system The breakthrough? It transforms you from a passive prompter into an active "pilot in the cockpit" with deep visibility into not just what agents are doing, but why they're doing it. Perfect for building agents that handle multi-step workflows and strategic collaboration beyond simple command-response chains. It's 100% open-source. Link to the repo in the comments! ___ Connect with me → Shubham Saboo I share daily AI tips and opensource tutorials on AI Agents, RAG and MCP.

🚀 Excited to share my latest Fortune column on truly groundbreaking academic work from my co-authors Professor Karim Lakhani and Fabrizio Dell'Acqua at Digital Data Design Institute at Harvard (D^3), where I serve as an executive fellow. This remarkable field experiment with 776 Procter & Gamble professionals fundamentally challenges what we thought we knew about teamwork. The research reveals the emergence of the "cybernetic teammate"—AI that doesn't just assist but actively participates in collaboration. Three breakthrough findings: 1. AI Can Replicate Team Benefits Individuals working with AI achieved nearly 40% performance gains—matching traditional two-person teams. AI is providing the same collaborative benefits we've long attributed to human teamwork. 2. Cross-Functional AI Teams Generate Breakthrough Innovation AI-augmented cross-functional teams were 3x more likely to produce top 10% solutions. This isn't marginal improvement—it's a multiplicative effect that neither human-only teams nor AI-enabled individuals could achieve alone. 3. AI Breaks Down Silos (For Real This Time) R&D specialists with AI proposed commercially viable solutions. Commercial professionals developed technically sound approaches. AI acted as a bridge, enabling each team member to think holistically across functions—achieving the "silo breaking" that leaders have struggled to accomplish through org chart reshuffles. Bonus finding: AI collaboration increased positive emotions by 64% in teams. This isn't cold, mechanical work—it's energizing and engaging. At Seven2, we're translating this research into practice with our portfolio companies, building these AI-augmented cross-functional teams to drive innovation and competitive advantage. This is the future of collaborative work—not AI replacing humans, but human-AI ensembles that combine the best of both worlds. Read the full analysis: https://lnkd.in/ef3f3pED #AI #Innovation #HBS #D3Institute #FutureOfWork #PrivateEquity #TeamDynamics

Here is the real reason why cross-functional teams fail, and how a new Harvard study proves AI may have permanently fixed it. Back in 2014, I pulled together a one-day pressure cooker at P&G. I got together Marketing, R&D, and our creative agency, all in one room. There was only one goal: to generate product marketing concepts fast for a new brand relaunch. The teams were wasting too much energy on back-and-forth. There were too many needless cycles. A set of 3-4 product concepts took 3 months to create. So I forced everyone into the same space with a hard deadline. It worked. We got about 4 ideas out the door within a day. At the time, I thought I'd solved a speed problem. I was wrong. A 2025 Harvard Business School study with P&G just validated what I'd actually fixed all those years ago. They put 776 P&G professionals through a live hackathon. They were all cross-functional teams tackling real product development challenges. Some had AI. Some didn't. Here's what the researchers found. When R&D professionals used AI, their ideas became more commercially viable. When marketers used AI, their solutions gained technical depth. AI didn't make specialists better at their specialty. It made them competent in adjacent domains. The study calls it a "boundary-spanning mechanism." AI helped professionals reason across traditional domain boundaries. R&D could think like marketers. Marketers could think like R&D. That's exactly what my 2014 pressure cooker session did. Physical proximity forced R&D to hear marketing's ideas in real time. Marketing had to engage with technical constraints immediately. The agency, who were crafting the concept cards, could incorporate both viewpoints without anything being lost in translation. Time pressure removed the luxury of retreating into specialist silos. The real problem wasn't speed. It was domain isolation. R&D couldn't think like marketers. Marketers couldn't think like R&D. Each team stayed locked in their own expertise. But now, AI makes boundary-spanning permanent. The implications go beyond productivity. If one person with AI can produce balanced solutions that used to require a full cross-functional team, what does that mean for how we structure organisations? Do we still need the same number of specialists? Do functional org charts make sense? What's the right team size when AI extends individual competence across domains? I don't have all the answers yet. But I know this: silos don't slow you down because of wasted time. They slow you down because specialists can't think across domains. And AI just fixed that.

𝗛𝗼𝘄 𝗜 𝗴𝗲𝘁 𝗼𝘂𝘁 𝗼𝗳 𝗵𝘂𝘀𝗹𝘁𝗲 𝗮𝗻𝗱 𝘀𝘁𝗿𝘂𝗴g𝗹𝗲 𝗶𝗻 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝘂𝘀𝗶𝗻𝗴 𝗔𝗜 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 I’ve always worked on large corporate and consulting projects throughout my entire career. I can really say that I know the pain points in project workflows and collaboration. Project work is full of hidden friction: 🔄 Repetitive updates 🧩 Misaligned communication 📄 Documentation that never gets finished 🤯 Mental overload from managing everything Project work shouldn’t be this hard. I discovered that AI can be a game-changer. It’s a toolbox that quietly removes the friction, so teams can actually focus on creating value. 👉 Here are 3 AI workflows I can’t imagine project work without: 📊 Project Status Report Drafting 𝗣𝗿𝗼𝗯𝗹𝗲𝗺: Creating regular updates is repetitive and often delayed. 𝗔𝗜 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: AI drafts weekly or monthly status reports from task data and notes. 𝗜𝗺𝗽𝗮𝗰𝘁 / 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀: Ensures consistent updates and professional formatting. 📍 Process Documentation Writer 𝗣𝗿𝗼𝗯𝗹𝗲𝗺: Documenting project workflows takes too long. 𝗔𝗜 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: Converts bullet points into formal standard operating procedures. Rewrites complex content into plain simple language that everyone understands. 𝗜𝗺𝗽𝗮𝗰𝘁 / 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀: Supports scaling and standardisation. 👥 Meeting Summary and Clarification Generator 𝗣𝗿𝗼𝗯𝗹𝗲𝗺: Not everyone captures the same notes during meetings. Missing information or perspectives can lead to delays or conflicts. Hidden conflicts influence team collaboration in a bad way. 𝗔𝗜 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻: AI creates a neutral, complete summary including action items and decisions. Lists missing information, reveals hidden conflicts. 𝗜𝗺𝗽𝗮𝗰𝘁 / 𝗕𝗲𝗻𝗲𝗳𝗶𝘁𝘀: Ensures team alignment and saves time consolidating notes. Helps move forward faster and improves team collaboration by avoiding or solving conflicts. AI can really be a supporter for project teams, not replace them. And it is a true game-changer. I’m really happy to announce that Christoph Schmiedinger and I will start a content series about the practical usage of AI in project management and product management. We will keep you posted. Leave a comment about your experiences. Let’s learn together.

🔥 Why Half of Agentic Projects Still Fail (And the 4 Patterns That Actually Work) The future is agentic but without the right architecture, you're setting up for disappointment. Quick pattern design framework to execute successful AI @ work Pattern #1: The Self-Checking System - The problem: AI confidently delivers wrong answers. - The solution: Build in quality checks. How it works: After generating output, the AI reviews its own work with prompts like "Check this response for accuracy" or "What assumptions might be incorrect?" Apply here: Content teams use this for fact-checking articles. Legal teams apply it to contract reviews. Marketing teams validate campaign copy. Try this: Add "Please review your answer for potential errors" to any complex AI request. Pattern #2: The Connected Intelligence - The problem: Your AI operates in a data vacuum. - The solution: Connect it to live systems and APIs. How it works: AI agents call external tools; web search for research, databases for current information, APIs for system integration. Apply here: Customer service bots that check order status, scheduling assistants that access calendars, research tools that pull live market data. Try this: Start by connecting your AI to one external data source this week. Pattern #3: Planner Approach - The problem: AI jumps to conclusions without thinking through the process. - The solution: Force systematic planning before execution. How it works: Before starting, the AI creates a step-by-step approach: define objectives → gather requirements → outline methodology → execute → review. Apply here: Financial modeling (plan analysis framework first), content strategy (outline before writing), project management (break down complex tasks). Try this: Ask "What's your step-by-step plan to solve this?" before any multi-part request. Pattern #4: Multi-agent collaboration - The problem: One AI trying to be everything to everyone. - The solution: Deploy specialized agents for different capabilities. How it works: Different agents handle their areas of expertise; one for data analysis, another for writing, another for fact-checking and then consolidate their outputs. Apply here: Research projects using separate agents for data gathering, analysis and report writing. Product development with agents for market research, technical feasibility and competitive analysis. Multi-agent approach is more complex to manage but often superior results for multifaceted challenges. Most successful implementations combine patterns: • Customer support: Tool Use (CRM access) + Reflection (response validation) • Content creation: Planning (strategy first) + Reflection (quality check) • Business analysis: Multi-agent (specialists) + Tool Use (data sources) + Planning (structured approach) Pick the pattern that addresses your biggest AI challenge. Test it on one workflow this week. Success isn't about the latest AI model; it's about thoughtful architectural choices. #AIinWork

This seems to be on everyone’s mind: how to operationalize your product team around AI. Peter Yang and I recently chatted about this topic and here’s what I shared about how we are doing this at Duolingo. For improving our product: -Using AI to solve problems that weren’t solvable before. One of the problems we had been trying to solve for years was conversation practice. With our Max feature, Video Call, learners can now practice conversations with our character Lily. The conversations are also personalized to each learner’s proficiency level. -Prototyping with AI to speed up the product process. For example, for our Duolingo Chess, PMs vibe-coded with LLMs to quickly build a prototype. This decreased rounds of iteration, allowing our Engineers to start building the final product much sooner. -Integrating AI into our tooling to scale. This allowed us to go from 100 language courses in 12 years to nearly 150 new ones in the last 12 months. For increasing AI adoption: -Building with AI Slack channels. Created an AI Slack channel for people to show and tell and share prototypes and tips. -“AI Show and Tell” at All-Hands meetings. Added a five‑minute live demo slot in every all hands meeting for people to share updates on AI work. -FriAIdays. Protected a two‑hour block every Friday for hands-on experimentation and demos. -Function-specific AI working groups. Assembled a cross-functional group (Eng, PM, Design, etc.) to test new tools and share best practices with the rest of the org. -Company-wide AI hackathon. Scheduled a 3-day hackathon focused on using generative AI. Here are some of our favorite AI tools and how we are using them: -ChatGPT as a general assistant -Cursor or Replit for vibe coding or prototyping  -Granola or Fathom for taking meeting notes -Glean for internal company search #productmanagement #duolingo

𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗔𝗜 AI doesn’t replace traditional architecture frameworks, it enhances them. Take, for example, the TOGAF Standard's #ADM. AI can act as a force multiplier for each phase. 🔸 𝗣𝗿𝗲𝗹𝗶𝗺𝗶𝗻𝗮𝗿𝘆 𝗣𝗵𝗮𝘀𝗲: Rapidly scan and synthesize architectural documentation to highlight recurring pain points. AI tools also support capability assessment. Skills inventories and role descriptions can be analyzed to identify gaps in the team’s abilities. 🔸 𝗣𝗵𝗮𝘀𝗲 𝗔: Simulate business scenarios based on real enterprise data. AI can model the impact of implementing predictive maintenance, intelligent customer service, or algorithmic procurement. AI tools can analyze stakeholder communication to identify sentiment trends and key concerns. This allows architecture teams to tailor the vision to what stakeholders care about. 🔸 𝗣𝗵𝗮𝘀𝗲 𝗕: Ingest workflow logs, screen interactions, and system traces to automatically map how business processes actually work, not how they are documented. These real-world models make it easier to identify inefficiencies, bottlenecks, and opportunities. 🔸 𝗣𝗵𝗮𝘀𝗲 𝗖: Assist by automatically profiling data sources to assess their readiness for machine learning and analytics use cases. On the application side, AI models can recommend integration points for new capabilities. 🔸 𝗣𝗵𝗮𝘀𝗲 𝗗: Simulate various deployment architectures and predict performance characteristics. This is especially useful in balancing on-premise and cloud strategies or designing hybrid environments. 🔸 𝗣𝗵𝗮𝘀𝗲 𝗘: Use-case prioritization can be supported with scoring models that assess feasibility, ROI, risk, and stakeholder alignment. AI design assistants can generate architecture artifacts: draft diagrams and interaction flows. This dramatically reduces the time required to prepare solution documentation. 🔸 𝗣𝗵𝗮𝘀𝗲 𝗙: Creating and continuously refining dependency graphs that reflect system interconnections, change risks, and stakeholder constraints. AI tools can also simulate different roadmap paths. E.g., how would a regulatory change impact the timeline? 🔸 𝗣𝗵𝗮𝘀𝗲 𝗚: Monitor project progress and detect misalignments with architecture specifications. This operates in near real-time, integrating with project management tools. Architecture compliance reviews become continuous and intelligent. 🔸 𝗣𝗵𝗮𝘀𝗲 𝗛: Monitor change signals (evolving regulations, new technologies, etc.) and surface emerging trends, risks, or opportunities. Feedback from users of AI-enabled systems can also be analyzed at scale. Applying AI to the ADM is about elevating the practice of Enterprise Architecture. The use of AI accelerates execution without losing structure. The methodology remains the same. The difference lies in how intelligently, quickly, and adaptively it can now be applied. ADM inset: © The Open Group #EnterpriseArchitecture #EA #TOGAF #OpenGroup #AI

How do you train project teams for an AI-driven environment? A question I get asked often. And here’s the truth; most PMOs start with the tools. They invest in AI platforms. Subscribe to AI-powered dashboards. Buy licenses. But they skip the most important part: Training the humans to think differently. You can’t just plug AI into a traditional PMO and expect transformation. You have to rewire how the team sees problems, data, and even their role in decision-making. When I consult for PMOs, here’s what I focus on and what’s often overlooked: 1️⃣ Start with Strategic Awareness Before you train anyone, align leadership on why AI. What business value are you trying to drive? - is it faster decision-making? - reduced delivery waste? - better forecasting? AI isn’t the solution. It’s the amplifier. If your foundation is shaky, AI will only make it worse. 2️⃣ Audit Your Current Ecosystem In almost every engagement, I find 2 things: You already have AI capabilities in your current tools (Jira, M365, Azure, etc.) Your teams aren’t trained or empowered to use them. We do a full PMO AI Audit: - What tools are you using? - What manual workflows are costing you time? - Where can AI reduce low-value effort and increase delivery clarity? This isn’t about ripping out your process. It’s about optimizing what already exists. 3️⃣ Train by Function, Not All at Once One of the biggest mistakes I see is blanket AI training. Instead, I design training by role, so each function learns to apply AI in context: - Scrum Masters & RTEs → learn to use GenAI for status reports, backlog clarity, and retros - Business Analysts → prompt engineering for user story generation, impact analysis - Product Owners → faster decision-making with AI-assisted roadmap planning - Executives → AI literacy to ask smarter questions & sponsor real innovation This step builds confidence across your org, not fear. 4️⃣ Focus on Quick Wins First Within the first 30 days, I help teams apply AI to one real workflow. Why? Because momentum is built through experience, not just theory. This could be sprint planning, risk registers, or report generation - low-hanging fruit that makes people go: “Wait, we can do this with AI?” 5️⃣Operationalize It or Risk Regression AI won’t stick unless it's embedded into your delivery culture. That’s why we build: - AI governance playbooks - Templates + SOPs for every use case - Guidelines for secure + ethical usage So that after I leave, your team still thrives and scales what we’ve built. You don’t need more AI buzzwords. You need AI readiness with delivery outcomes. That’s what I help PMOs do. 📩 DM me if your org is actively planning AI adoption and you want to get it right the first time.