Team Collaboration Techniques

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

If you are in a Product Management role, here's one of my best tips: partner with your Sales Leaders. Yesterday, I presented our AI Foundation Models strategy to 10k+ sellers and partners at our Americas Sales Kickoff for Q3 in Washington, DC. I enjoyed sharing the stage with one of my favorite colleagues, Madison Gooch, the VP of Sales in the Americas for watsonx. We've come a long way working together, more than six years building products and serving all kinds of customers: from small startups to some of the largest and most complex organizations. Your sales team interacts with customers daily. As a product leader, you must: 1. Build trust with your sales team. 2. Get invited to key customer meetings by the sales team. 3. Become the sales team's best partner. 4. Encourage the sales team to provide honest feedback about the product. 5. Use their feedback to improve the product. 6. Allow the sales team to keep you grounded and focus on value rather than just features. 7. Let the sales team help craft the product messaging. 8. Ask the sales team to recommend a pricing strategy. 9. If you have multiple products in your portfolio, get the sales team's advice on how to package them effectively. 10. Regularly communicate with the sales team to stay aligned on goals and strategies. If you want to build a rocketship product, you need: - Product Market Fit - Some Virality and network effect; in my case, I am obsessed with capturing this new wave of developers adopting AI technology - and most importantly, you need sellers selling your product and make your numbers! Thanks to everyone who joined us in DC and online yesterday and for the candid messages after the session!

APIs do more than connect systems—they enable consistent, secure, and scalable interactions across applications. As products grow and diversify, REST API design becomes essential for ensuring that these interactions are reliable, maintainable, and optimized for performance. To build an API that stands the test of time, it must adhere to key REST principles: 1. Code on Demand - Flexibility to download and execute code for specialized actions. 2. Uniform Interface - Standardized methods to simplify and unify API operations. 3. Layered System - Enables scalability by allowing intermediaries like load balancers. 4. Statelessness - Each request from client to server must contain all the necessary information. 5. Client-Server - A clear separation between client and server concerns ensures modularity. These principles allow APIs to be scalable, manageable, and versatile in various architectures. HTTP Methods for CRUD Operations REST APIs primarily rely on HTTP methods to perform Create, Read, Update, Delete (CRUD) operations, making interactions predictable: - GET - Retrieve information (e.g., fetching user data). - POST - Add new resources (e.g., creating a new entry). - PUT - Update existing resources. - PATCH - Partially update resources. - DELETE - Remove resources. Using these methods thoughtfully ensures your API is intuitive and easy to maintain for both current and future developers. To provide a seamless experience and robust data handling, consider these design factors: - Simple and Fine-grained Resources - Avoid overloading endpoints; focus on specific, manageable resources. - Pagination & Links - Ensure data is accessible in manageable chunks with options like first, last, next, and prev links. - Filtering & Ordering - Allow users to query and sort data to meet their specific needs. - Resource Naming - Stick to clear, consistent naming conventions (e.g., /users/{id}), enhancing readability and predictability. - Versioning - Ensure backward compatibility by introducing versioning (`/v1/users`). Security & Reliability Modern APIs must handle sensitive data securely and reliably. Key security practices include: - CORS (Cross-Origin Resource Sharing) - Control who can access your API to prevent cross-site scripting attacks. - Idempotence - Ensure certain operations, like DELETE, can be repeated without unintended effects. - Authentication & Authorization - Implement secure, token-based access to protect user data. - Input Validation - Sanitize and validate user inputs to prevent security vulnerabilities. - TLS (Transport Layer Security) - Encrypt data in transit to prevent interception. Additional Best Practices 1. Use Self-descriptive Messages 2. HATEOAS (Hypermedia as the Engine of Application State) 3. Monitoring & Logging 4. Caching         Have I overlooked anything? Please share your thoughts—your insights are priceless to me.

