Collaborative Design Tools for Teams

One of the clearest signals of whether a transformation is working isn’t in the plan - it’s in the conversations happening in your teams. So pay close attention to the frequency of healthy debate, constructive challenge and openness to new and divergent ideas that takes place. If the frequency is low… …there is the risk of creating the illusion of performance because people readily ‘understand’ each other, agree on everything, collaboration seems to flow smoothly and there is a collective sensation of progress. However, the opportunity cost is teams gets trapped in their own paradigms, opportunities get overlooked, risks ignored - and ultimately their output becomes derivative not innovative, performance diminishes as opposed to improving and compounding. If the frequency is high… …there is a level of psychological safety that allows for team members to be more objective, to speak up with relevant ideas, to constructively challenge each other, and bring their diverse perspectives and experiences to the table - in the knowledge it won’t be held against them. This opens up the opportunity of reframing the paradigm, and connecting different perspectives and ideas. Ingredients for creativity, innovation, resilience and performance. You see homogeneous teams might feel easier, but easy doesn’t translate into Performance. Here are a few ideas to experiment with your teams… 1. Intentionally foster a team environment that replaces scepticism with intellectual curiosity, an open and learning mindset.   2. Consider how you can create a ways of working that allows all ideas and perspectives from everyone in the room to be heard. 3. Encourage dissenting perspectives. Surrounding yourself with people who are willing to disagree with you and challenge your perspectives and each other. 4. Consider whether you may need to invite others to that creative or idea generation meeting to ensure you get a broader perspective. 5. De-stigmatise failure through sharing past mistakes and celebrating lessons learnt. 6. Institutionalise a team culture of healthy candour. Candour is one of the key attributes to improving the quality of output, levelling up creativity and enabling effective collaboration. What would you add? #transformation #culture #psychologicalsafety

How often do we design with people, instead of for them? It’s easy to fall into the trap of thinking that creativity is something only designers hold the key to. But when we pause and engage with communities, we realize something powerful: Creativity thrives within the community itself—it just needs the right conditions to flourish. Take, for example, the Collective Action Toolkit (CAT) by Frog. It’s not just a tool; it’s a framework that empowers communities to solve problems by tapping into their collective strength. Through a series of activities—like clarifying goals and imagining new ideas—small groups around the world have used this toolkit to not only share their thoughts but to take decisive action that addresses their concerns. The beauty of this approach is in its adaptability. It’s not a one-size-fits-all model. Each group can mould it to fit their unique needs, ensuring that everyone’s voice is heard and valued. But collaboration, as we know, isn’t always easy. There’s often discomfort, sometimes even conflict, when differing ideas meet. Yet, as designers, navigating these challenges is where true progress happens. As Otto Scharmer and Peter Senge, leaders in organizational development, have shown, it's in this space of tension that new solutions are born. A recent contribution from @Design Impact offers a set of guiding principles for designers to keep in mind when working with communities. One of these, “Value me for who I am, not who I’m told to be,” resonates deeply. It’s a reminder that behind every design is a real person, with history, emotions, and passions. When we acknowledge that, we move beyond simply gathering feedback—we tap into real leadership within the community. At the end of the day, Social innovation isn’t just about creating a product or service. It’s about co-creating, about building alongside communities rather than handing down solutions. It’s about fostering a space where everyone’s creativity can shine, and where long-term, sustainable change is possible. Have you been part of a design process that values community leadership? What challenges—and opportunities—did you encounter along the way?

👷🏻♀️ If you're building with #PowerAutomate or thinking about how agents can level up your workflow automation, check out our episode with Catherine Han and John Liu. They joined me on #TheLowCodeRevolution show to share how their third-party tool, Flow Studio MCP, works alongside AI models to build and optimize #PowerAutomate flows. 📺 Watch now at https://lnkd.in/eDvyFUXz ⚠️ Note: This is not a Microsoft product - it's a tool developed by Catherine and John that integrates via APIs. One of my favourite moments was watching the agent not just diagnose a failed flow but actually fix it! The run down of live demos to show how the tool works in practice: 🤖 Build flows using natural language - Describe what you want, and the agent creates the flow - including triggers, actions, and approvals. ⚡ Faster troubleshooting & optimization - The tool helps identify errors, explain root causes, and can fix issues automatically. 🔍 Deep visibility into your environment - Query environments, analyze failing flows, and get instant insights without digging through the UI. 🧠 Governance + consistency at scale - Enforce naming conventions, review flows against standards, and clean things up in seconds. A shout out was made to Matthew Devaney 😊 ⏱️ Advanced patterns made easy - From approval escalations to complex logic - the demos show how AI can handle scenarios that aren't exactly "beginner-friendly" 👏🏻👏🏻👏🏻 Huge thanks to Catherine and John for sharing their work and walking us through the live demos! ✅ Learn more: 🔗 Flow Studio MCP including information on security, privacy and responsible AI - https://mcp.flowstudio.app 🔗 Flow Studio MCP Guides: Getting Started, Debug, Build, Tools, Copilot Skills - https://lnkd.in/eZTzFqRZ #Microsoft #PowerPlatform #PowerAutomate #AI #powerplatformadvocates

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!

