Your design team isn't disengaged. They're just tired of not being heard. The gap between design and product isn't about people—it's about process. Or lack of it. Here's what I've learned: you can't fix communication by asking people to communicate better. You have to change the structure. One exercise that consistently works: Simple workshop prompt 👉 "What's blocking you from doing your best work with product?" Use Miro and let everyone add sticky notes (async, no pressure). Use AI to cluster them into themes. The themes that come up are always similar: brought in too late, feedback loops broken, missing the full picture. But here's what changes: - You stop guessing. - You have data. - And suddenly, you have a shared starting point for the conversation. The board becomes the artifact that product can actually see and respond to. What makes this work isn't just the exercise—it's what happens next. When you present those organized themes to product leadership, you're not complaining. You're diagnosing. You're showing patterns. You're leading the solution. Designers go from feeling like order-takers to being strategic partners. Product sees the gaps they didn't know existed. Stakeholders understand why they need to bring design in from day one. It's not about running more meetings. It's about creating shared visibility so everyone's working from the same truth. Bridge the gap by making the invisible visible. 🔥 http://miro.pxf.io/55rBO9 #MiroPartner

Mind Maps: More Than a Pretty Diagram In a recent discussion, I said that mind maps have become a lost tool — not because we’ve stopped using them, but because we’ve forgotten how to use them effectively. Modern tools like Miro, Xmind, and MindMeister have transformed the original paper mind map into dynamic, collaborative digital platforms. They allow real-time co-creation, task integration, and even AI-generated ideas. But here’s the issue: the discipline behind mind mapping has been left behind. In many group sessions, mind maps have become little more than colourful brainstorming boards — lots of activity, but limited insight. A true mind map is a structured thinking process, not a template to fill out. When used well, it helps teams: ✅ Break complex problems into manageable parts ✅ Identify dependencies and root causes ✅ Turn raw ideas into actionable strategies The difference is in the intent and method, not the tool. Technology should amplify our thinking, not replace it. When we skip the deliberate, associative process that makes mind mapping powerful, we end up with neat visuals that don’t move us any closer to solutions. So the next time you open a digital whiteboard, ask: Are we mapping ideas, or just decorating them?

𝟯 𝗖𝗼𝗺𝗺𝗼𝗻 𝗠𝗶𝘀𝘁𝗮𝗸𝗲𝘀 𝗶𝗻 𝗖𝗼𝗿𝗽𝗼𝗿𝗮𝘁𝗲 𝗗𝗲𝘀𝗶𝗴𝗻 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝗪𝗼𝗿𝗸𝘀𝗵𝗼𝗽𝘀 — and How to Avoid Them. Many companies proudly run “Design Thinking workshops.” But in practice, most of them fall into the same traps that make the process feel more like a checkbox than a transformation tool. Here are the 𝟯 𝗺𝗼𝘀𝘁 𝗰𝗼𝗺𝗺𝗼𝗻 𝗺𝗶𝘀𝘁𝗮𝗸𝗲𝘀 I’ve seen: 1️⃣ Treating it as a one-time event Design Thinking isn’t a workshop — it’s a mindset. A single session without follow-up rarely changes how teams think or work. 2️⃣ Skipping real user empathy Teams often rely on assumptions instead of talking to users. Without empathy, every idea is just a guess. 3️⃣ No bridge to implementation Many workshops end with sticky notes and photos… and nothing else. Without a clear next step, all that creative energy disappears. 💡 How to fix it:   • Plan ongoing design sessions, not one-offs.   • Involve real users or data in every stage.   • Assign ownership and follow through with prototypes and experiments. "𝘿𝙚𝙨𝙞𝙜𝙣 𝙏𝙝𝙞𝙣𝙠𝙞𝙣𝙜 𝙤𝙣𝙡𝙮 𝙬𝙤𝙧𝙠𝙨 𝙬𝙝𝙚𝙣 𝙞𝙩 𝙢𝙤𝙫𝙚𝙨 𝙗𝙚𝙮𝙤𝙣𝙙 𝙩𝙝𝙚 𝙬𝙝𝙞𝙩𝙚𝙗𝙤𝙖𝙧𝙙." #DesignThinking #Innovation #WorkshopFacilitation #CorporateCulture #HumanCenteredDesign

They automated everything… and accidentally killed the magic. A design director told us this story, one that hits close to home for a lot of creative teams right now. His studio had just rolled out a full stack of AI-powered tools. Automated briefs. Instant research. Seamless scheduling. Every promise of efficiency delivered. For the first time, everything was working perfectly. No chaos. No delays. No bottlenecks. But something felt wrong. The work had lost its spark. Ideas were fine, but not alive. Collaboration had become process. So he made a counterintuitive decision. He turned half the tools off. For one month, they went back to basics: whiteboards, post-its, and messy, in-person brainstorming. The change was immediate. ⚡ Energy came back. 🎨 Ideas got stranger (and better). 🤝 Collaboration felt like play again. “We realised productivity had replaced presence.” That’s the paradox of design today. The smoother the process, the flatter the thinking can become. Don’t let efficiency erase emotion. Use tools to amplify creativity, not replace it. Have you ever simplified your workflow and seen your team’s creativity come back to life?

