Collaborative Design Projects

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!

When ACC Collaboration Replaced ISO 19650 Publishing On one high-profile project, the team decided to “go fully digital” using Autodesk Construction Cloud. Everyone worked live in ACC Collaboration architects, engineers, even external consultants. At first, it felt smooth: models synced instantly, changes appeared in real time, and coordination seemed faster. But the problems came later. The problem: - Models were synced live but never formally published through ISO states (WIP → Shared → Published). - No review or approval cycle whatever was in the central model was assumed to be “the latest.” - A structural update overwritten without review caused major clashes with the MEP systems. - When the contractor requested “the Published IFC,” there was no traceable, approved version, only an unstable live model. The impact: - Weeks of rework due to installations based on unapproved models. - Loss of client confidence in the CDE process. - Endless debates between consultants: “We updated live, why didn’t you coordinate?” vs. “We were waiting for Published.” The recovery plan: - Re-introduced the ISO 19650 publishing cycle inside ACC with a clear workflow for moving models through states: WIP → Shared → Published → Archive. - Configured folder permissions and approval workflows in ACC. - Set a clear rule: live collaboration for internal teams only; publishing for contractual deliverables. - Enforced approval gates in ACC before any file moved to Shared or Published. - Defined a single source of truth: only Published = valid deliverable. Key lessons: - ACC Collaboration is a working method. It accelerates design, but it is not a substitute for publishing. - ISO 19650 workflows are governance. Without them, there’s no accountability or traceability. Projects fail when the two modes of working are mixed without clear rules. Takeaway: Use ACC Collaboration for speed, but enforce ISO 19650 publishing for control. Without that boundary, you end up with chaos disguised as progress. Have you seen teams confuse live co-authoring with formal publishing? What was the result? #BIM #ISO19650 #DigitalDelivery #CDE #AutodeskConstructionCloud #ACCCollaboration #DesignCollaboration #ProjectDelivery #ConstructionTechnology #AEC

Clients vs. Designers It’s not a fight. It’s a partnership We’ve all been there. The client asks for something that makes your design brain scream: “Nooo! That’s going to ruin the whole flow!” But here’s the thing: successful web design isn’t about winning battles. It’s about collaboration. Clients bring valuable insights about their audience, goals, and brand vision. Designers? They bring creativity, strategy, and technical know-how. The magic happens when they work together, blending these perspectives into something better than either side could create alone. Here’s how to shift from versus to teamwork: 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗧𝗵𝗲𝗶𝗿 𝗪𝗵𝘆 When clients make odd requests, dig deeper. What problem are they trying to solve? What’s their underlying concern? Once you understand their perspective, you can offer solutions that align with both their goals and good design. 𝗘𝗱𝘂𝗰𝗮𝘁𝗲, 𝗗𝗼𝗻’𝘁 𝗗𝗶𝘀𝗺𝗶𝘀𝘀 You’re the design expert, but clients may not speak your language. Instead of saying, “That won’t work,” explain why and present alternatives. Great collaboration means teaching, not dismissing. 𝗣𝗶𝗰𝗸 𝗬𝗼𝘂𝗿 𝗕𝗮𝘁𝘁𝗹𝗲𝘀 (𝗪𝗶𝘀𝗲𝗹𝘆) Not every design element needs to be perfect in your eyes. Focus on the changes that will truly impact the end product and be flexible on the rest. Save your energy for what really matters. 𝗣𝗿𝗼𝘁𝗼𝘁𝘆𝗽𝗲 𝗮𝗻𝗱 𝗜𝘁𝗲𝗿𝗮𝘁𝗲 Sometimes, the best way to show why an idea won’t work (or why yours will) is to prototype it. Seeing things in action helps everyone align faster. 𝗖𝗲𝗹𝗲𝗯𝗿𝗮𝘁𝗲 𝘁𝗵𝗲 𝗪𝗶𝗻𝘀 𝗧𝗼𝗴𝗲𝘁𝗵𝗲𝗿 When the project wraps, acknowledge the teamwork that made it happen. Great outcomes are the result of trust, communication, and compromise on both sides. The best websites are built through collaboration, not competition. At the end of the day, both clients and designers are on the same team—working toward a product that looks great, performs well, and meets business goals. So, next time you’re tempted to dig in your heels, remember: It’s not “me vs. you”—it’s “us vs. the problem.” And when we approach it that way? Everybody wins. --- Follow Jeff Gapinski for more content like this. ♻️ Share this to help someone else learn to collaborate today.