My research shows that a culture of collaboration lies at the heart of any organisation looking to thrive over the next few decades. The fact that innovation and proactive change comes from ideas, from fresh perspectives and from challenging conventions means that we have to find ways to put collaboration at the heart of our strategic planning. It requires factors to be developed, recognised, and understood by everyone. It cannot be the preserve of the hierarchy or line managers; it is an organic process that needs nurturing. It is so important that we remember that great ideas can come from anyone, at any time, no matter what job they do or where they work in an organisation. At the heart of collaboration sits trust and a sense of psychological safety. A climate where people can be honest and egos are set aside. Here I my 5 top tips for auditing whether you have a healthy collaborative climate… and before you think about the eight, remember that you need to check that it isn’t just you that feels you check the boxes but people at every level in your teams! • Trust: Do people see their colleagues as exactly that, or do they sense a culture of competition which prevents them from being honest, from sharing their challenges, strengths or ideas. Do people feel confident enough to give others credit for their actions, thinking and contributions or threatened by it? Collaboration can only flourish in open, confident, and honest environments where there is a real sense of shared purpose and value. • Support: Is there a spirit of support where people don’t feel judged if they ask for it or interfering if they offer it. Do people recognise their own and each other’s strengths and weaknesses in a constructive way? • Sharing: Do people/teams share their ideas, challenges, and processes openly, both when things are going well and when they’re not? Communication is so very important. • Inspiration: People can only develop new thinking if they are catalysed by new experiences. If you only ever have people with similar job descriptions, ways of working and experiences in the room, you are going to breathe stale air where at best you tweak your methodologies? Do you give people time and opportunity to experience new things; working across teams and departments? Do you value their interests and hobbies away from work? Inspiration comes from often random and unplanned moments, make sure you allow space and time for those to happen. • Success: Do you regularly celebrate ideas, achievements and thinking, not just the big stuff but the micro too. We are often so busy looking to at the summit we forget the work being done to get to base camp. Also, the four previous tips are fuelled by feel good moments and nothing breeds success like success. Take time out to celebrate, together. #collaboration #leadership #culturematters

Top 6 AI tools for design & workflow in 2026 👇 Yes, not all of them are “design tools.” Yes, that’s exactly the point. I spent time exploring tools beyond just UI screens… Because real product work is not just design anymore. It’s workflows. Automation. AI orchestration. Here are 6 that actually matter right now: 1. Paperclip AI https://lnkd.in/dXkCrnbe Local-first AI for organizing research, notes, and work items. But it goes deeper. It acts like an orchestration layer for AI agents. Goals. Budgets. Audit logs. Agent “heartbeats.” If you deal with messy research or multi-step thinking, this is insanely powerful. 2. Flowstep https://flowstep.ai Prompt → UI designs. It generates wireframes and full interfaces on an infinite canvas. You can iterate fast. Refine layouts. Explore ideas visually. Feels like Figma + AI had a smarter child. 3. Moonchild AI https://moonchild.ai Turn PRDs into actual UI screens. It helps with: User flows UX problem solving Moodboards Design systems This is not just generation. It’s structured product thinking. 4. Dify https://dify.ai Visual builder for AI apps. Drag. Drop. Deploy. You can create: Chat apps Text-generation tools Custom AI workflows If you ever wanted to ship your own AI product without heavy coding, start here. 5. Flowise https://www.flowise.io Low-code builder for LLM workflows. Think: Connecting multiple models Creating agent flows Shipping APIs fast Great for prototyping AI features inside real products. 6. n8n https://n8n.io Automation on steroids. Connect apps. Trigger workflows. Automate repetitive ops. Designers ignore this. Smart designers don’t. Because real impact = design + systems. Here is the shift most designers are still missing. The future is not just UI design. It’s: Design + AI Design + automation Design + systems thinking Tools like Flowstep and Moonchild help you design faster. Tools like Dify, Flowise, and n8n help you build smarter. And tools like Paperclip help you think better. AI will not replace designers. But designers who understand workflows will replace designers who only push pixels. Use these tools for: Speed Exploration Systems thinking Execution Not just aesthetics. Because in 2026… The best designers are not just designing screens. They are designing how things work. If you had to pick ONE tool to explore this week, Which one are you trying first?

