Team Collaboration in Product Innovation

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!

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

Do you believe that a PM's job is to "protect the team" and help them focus on execution? That product management should own the WHY and WHAT, being the expert on the customer and business, leaving the HOW to the team? I used to think this way too, until I realized it significantly blocked innovation. When I took sole responsibility for the why and what, I found that I was: • Keeping my team from direct contact with stakeholders, making me the only person exposed to different perspectives on a problem • Providing strategic context without really allowing the team to work with it • Delivering predefined solutions, holding the team accountable only for the final step Even when the team was given a problem to solve, I bore much of the responsibility on my shoulders, thinking it was for the best. Until I realized it was not. True innovation comes from considering different perspectives from the beginning. The entire team should feel responsible and accountable for the why, what, and how, and work together to define how to best get there. Since I started to think this way, I’ve witnessed: 📋 Easier prioritization as we collectively weigh different perspectives and take responsibility for the product in the short, medium, and long term 💝 The team's understanding of customers has deepened, allowing them to empathize and innovate more effectively 🤝The team’s grasp of stakeholders' point of view has improved, unlocking a better understanding of business constraints and opportunities 🪽A lighter burden on my shoulders, as I no longer feel the pressure of always having to have all the answers Below, I've shared my old and new sketches of the product's role within a team and how I coach my PMs to think about responsibilities within a product team. I’m curious, how would you define the roles of different competencies in your product team? #ProductInsights #Innovation #ProductDevelopment #ProductManagement

Innovation doesn’t happen in isolation It happens when teams, disciplines and companies decide to build real relationships—the kind that push boundaries instead of protecting comfort zones That’s why the story of IDEA Design Mindset in Spain stands out A real reminder of the power of collaboration done right IDEA Design started as a product-development studio in Murcia with a clear aim: blend strategy, engineering and design into solutions that genuinely solve problems Their work now spans medical devices, industrial design, packaging, and technical product development What matters isn’t just the portfolio—it’s how they operate They partner deeply, stay close to customer challenges, and co-create instead of designing in a vacuum That relationship-first mindset is why their journey has been packed with global recognition: iF Design Awards in the Medicine/Health category New York Product Design Awards Red Dot and BIG SEE accolades across multiple years Awards don’t matter on their own What matters is why they’ve won them: because they build trust with clients, learn the nuances of the industries they serve, and create long-term engagement instead of transactional output In healthcare and medtech—where risk is high, timelines are tight, and user experience is mission-critical—this approach isn’t optional It’s the difference between shipping a product and shaping a market Their work with companies like INBENTUS Medical Technology, developing rugged field-ready ventilators, is the perfect example That type of device doesn’t happen without tight collaboration between designers, engineers, clinicians and manufacturers. It takes aligned teams, clear communication and shared accountability It’s a demonstration of how the right relationships multiply capability And that’s the point worth highlighting IDEA Design’s journey is proof that strong partnerships drive stronger outcomes. Looking ahead, their future will be shaped by the same principles that built their past: Deep collaboration with clients Cross-functional development A commitment to understanding needs before solving them Good People making a difference, sounds so simple But it's the simple things people miss, and that really make a difference!

Why do product teams and other teams clash so much? "It’s just different priorities", right? Wrong. Very Wrong. Product is the conduit through which priorities become reality. If not aligned, trouble's always brewing. The truth: relationships define your product’s success. A PM I worked with rushed our product update. Ops wasn’t informed, and customers called confused. The blame game started, and trust was broken. This led to: - Missed targets for both teams. - Frustration on every side. - Delays that could’ve been avoided. - Damage to customer perception. Burnout! Strong relationships don’t just happen.  You need to build them. Here are 7 proven ways to unite your teams: 1. Regular check-ins Host !short!, cross-team syncs every two weeks. Focus on alignment. Don't be afraid to chitchat. You’ll spot problems before they escalate. 2. Shared OKRs Set goals that depend on all teams contributing. This builds alignment and reduces silos. Make sure everyone knows them! 3. Empathy sessions, Steelmanning Put yourself in another team's shoes. You’ll see their challenges in a new light. 4. Open roadmaps Share product plans early and often. Other teams will feel informed, involved, valued! 5. Simplify language Drop the jargon; focus on clarity. This makes collaboration much smoother. 6. Celebrate shared wins Highlight wins that cross teams. You’ll build goodwill and deeper trust. A release isn't a marketing win, it shouldn't feel like one. 7. Resolve conflict early Set clear steps for handling disputes. This keeps issues small and progress steady. Avoid at all costs being passive agressive. AT ALL COSTS Great products need great team relationships. When teams align, everyone wins. And you want everyone around you to feel they win when they work with you. PS. What’s 1 thing you’ve done to align teams better?