Don't overcomplicate design-to-dev handoffs. Listen up designers, dropping Figma files into the void and praying for the best: Your developers are SILENTLY SCREAMING. And no, it's not because they hate designers. Here's the truth about your current process: • You're designing in isolation • You're skipping documentation • You're ignoring technical constraints • You're using inconsistent naming conventions Instead, here's what actually works: 1. Component Audit First - Map existing components before new designs - Document reusable patterns - Align with dev team's component library 2. Design System Integration - Use real data, not Lorem Ipsum - Define clear states (loading, error, success) - Document responsive breakpoints 3. Collaborative Reviews - Weekly design-dev syncs - Live prototype reviews - Technical feasibility checks early 4. Handoff Documentation - Clear component specs - Interaction flows - Edge cases defined - Accessibility requirements Stop treating handoff like throwing designs over a wall. Start treating it like a bridge you're building together. --- PS: The best designs aren't just beautiful. They're buildable. When's the last time you asked your dev team what would make their life easier? Follow me, John Balboa. I swear I'm friendly and I won't detach your components.

Designers and developers speak different languages. But when they listen early, magic happens. A few months ago, we kicked off a new product build. The usual setup: designers finalize flows, hand off to dev, then... endless Slack threads, clarifying questions, and "this isn't what I expected" moments. Sound familiar? This time, we took a different approach. Instead of working in silos, we brought everyone into the same (virtual) room—from day one. We ran cross-functional workshops: 👉 Designers walked through their thinking 👉 Developers flagged edge cases early 👉 Everyone had a say in feasibility before pixels were polished We used Figma’s handoff tools—not just as a delivery method, but as a shared language. And we held quick weekly syncs to stay aligned, not just at kickoff. The result? ✅ Build time dropped by 25% ✅ Fewer bugs ✅ Zero surprise revisions ✅ And... team morale? Way up. Here’s what I learned: When design and dev teams collaborate early, they don’t just move faster—they trust each other more. And that trust? That’s where the real magic starts. 👥 Tag a designer or developer you love working with. And share your best tip for making the collaboration smoother.

Soft Skills in Action: A Framework for Collaborative Instructional Design Projects In instructional design, frameworks and tools set the stage, but soft skills are what keep projects moving forward. Over the years, I’ve noticed that the way we communicate, collaborate, and navigate challenges often matters more than the tools we use. Here are ten soft skills that have shaped my approach and impact: Communication: Clear, intentional communication builds trust and saves time. Translating complex ideas into accessible language helps align teams without getting stuck on perfection. Collaboration & Teamwork: Collaboration is co-creating meaning. Inviting every voice early leads to richer ideas and stronger buy-in. It requires humility and letting others contribute their expertise. Empathy: Pausing to listen, asking “what would make this easier for you?”, or adjusting timelines shows respect and helps design experiences that feel human and relevant. Conflict Resolution & Negotiation: Disagreements are inevitable. Focusing on shared goals like “What serves learners best?” often shifts tension toward collaboration, turning challenges into better design. Adaptability: Projects always surprise you. Staying grounded while embracing change keeps momentum alive even in uncertainty. Critical Thinking: Instructional design rarely follows a straight path. Defining problems precisely reveals simpler, smarter solutions. Time & Project Management: Deadlines aren’t constraints. They’re clarity tools. Milestones and check-ins keep the team aligned and accountable. Leadership without Authority: Influence comes from trust, not title. Modeling collaborative behavior and thoughtful reasoning guides decisions even when not “in charge.” Cultural & Emotional Intelligence: Awareness of diverse norms, values, and emotions prevents misunderstandings and strengthens collaboration. Reflective Practice: After each project, I ask: What worked? What would I do differently? Reflection helps refine my approach and stay intentional about growth. Soft skills may be invisible, but they’re the glue that holds collaborative design projects together. Which of these has made the biggest difference in your work? 👇More posts like this in the comments 👇 #InstructionalDesign #SoftSkills #LearningDesign #ProfessionalGrowth #Teamwork #EmpathyInDesign #LeadershipWithoutAuthority #ReflectivePractice #EmotionalIntelligence #Adaptability #CommunicationSkills #ProjectManagement #ConflictResolution #HigherEd #LearningExperienceDesign #CollaborativeDesign #HumanCenteredDesign #LXD