If your one-on-ones are primarily status updates, you're missing a massive opportunity to build trust, develop talent, and drive real results. After working with countless leadership teams across industries, I've found that the most effective managers approach 1:1s with a fundamentally different mindset... They see these meetings as investments in people, not project tracking sessions. Great 1:1s focus on these three elements: 1. Support: Create space for authentic conversations about challenges, both professional and personal. When people feel safe discussing real obstacles, you can actually help remove them. Questions to try: "What's currently making your job harder than it needs to be?" "Where could you use more support from me?" 2. Growth: Use 1:1s to understand aspirations and build development paths. People who see a future with your team invest more deeply in the present. Questions to explore: "What skills would you like to develop in the next six months?" "What parts of your role energize you most?" 3. Alignment: Help team members connect their daily work to larger purpose and meaning. People work harder when they understand the "why" behind tasks. Questions that create alignment: "How clear is the connection between your work and our team's priorities?" "What part of our mission resonates most with you personally?" By focusing less on immediate work outputs and more on the human doing the work, you'll actually see better performance, retention, and results. Check out my newsletter for more insights here: https://lnkd.in/ei_uQjju #executiverecruiter #eliterecruiter #jobmarket2025 #profoliosai #resume #jobstrategy #leadershipdevelopment #teammanagement

Your emails say more about you than you think. 👇 Here’s how to make every email polished and professional. Acknowledge Delays Gracefully ✘ "Sorry for the late response." ✔ "Thank you for your patience." Be Clear with Requests ✘ "Let me know what works for you." ✔ "Could you confirm if this works for you?" Own Your Mistakes ✘ "Sorry, I missed that." ✔ "Thanks for pointing that out—I’ll fix it right away." Close Emails Effectively ✘ "Let me know if you need anything." ✔ "Feel free to reach out if you have any questions." Make Follow-Ups Professional ✘ "Just following up on this." ✔ "When can I expect an update on this?" Show Respect for Their Time ✘ "Can we talk about this soon?" ✔ "Would you have 15 minutes this week to discuss this?" Be Confident, Not Tentative ✘ "I think we should consider…" ✔ "Here’s what I propose we do." Avoid Wordy Explanations ✘ "I spent a lot of time rewriting this to make it perfect." ✔ "This email outlines the key points—we can discuss more in person." Offer Solutions, Not Problems ✘ "I’m not sure what to do here." ✔ "Here’s what I suggest as the next step—what are your thoughts?" Set Clear Expectations ✘ "Does this make sense?" ✔ "Let me know if this aligns with your expectations." Be Polite When Asking for Help ✘ "I need this ASAP." ✔ "Would you be able to assist me with this by [specific deadline]?" Keep It Professional When Scheduling ✘ "What time works for you?" ✔ "Are you available at [specific time and date]? If not, let me know what works instead." Emails reflect your professionalism. Get them right, and you’ll always leave a great impression. ➞ Start today by refining your communication style. -- Think this could help someone? Share it to improve the way they communicate. ♻️