One of the most underestimated challenges in combination product development is bridging the gap between Pharma and Device teams. Pharma brings deep expertise in clinical pathways, regulatory labeling, and therapeutic outcomes. Device teams, on the other hand, live and breathe design controls, risk analysis, and human factors. Both are essential. But too often, they operate in parallel, not in sync. I've seen projects slow to a crawl because ownership was unclear. Risk files left in limbo. Feedback lost in translation. Not due to lack of talent, but because teams weren’t aligned on what success together looks like. What made the difference for us was intentionally rethinking collaboration. We started bringing Pharma and Device leads into the same conversations early, not just for check-ins but for co-ownership. Shared milestones. Unified risk deliverables. A culture in which asking the other team, “What does this mean?” became second nature. The shift was subtle but powerful: engineers began considering clinical narratives. The pharma team started flagging usability insights. Barriers dissolved. Combination products demand more than technical excellence. They require teams who are willing to cross the aisle and think beyond their functional walls. #CombinationProducts #CrossFunctionalLeadership #MedTech #Pharma #DeviceDesign #HumanFactors #ProductDevelopment #InnovationCulture #injectables 

Most PMs think collaboration is about team meetings and shared docs. They're missing something far more powerful. — 𝗧𝗵𝗲 𝗥𝗲𝗮𝗹𝗶𝘁𝘆 In my 15 years leading product teams, I mainly operated on winning teams. Since becoming a creator, I've learned: a rare few product teams operate fundamentally differently from everyone else. Here's what no one's talking about: — 𝟭. 𝗧𝗛𝗘 𝗖𝗢𝗟𝗟𝗔𝗕𝗢𝗥𝗔𝗧𝗜𝗢𝗡 𝗠𝗬𝗧𝗛 Most teams lock themselves into a familiar pattern: • Strategy happens once a year, behind closed doors • Roadmaps become endless point-to-point exercises • Teams chase tasks without understanding the "why" • Planning becomes a checkbox rather than a conversation But elite teams have learned something deeper: True collaboration isn't about the ceremony of working together. It's about how teams learn and adapt together. — 𝟮. 𝗧𝗛𝗘 𝗘𝗟𝗜𝗧𝗘 𝗣𝗟𝗔𝗬𝗕𝗢𝗢𝗞 Here's what I've seen the best teams do differently: They build living strategies → Strategy evolves with learning, not annual declarations They test rather than debate → When opinions clash, they turn them into hypotheses to validate They share the journey → Every learning, every pivot, every insight becomes part of the team's collective intelligence They stay grounded in reality → Constant customer contact and data keep decisions anchored in truth — 𝟯. 𝗧𝗛𝗘 𝗧𝗢𝗢𝗟𝗜𝗡𝗚 𝗚𝗔𝗣 The challenge with most product tools: They're built for documenting decisions, not enabling continuous learning. That's where Jira Product Discovery caught my eye: • It creates space for evolving strategy, not just static plans • It helps teams move from debate to validation • It connects high-level thinking to ground-level execution • It makes learning visible and actionable You can try it here (free): https://lnkd.in/e8R84puS — 𝟰. 𝗧𝗛𝗘 𝗣𝗔𝗧𝗛 𝗙𝗢𝗥𝗪𝗔𝗥𝗗 The transition starts with fundamental shifts: → Building a shared language for priorities and progress → Making product conversations transparent and accessible → Matching investment to validation, not hope → Creating space for experiments and quick learning — 𝟱. 𝗧𝗛𝗘 𝗧𝗥𝗨𝗧𝗛 After profiling tens of product teams, I've seen it consistently: The best ones don't just collaborate more. They collaborate differently. They've turned learning and adaptation from aspirations into daily reality. #ProductManagement #JiraProductDiscovery #AtlassianPartner