Why should design and construction projects use collaborative contracts? When the project is complex, the worse delivery method is DBB. The method that takes the longest is also DBB. For this reason, many complex projects can benefit from the use of collaborative contracts such as Progressive Design Build or Integrated Project Delivery. In fact, collaborative contracting will be the future for pretty much every project over 100M USD. Some other key reasons include: 1️⃣ Enhanced collaboration and teamwork: Collaborative contracts foster a culture of trust, cooperation, and shared responsibility among project stakeholders, including owners, designers, and contractors. 2️⃣ Improved risk management: By sharing risks and rewards, parties can avoid adversarial relationships, litigation, and claims, leading to better risk allocation and mitigation. 3️⃣ Early contractor involvement: Collaborative models allow contractors to participate in the planning and design phases, providing valuable input on cost, schedule, constructability, and innovation. 4️⃣ Better cost control: The collaborative approach enables more efficient pricing, reduces guesswork, and improves confidence and predictability for all parties. 5️⃣ Increased innovation: The collaborative environment encourages creativity and allows teams to explore new solutions and technologies. 6️⃣ Enhanced project outcomes: Collaborative contracts can lead to reduced costs, improved quality, and better overall project performance. 7️⃣ Flexibility and adaptability: These models allow for easier adjustments to changing needs and opportunities throughout the project lifecycle. 8️⃣ Sustainability benefits: Collaborative approaches can facilitate the implementation of sustainable practices and solutions. 9️⃣ Improved dispute resolution: Collaborative contracts often include mechanisms for proactive and constructive dispute resolution, reducing the likelihood of costly legal battles. 🔟 Optimized design development: The iterative nature of collaborative contracting allows for systematic improvement of project delivery at each design milestone. By using collaborative contracts, construction projects can benefit from improved coordination, reduced inefficiencies, and a more positive working environment, ultimately leading to more successful project outcomes. #leanconstruction

Stop brainstorming and start collaborating in more effective ways. After spending 25 years learning how to facilitate design charrettes, I have picked up a few strategies for success along the way. To be successful, you must master multiple time horizons. Let me explain: 👉 Short Term: In real time you are reading the room, managing the clock, and interrupting people when needed to keep the process flowing. Once the stakeholders understand that you are carefully managing the process, they will start to collaborate more effectively. 👉 Medium Term: As the facilitator, you need to understand the challenges and opportunities contained within the project. Develop frameworks and mental maps to help stakeholders think about the project from different perspectives. #IntegralTheory is great but you can keep it simple and use the Quadruple Bottom Line of Sustainability: People, Planet, Place and Prosperity. 👉 Long Term: Use guiding principles, goals and targets to keep the stakeholders focused on the future impacts of the project. Impacts could include concerns about climate change, quality of life issues, future expansion and more. Co-creativity is a very powerful method to align actions with words. It is a “walking the talk” to ensure that everyone has a voice. Along the way, trust-based relationships are established, leading to long term benefits for the organization and its stakeholders. I cover these topics in more detail in my book Sustainable Design for the Built Environment. https://lnkd.in/eQCth-Hf