🧠 “How We Brainstorm And Choose UX Ideas” (+ Miro template) (https://lnkd.in/eN32hH2x), a practical guide by Booking.com on how to run a rapid UX ideation session with silent brainstorming and “How Might We” (HMW) statements — by clustering data points into themes, reframing each theme and then prioritizing impactful ideas. Shared by Evan Karageorgos, Tori Holmes, Alexandre Benitah. 👏🏼👏🏽👏🏾 Booking.com UX Ideation Template (Miro) https://lnkd.in/eipdgPuC (password: bookingcom) 🚫 Ideas shouldn’t come from assumptions but UX research. ✅ Study past research and conduct a new study if needed. ✅ Cluster data in user needs, business goals, competitive insights. ✅ Best ideas emerge at the intersections of these 3 pillars. ✅ Cluster all data points into themes, prioritize with colors. ✅ Reframe each theme as a “How Might We” (HMW) statement. ✅ Start with the problems (or insights) you’ve uncovered. ✅ Focus on the desired outcomes, rather than symptoms. ✅ Collect and group ideas by relevance for every theme. ✅ Prioritize and visualize ideas with visuals and storytelling. Many brainstorming sessions are an avalanche of unstructured ideas, based on hunches and assumptions. Just like in design work we need constraints to be intentional in our decisions, we need at least some structure to mold realistic and viable ideas. I absolutely love the idea of frame the perspective through the lens of ideation clusters: user needs, business problems and insights. Reframing emerging themes as “How-Might-We”-statements is a neat way to help teams focus on a specific problem at hand and a desired outcome. A simple but very helpful approach — without too much rigidity but just enough structure to generate, prioritize and eventually visualize effective ideas with the entire team. Invite non-designers in the sessions as well, and I wouldn’t be surprised how much value a 2h session might deliver. Useful resources: The Rules of Productive Brainstorming, by Slava Shestopalov https://lnkd.in/eyYZjAz3 On “How Might We” Questions, by Maria Rosala, NN/g https://lnkd.in/ejDnmsRr Ideation for Everyday Design Challenges, by Aurora Harley, NN/g https://lnkd.in/emGtnMyy Brainstorming Exercises for Introverts, by Allison Press https://lnkd.in/eta6YsFJ How To Run Successful Product Design Workshops, by Gustavs Cirulis, Cindy Chang https://lnkd.in/eMtX-xwD Useful Miro Templates For UX Designers, by yours truly https://lnkd.in/eQVxM_Nq #ux #design

When I became a Head of Marketing, I thought the hardest part would be building campaigns that delivered results. It wasn’t. The hardest part? Partnering with leadership — aligning creative vision with business reality. After leading marketing at startups and scaling companies (and having a few coffee chats with fellow marketing leaders), here’s what I wish I’d known sooner: 𝟭. 𝗧𝘂𝗿𝗻 "𝗟𝗲𝘁’𝘀 𝗴𝗼 𝘃𝗶𝗿𝗮𝗹" 𝗶𝗻𝘁𝗼 "𝗟𝗲𝘁’𝘀 𝗴𝗲𝘁 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰" When leadership comes to you with wild ideas (and they will), resist the urge to immediately say "that won’t work." Instead, redirect: 💬 “What’s the real goal here — awareness, leads, or engagement?” 💬 “Let’s test a version of this in one channel first.” 💬 “Here’s how we could amplify this with our existing strategy.” Marketing thrives at the intersection of creativity and practicality. 𝟮. 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝘁𝗵𝗲 "𝗖𝗿𝗲𝗮𝘁𝗶𝘃𝗲-𝗥𝗢𝗜 𝗧𝗲𝗻𝘀𝗶𝗼𝗻" Marketing’s job is to build brand and drive results. Leadership often wants immediate ROI. This tension isn’t a problem — it’s the process. Great marketing lives in that balance between bold creative and measurable impact. 𝟯. 𝗦𝗽𝗲𝗮𝗸 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 (𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗠𝗮𝗿𝗸𝗲𝘁𝗶𝗻𝗴) I’ve made the mistake of presenting campaign click-through rates and MQL counts in a leadership meeting. I lost the room in minutes. Now I lead with: 📊 How marketing is accelerating revenue goals 📊 Where we’re de-risking spend 📊 How brand work supports the long-term vision Data matters — but tell the business story first. 𝟰. 𝗣𝗶𝗰𝗸 𝘆𝗼𝘂𝗿 𝗯𝗮𝘁𝘁𝗹𝗲𝘀 (𝗮𝗻𝗱 𝗸𝗻𝗼𝘄 𝘄𝗵𝗲𝗻 𝘁𝗼 𝘀𝗮𝘆 𝘆𝗲𝘀) Not every design debate or copy edit is worth a hill to die on. Focus your energy on the strategic moves that actually impact growth. Sometimes "good enough" gets you to market faster — and that’s a win. My colleagues at interVal hear this one "GE" all the time. 𝗪𝗵𝗮𝘁’𝘀 𝘁𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝗹𝗲𝘀𝘀𝗼𝗻 𝘆𝗼𝘂’𝘃𝗲 𝗹𝗲𝗮𝗿𝗻𝗲𝗱 𝗮𝘀 𝗮 𝗺𝗮𝗿𝗸𝗲𝘁𝗶𝗻𝗴 𝗹𝗲𝗮𝗱𝗲𝗿?

Too often, I’ve been in a meeting where everyone agreed collaboration was essential—yet when it came to execution, things stalled. Silos persisted, friction rose, and progress felt painfully slow. A recent Harvard Business Review article highlights a frustrating truth: even the best-intentioned leaders struggle to work across functions. Why? Because traditional leadership development focuses on vertical leadership (managing teams) rather than lateral leadership (influencing peers across the business). The best cross-functional leaders operate differently. They don’t just lead their teams—they master LATERAL AGILITY: the ability to move side to side, collaborate effectively, and drive results without authority. The article suggests three strategies on how to do this: (1) Think Enterprise-First. Instead of fighting for their department, top leaders prioritize company-wide success. They ask: “What does the business need from our collaboration?” rather than “How does this benefit my team?” (2) Use "Paradoxical Questions" to Avoid Stalemates. Instead of arguing over priorities, they find a way to win together by asking: “How can we achieve my objective AND help you meet yours?” This shifts the conversation from turf battles to solutions. (3) “Make Purple” Instead of Pushing a Plan. One leader in the article put it best: “I bring red, you bring blue, and together we create purple.” The best collaborators don’t show up with a fully baked plan—they co-create with others to build trust and alignment. In my research, I’ve found that curiosity is so helpful in breaking down silos. Leaders who ask more questions—genuinely, not just performatively—build deeper trust, uncover hidden constraints, and unlock creative solutions. - Instead of assuming resistance, ask: “What constraints are you facing?” - Instead of pushing a plan, ask: “How might we build this together?” - Instead of guarding your function’s priorities, ask: “What’s the bigger picture we’re missing?” Great collaboration isn’t about power—it’s about perspective. And the leaders who master it create workplaces where innovation thrives. Which of these strategies resonates with you most? #collaboration #leadership #learning #skills https://lnkd.in/esC4cfjS

Your background in video meetings is saying more than you think. 𝘉𝘭𝘶𝘳𝘳𝘦𝘥? 𝘉𝘳𝘢��𝘥𝘦𝘥? 𝘙𝘦𝘷𝘦𝘢𝘭𝘪𝘯𝘨? Your choice is impacting how others perceive you. In 2025, 𝘃𝗶𝗿𝘁𝘂𝗮𝗹 𝗽𝗿𝗲𝘀𝗲𝗻𝗰𝗲 is a critical skill to learn. As more meetings happen across distance, 𝗺𝗮𝘀𝘁𝗲𝗿𝗶𝗻𝗴 𝘁𝗵𝗲 𝗮𝗿𝘁 𝗼𝗳 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 𝘁𝗵𝗲 𝘀𝗰𝗿𝗲𝗲𝗻 is essential. One component is your choice of background. 💡 Research shows that: ↪️ Employees often misjudge the impact of personal (revealing) vs. neutral (non-revealing) backgrounds. ↪️ Some employees choose neutral backgrounds to seem more competent. ↪️ Customers, however, like seeing personalized backgrounds because it conveys greater warmth -> which increases the feeling that the service quality is higher and it does NOT diminish perceptions of competence. 🚨 Caution: Avoid polarizing visual elements (🕷️ 🐍)- they can have a negative effect! 🔍 𝗧𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝗿 𝗽𝗶𝗰𝘁𝘂𝗿𝗲? Virtual leadership requires 𝘁𝗵𝗼𝘂𝗴𝗵𝘁𝗳𝘂𝗹 𝗱𝗶𝗴𝗶𝘁𝗮𝗹 𝗽𝗿𝗲𝘀𝗲𝗻𝗰𝗲. Knowing how to influence, engage, and build relationships through a screen is a competitive advantage. 🙋♀️ I’ve used my background for years to humanize virtual interactions - family photos, meaningful memorabilia, and hobbies spark conversation and connection. 🎯 𝗬𝗼𝘂𝗿 𝘁𝘂𝗿𝗻: What’s in your background? How do you use it to build warmth and competence in virtual meetings? #SkillsOnTheRise

If you work on a data engineering or data science team, then cost reduction is likely a major point of discussion. Especially this time of year. As a data consultant, I have managed to save millions of dollars over the past few years. The surprising thing is much of those expenses come from the same usual suspects(perhaps it's not that surprising). 1. Make sure you set up partitions or clusters where needed 2. Don't build a view, on view, on view mess that takes 10 minutes to run and is used for a heavily used dashboard 3. Check to ensure you've set Snowflake idle time to 1 minute(when it makes sense) 4. Make sure you've optimized your data ingestion solution(if you're paying 100k a year for ingestion, we should talk!) 5. Have some level of governance on who can build in production 6. Create a process to review costs every month or so. New projects and workflows can suddenly increase costs and if you're not constantly ensuring your costs are managed, they will explode I'd love to hear your tips as well!