Finding product-market fit is hard. But building the way your team works together? That might be even harder. In startups and corporate innovation alike, we pour time, money, frameworks, and effort into testing the market. Is there demand? Will they pay? How do we scale it? (And if you know me at all, you know I LOVE a good framework.) That’s the visible part of the iceberg. What’s beneath the surface is what I’ve started calling: Team-Operating-Model-Collaborative-Fit. (Yeah, it’s a mouthful. The ol’ TOMCF.) This isn’t just about rituals or tools. It’s about: 🔥 Handling conflict together when things get rough 📉 Interpreting data (and each other) under uncertainty 🧮 Making better decisions 😊 Building empathy for each other through learning about their purpose, backstory, and skillsets ❤️ Remembering the goal is to empower each other, not just get the work done This is the work behind the work. It’s always messier, harder, and more consequential than just validating a market. Because no matter how good your product is—if your team can’t collaborate with intention, it won’t scale. ⚡️⚡️⚡️ How to begin: It could be as simple spending some time together at an offsite (mini-golf, dive bar, city park) and reflecting upon what behaviors and mindsets have gotten us this far? Which might be holding us back? What might be new ones needed to achieve our goals? Or you can tell your life story through interpretative dance, I’ve found that works pretty well.

Every time a team member stays silent, you lose more than morale. You lose momentum, market share, and millions. Harvard Business Review confirms a staggering 70–90% of innovation initiatives fail. But here’s what most leaders miss: The failure isn’t happening in your idea pipeline. It’s happening in your team dynamics. I worked with a tech company after their third failed product launch, despite brilliant engineers, strong leadership, and cutting-edge tools. What I saw: • Interrupted conversations • Defensive tension • Misattributed ideas • Silence from key contributors This wasn’t a process problem. It was a psychological one. When the brain senses threat, the prefrontal cortex,  your innovation engine, shuts down. Innovation isn’t blocked by lack of ideas. It’s blocked by unsafe environments. We implemented the JOY Framework™ to focus on: ✅ Communication safety ✅ Purpose alignment ✅ Conflict intelligence In just 90 days: • Innovation implementation ↑ 43% • Team retention ↑ 28% • Cross-functional collaboration ↑ 35% • Burnout indicators ↓ 41% No new brainstorming tools. Just new conditions. If your innovation is stalled, your culture may be the bottleneck. Because psychological safety isn’t just about morale, it’s about ROI. I’m opening 3 JOY Breakthrough Strategy Sessions for People leaders ready to rewire innovation from the brain up. Comment “INNOVATE” if that’s you.

With the olympics having just flown by, we're having a throwback to our conversation with Clarissa Riggins and her spot-on statement that product management is a team sport, not a solo performance 🏅 What does this mean in practice? Too often, teams (including product) see their job in isolation...  "That's not my problem, that's sales..." Those situations really call for a mindset shift. Product is not just responsible for the technology that is solving the problem, it's about working cross-functionally: That includes working out the details: - Collaborating with sales to articulate the value proposition - Partnering with the implementation team to define model installations - Providing support teams with the right tools and knowledge to service clients This holistic approach doesn't just add revenue to the business… It creates value for the customer from the very beginning and throughout the entire experience. Clarissa (CPO at Experian Health): “It's a set of activities that we undertook as an organization, and we're still transforming the organization. But a lot of what we did, what I did really, is infusing kind of a rebel mindset, opening the aperture of how our product managers and our team should be looking at the customer experience.” Be the rebel in your own organization: Shift the mindset from solo performance to team sport. Your team members extend beyond your immediate product group and include every function that is part of the customer journey… How are you fostering cross-functional collaboration in your product management practice? #ProductManagement #TeamWork #CrossFunctionalCollaboration #CustomerExperience