🔄 Why Revision Control and Change Management Matters More Than Ever 🔍 In product development, change is constant—designs evolve, suppliers shift, requirements grow. But here's the kicker: the old ways of managing these changes (hello, spreadsheets and shared folders) simply don’t cut it anymore. 🚨 Why Revision Control Is Critical Revision control isn’t just about tracking edits—it’s about building a reliable system to manage product evolution. It provides full traceability, ensures consistency, and supports compliance across the lifecycle of your product. Without it, you're flying blind. 🤝 The Modern Twist: Collaborative, Multi-Team Development Modern product development involves mechanical, electrical, and software teams all working in parallel. Changes in one domain impact the others. A robust revision system must not only track changes—but synchronize them across disciplines, ensuring everyone stays aligned. 💡 How OpenBOM Makes It Work. At OpenBOM, we reimagined revision control for today’s collaborative, connected teams. Our Collaborative Workspace lets multiple contributors work on structured product data—Items, BOMs, CAD files—in real-time, with full version and revision tracking. ✅ Instant visibility into updates ✅ Baseline snapshots for audit and compliance ✅ Structured ECO workflows to manage formal change With OpenBOM, you're managing a virtual collaborative data space where users can make changes simultaneously and once not just managing revisions—you’re building a connected digital thread across design, engineering, and manufacturing. 📘 Read the full article here [link in the comments] 🔁 Interested to discuss how to support mechanical, electronics, and software teams to work together and control changes? Let's talk. #PLM #PDM #RevisionControl #DigitalThread #OpenBOM #Collaboration #Engineering #Manufacturing #ProductDevelopment #ChangeManagement

𝗧𝗵𝗲 𝗺𝗼𝗺𝗲𝗻𝘁 𝗜 𝗿𝗲𝗮𝗹𝗶𝘀𝗲𝗱 𝗺𝘆 𝗯𝗲𝘀𝘁 𝗱𝗲𝘀𝗶𝗴𝗻 𝗶𝗱𝗲𝗮𝘀 𝘄𝗲𝗿𝗲𝗻’𝘁 𝗺𝗶𝗻𝗲, 𝗺𝘆 𝗲𝗻𝘁𝗶𝗿𝗲 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵 𝘁𝗼 𝗱𝗲𝘀𝗶𝗴𝗻 𝗰𝗵𝗮𝗻𝗴𝗲𝗱. As designers, we are often trained to believe that our job is to 𝗰𝗿𝗲𝗮𝘁𝗲 — ideas, products, systems, experiences. But over time, I’ve realised something important: The best design rarely comes from one person sitting alone with a sketchbook or a screen. It emerges from 𝗰𝗼-𝗰𝗿𝗲𝗮𝘁𝗶𝗼𝗻. Whether you are working with 𝗮𝗿𝘁𝗶𝘀𝗮𝗻𝘀, 𝘂𝘀𝗲𝗿𝘀, 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀, 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝘀𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀, 𝗼𝗿 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝗶𝗲𝘀, you are never really designing alone. Every perspective adds a layer that you would have never arrived at by yourself. The moment you realise that 𝗰𝗼-𝗰𝗿𝗲𝗮𝘁𝗶𝗻𝗴 > 𝗰𝗿𝗲𝗮𝘁𝗶𝗻𝗴, your way of working and your perspective shift. •⁠ ⁠You listen more than you speak. •⁠ ⁠You observe before you decide. •⁠ ⁠You design 𝘸𝘪𝘵𝘩 people, not just 𝘧𝘰𝘳 them. Some of the most meaningful work I’ve been part of happened when the process shifted from “𝗺𝘆 𝗱𝗲𝘀𝗶𝗴𝗻” to “𝗼𝘂𝗿 𝗱𝗲𝘀𝗶𝗴𝗻.” Because the truth is: Users understand their problems better than we do. Artisans understand their craft better than we do. Stakeholders understand constraints better than we do. When these perspectives come together, design stops being an isolated act of creativity and becomes a 𝘀𝗵𝗮𝗿𝗲𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗼𝗳 𝗱𝗶𝘀𝗰𝗼𝘃𝗲𝗿𝘆. And that’s where truly impactful solutions emerge. #DesignThinking #CoCreation #UXDesign #ProductDesign #HumanCenteredDesign #Collaboration #DesignProcess