Automating Autodesk Construction Cloud with Open-Source Low-Code Agents 🤖   Connecting directly to LLMs is powerful, but a dynamic AI agent needs more than just raw intelligence.   It needs to decide how to act and respond based on context and broader goals, without requiring us to explicitly program every step.   n8n is an open-source, low-code workflow automation tool with built in AI features, reducing a lot of the complexity involved in controlling agents.   It also makes it easier to apply Retrieval-Augmented Generation (RAG), which improves AI responses by finding relevant data from external sources before generating text.   RAG uses AI-generated embeddings to classify and search documents based on semantic meaning rather than just keywords, ensuring more relevant and context aware results.   This means: ✅ Smarter AI decisions based on contextual rather than keyword-based searches ✅ More accurate and meaningful interactions with project data ✅ A straightforward way to leverage AI without complex custom development   While hallucinations still happen, tools like n8n are great for quickly prototyping with out of the box AI functionality, with the ability to scale when needed.   With ACC's open APIs, we can easily bring project data into the AI knowledgebase. Here I'm extracting data from ACC Issues and RFIs, querying it using AI, and updating records where needed.   To take this further, n8n could be configured to run scheduled updates to keep the RAG databases in sync with the ACC project.   This excites me because with a solid foundation it's possible to automate entire processes rather than individual tasks. For example drafting an RFI response by reviewing specifications, assigning the correct person to review, flagging critical issues and escalating if not closed out.   🏁 Getting Started n8n is free to run locally. You can follow this guide to set it up: https://lnkd.in/gYwm5sSD   🔗Also check out the ACC APIs: https://lnkd.in/g_TSeUYA   🔗My previous post on Copilot Studio with ACC: https://lnkd.in/g4jWacuK   #Autodesk #n8n #Automation #OpenAI

Make vs n8n vs LangGraph vs CrewAI - the automation tools everyone's comparing wrong. People keep asking "which is best?" when they should ask "which dimension does my problem live in?" After building 30+ workflows across all four platforms, here's what actually matters: 1️⃣ Make excels at simple A→B→C integrations. Connect Stripe to Sheets to Slack. Done. It's been around since 2012, so it's polished but limited. Perfect for marketers who need quick wins. 2️⃣ n8n brings visual programming with actual logic. Loops, conditionals, error handling plus AI agents that can make decisions. Self-hostable too. Engineers love it because it scales without breaking the bank. 3️⃣ LangGraph is where things get serious. Graph-based AI workflows with state management. Your agents remember context, handle complex reasoning, coordinate actions. This is production-grade AI orchestration. 4️⃣ CrewAI simplifies multi-agent collaboration. Instead of one AI doing everything, you assign roles: researcher, writer, analyst. They work together like a real team. Less code, more results. The pattern here is each tool adds a dimension of complexity: - Make: Linear automation - n8n: Branching workflows   - LangGraph: Stateful AI systems - CrewAI: Collaborative agents Stop comparing features. Start matching tools to problem complexity. Over to you: Which dimension does your problem actually live in and what are you using right now?

Your biggest threat isn't disruption. It's when your best people compete instead of collaborate. I've watched brilliant teams destroy themselves. Not because they lacked talent. But because everyone fought for themselves.  Instead of fighting for each other. The difference between strong and weak cultures? ✅ Strong cultures work together to win together. ❌ Weak cultures work alone and lose together. Here's how to build a culture where people actually work  with each other, for each other: 1. Start meetings with "who needs help?" → Ask this before anything else. → People share what's hard. → Others jump in to support. 2. Reward collaboration over competition → Track who helps others succeed. → Promote the people who lift others up. → Make teamwork the fastest path to success. 3. Share credit loudly and publicly → "Sarah closed the deal with Marc's technical support." → Name every person who contributed. → Make helping visible and valuable. 4. Create shared goals, not competing ones → Sales and product win together or lose together. → No department succeeds if another fails. → Align incentives toward collective wins. 5. Fire anyone who isn't a team player → One person working for themselves is poison.  → They'll rot your company from the inside out.  → Protect the many from the few. When people work with each other, for each other,  companies become unstoppable. When people work against each other, for themselves,  even the best strategies fail. Which culture are you building today? 👉 Repost to help more founders build collaborative cultures Follow Christian Rebernik for more on building strong teams