Design is teamwork: here’s how I make collaboration easier Design doesn’t happen in isolation. Great products are the result of clear communication, shared understanding, and seamless collaboration. Here’s how I make it easier for my teams: 1. Document everything visually – From wireframes to flows, clear visuals reduce confusion and keep everyone on the same page. 2. Keep feedback structured – Using frameworks like “What works / What could improve / Ideas” helps feedback be actionable, not overwhelming. 3. Set regular checkpoints – Short syncs prevent misalignment and save time in the long run. 4. Empathize with all roles – Understanding developers, PMs, and stakeholders makes it easier to design solutions that work for everyone. 5. Foster a culture of curiosity – Encouraging questions and open discussions strengthens trust and improves outcomes. Collaboration is a skill as much as design itself. When teams work well together, ideas flow faster, decisions are better, and designs truly shine. #DesignTeamwork #CollaborationInDesign #UXDesign #ProductDesign #DesignThinking #Teamwork

Your strategic plan is a ghost. It haunts the Q4 kickoff deck, but it has little influence on how your team actually works. Why? Because culture eats strategy for breakfast. And your culture is nothing more than the sum of your daily rituals. You’re stuck in the feature factory not because your goals are wrong, but because your rituals are designed for a different purpose:  → Your weekly demo rewards a long list of shipped features, not impact.  → Your design critique produces safe, incremental changes, not bold moves.  → Your planning session defaults to adding more to the backlog, not questioning the "why." These rituals are the invisible design of your culture. And that design is perfectly tuned to ignore your new strategy. You can't install a new culture with a PowerPoint. You have to embody it with new behaviors. The solution is to stop preaching the strategy and start prototyping the culture. Instead of another all-hands to "drive alignment," try running a single "Ritual Prototype" for two weeks: ✺ Old Ritual: Hour-long demo celebrating "what we shipped." ✺ New Ritual: 20-minute "Impact Review" where each team answers: → What was our most important goal this week?  → What did we ship to achieve it?  → What did we learn from the result? This isn't just a new meeting format. It's a small, intentional provocation designed to embed a new "meme" into your team: one that values learning and impact over sheer activity. Strategy doesn't scale. Rituals do. What's one team ritual you have that's secretly undermining your strategic goals? __________ I use Systems Thinking to help leaders solve complex product and team challenges. On Substack, I explore the deeper layer: Memetic Design. ✺ Follow me Jake Redmond, MBA for more on strategic design.

Discover how structure can spark creativity! Learn how balancing clear, efficient workflows with creative freedom helps design teams innovate and thrive - without missing a beat. Check out our latest blog for the inside scoop in the comments below 👇 #WorkflowMax

⚡️ Rethink 'Overrated' in Design Thinking! ⚡️ Is design thinking just corporate jargon? Or is it the secret sauce to a thriving practice? 🏓 Picture the spinning world of tennis... Every player relies not just on skill, but a well-honed strategy. A game plan. That's how design thinking revamps our approach to everyday challenges. Case Study: Inclusive Branding in Action A colleague once spearheaded a branding initiative. The mission? Enhance diversity and inclusion. But initial strategies flopped. Why? We weren't consulting the audience we aimed to include. Sound familiar? We decided to apply a fresh design thinking approach. Here’s How: Breaking Down Barriers 1. *Empathizing For Insight*   - Hosted workshops with diverse voices.   - Collected stories, pain points, and aspirations. It shifted our perspective. 2. *Ideation Sparking Change*   - Harnessed broad ideas into focused prototypes.   - Created brands that reflected genuine inclusion, not just token gestures. 3. *Testing Through Real Scenarios*   - Released branding assets in test markets.   - Gathered candid feedback, reworked, and repeated. Design thinking fused empathy with action, breaking the barrier between brand and community. Suddenly, our branding wasn't just inclusive—it was impactful. Actionable Insight #1: Activate Diverse Perspectives 1. Curate a team as diverse as your audience. 2. Facilitate inclusive dialogue—make space for every voice. 3. Document and visualize diverse experiences. Actionable Insight #2: Prototype with Purpose 1. Start with small-scale testing—don't be afraid to pivot. 2. Measure feedback critically. 3. Implement changes iteratively. Practical Tips: 1. Build advisory boards from varied communities. 2. Create low-fidelity prototypes for quick testing. 3. Develop clear feedback mechanisms. 4. Be open to learning and adjusting for real understanding. Redefine 'overrated'. Rethink your processes. Revolutionize outcomes with design thinking. What aspect of design thinking could transform your approach to challenges? #DesignThinking #DiversityInclusion #InnovationLeadership #UserExperience #PersonalGrowth

Over the weekend, I read a few great articles about how design systems scale, and it reminded me that it’s less about tools, more about how teams work together. Scalability isn’t built from components; it’s built from clarity, shared understanding, and collaboration. When systems grow with purpose and structure, they stay useful long after the first release. Here’s a short visual summary of the key ideas that stood out to me! #UXDesign #DesignSystems #ScalableDesign

Most of the work that makes a project successful is invisible. Before the first design, line of code, or word of copy, there’s alignment. The patient, sometimes messy process of turning ideas, instincts, and goals into shared understanding. It’s the work of listening for what isn’t said. Translating between teams. Testing assumptions. Finding a shared vernacular that everyone can see themselves in. That’s the part we love most. Because when alignment clicks, everything else flows more smoothly. At Significant Other, our best projects start not with “let’s design,” but with “let’s understand each other.” #Strategy #Design #Collaboration #CreativeProcess