Collaborative Design Tools for Teams

One of the most frustrating parts of early-stage design? You spend more time managing tools than testing ideas. I’d have SketchUp open for massing, GIS for overlays, and Excel for calculations - all running at once. It was clunky, slow, and completely broke my design flow. Recently, I tried Giraffe Technology on a project, and it turned out to be one of the most useful upgrades to my workflow. 🚀 I tested three different design options in one sitting. No switching tools. No reformatting. No waiting. Here’s what stood out: ✅ Instant site analysis with contextual overlays ✅ Real-time solar radiation and shadow studies ✅ Rapid conceptual designs with built-in flexibility ✅ Live yield and area metrics ✅ Export-ready reports ✅ Seamless collaboration with team members My personal favorites? 👉 The Site Analysis Annotations : it pulled together zoning, setbacks, and overlays in one neat layer. 👉 And the Solar Radiation Tool - gave me intuitive, visual insights that usually take hours to compile. If you’re working on anything that involves early-stage planning or site strategy, Giraffe Technology is worth exploring. ✨ Watch the tutorial attached to see how I used it.

Today, our favorite chatbot Claude has gotten an upgrade. Anthropic is going all in to create a GenAI Chatbot that is for everyone from developers to teachers with their artifacts feature. Anthropic just widely released artifacts for all Claude users across their free and premium plans, as well as in their iOS and Android apps. Artifacts is a game-changer for educators, creating a dedicated window alongside the chat where Claude takes your written prompts and turns them into interactive games, presentations, websites, etc. Claude also has made it easy to publish the artifacts, so students or colleagues can interact with the activities. Mandy DePriest, on our team at AI for Education, recently demonstrated how the artifacts feature works with a quick walkthrough of a common classroom use case: creating an interactive, digital vocabulary quiz in seconds with no code and only a few simple prompts. In our training on Monday with a district in NJ, I modeled creating an interactive game out of the popular Egg Drop Challenge STEM project, adding a Batman themed twist to help students in their mission – trust me when I tell you teachers were super excited to start building their own interactive elements. If you want to try artifacts out, here are some example prompts to get you started: -Create a webpage for a high school English class based on this uploaded syllabus (we love the upload feature on Claude) -Generate an interactive math game to help 4th-grade students master comparing fractions. Use faction bars when providing students explanations for the questions -Design an interactive game to help students' learn Newton's First Law of Motion. Include an interactive element and directions for the game -Create an interactive vocabulary quiz based on keywords in the attached file We're excited about the potential of the artifacts feature to help teachers create fun and interactive ways to engage students in the classroom. Add it to the list of the many reasons to try out Claude. Have you used Claude and the artifacts feature yet? Share your best results! Links in the comments to my game and our Claude video walk through. #aiforeducation #GenAI #Claude #teachingwithAI

Many teams believe they’re being inclusive when they say, “We kept accessibility in mind from the start." But good intentions aren’t the same as meaningful inclusion. I’ve been doing accessibility and inclusive design work for 25 years. Over the last decade, I’ve focused more deeply on what true disability inclusion really means—especially when it comes to power in the design relationship. Again and again, I’ve seen the same pattern: there are levels to inclusion. And only one of them truly shifts power. Here’s how that journey tends to unfold... ranked from least to most inclusive: Level 1: “We kept accessibility in mind.” You didn’t include disabled people. You included the idea of them. This is empathy without participation, and honestly... it’s not enough. Level 2: “We tested with disabled people just before launch.” There’s progress here—real people were involved. But testing at the end only lets you ask: “Do you accept what we built?” It’s too late for meaningful change. This is just late-stage validation. Level 3: “We tested early AND at the end.” Now there’s room for impact. People with disabilities had a chance to shape the work before it was finished. Their feedback could actually change the outcome—and that matters. Level 4: “We included disabled people throughout the process.” Even better. You've moved from on from a "testing" mindset. You brought people in during idea generation, design, development, and launch. You did research. You listened. You adjusted. That’s inclusion in action. Level 5: “We co-created the solution.” ✅ This is the gold standard. You didn’t just include people—you gave them power. They helped shape the goals, question the methods, and guide the direction. It wasn’t just "your" product. It was "ours" -- co-created together. Your greatest power is to give that power away. Inclusive design means shared decisions—not just shared feedback. If you’re not sure where to start, ask yourself: 👉 Where in our process do disabled people have the power to shape what we build? And if the answer is “nowhere”—it’s time to change that. #InclusiveDesign #Accessibility #DesignLeadership #CoCreation #DisabilityInclusion #UXDesign #ProductDesign

"We stopped talking about return to office and started talking about reattaching." — Ryan Anderson, MillerKnoll Stress and burnout continue to grow and building engagement at work has taken a distant back seat to the continued drive for efficiency. Recent Upwork research reveals a troubling trend around AI: heavy users are becoming emotionally disconnected from their teams -- they actually trust AI more than their colleagues. What if, instead, we took some of that time back and invested in relationships? As Ryan put it "looking at AI as a way of reinvesting time savings in more relational human activities." The solution isn't just getting bodies in seats. It's designing spaces that strengthen human relationships. His team at MillerKnoll has identified what works in "relationship-based design": 🏢 Cafes with intention: Different table heights and seating arrangements that give people "permission to go meet someone new"—from quick corridor intercepts to intimate booth conversations. 📺 Meeting spaces for equity: Moving away from "Death Star-like" conference rooms to inclusive spaces where everyone has clear sight lines, whether remote or in-person. 🚪 Private offices reimagined: Designs that invite people in rather than create power distance—even executive offices can build relationships if you're intentional. Anderson's insight: successful workplace design is "50% space, 50% engagement." If people understand that a space is designed to help them connect and learn from each other, they'll actually use it that way. 👉 Read on for more in-depth #workplace design research: https://lnkd.in/d6fDvugg How are you designing your workplace to strengthen relationships, not just support tasks?

Claude becomes much better when it knows how you work. Most people keep repeating the same instructions every time: → “Write in this tone” → “Don’t add filler” → “Keep it short” → “Don’t change the whole thing” → “Ask before making big edits” → “Use this project context” That’s exactly where CLAUDE.md helps. It works like a personal instruction file for Claude. You can add your role, writing style, audience, formatting rules, project details, editing preferences, and permission boundaries in one place. So instead of correcting Claude again and again, you give it a reusable operating manual. A good CLAUDE.md can help you: → Remove unnecessary filler → Keep responses matched to the task → Make Claude honest when unsure → Protect your original work from unwanted edits → Keep outputs focused on your exact request → Add project context for better, less generic answers → Stop Claude from taking actions without permission The biggest benefit? Claude starts working more like your assistant instead of a generic chatbot. Small setup. Better outputs. Less repeated correction. If you use Claude regularly for writing, coding, research, strategy, or content planning, creating a CLAUDE.md file is worth it.

Walk into most corporate meeting rooms and you'll see presentation layouts. But most meetings are discussions. Why? The Presentation Room Bias. Rectangular tables facing displays. Theatre-style seating. Cameras positioned for passive viewing. Everything optimised for one person speaking to many - which represents perhaps a fifth of actual meeting activity. The Hybrid Tension. Decision-making meetings need configurations where all participants can see each other and contribute equally. But traditional round tables leave remote participants watching backs and profiles. U-shaped arrangements work better when the open end faces the camera, but this creates 'premium seats' closest to the screen. Microsoft's guitar-pick shaped tables address this: curved arrangements bringing everyone into camera view while maintaining conversational sightlines. But furniture alone doesn't solve it. * You need acoustic design supporting overlapping speech patterns. * Lighting that works for both faces and screens. * Camera positioning that doesn't create a barrier between in-room and remote participants. The Technical Cascade. * Design for the wrong meeting type and everything fails systematically. * DISCAS calculations assume viewing distances that don't account for participants needing to see faces. * Audio systems optimised for amplification struggle with natural discussion patterns. * Acoustic treatment differs: RT60 0.4-0.5s for conversation versus 0.6-0.8s for presentation. The EASE Solution. Environment comes first in GJC's EASE methodology because we must determine what behaviours the space supports - and how to balance in-room and remote needs - before specifying technology. At GJC, we audit meeting room portfolios against actual usage patterns, then redesign spaces to match how teams work. Sometimes converting three presentation rooms into one presentation space and two collaboration spaces with furniture systems that transform based on meeting type. My bi-weekly newsletter 'Industry Standard' explores room design challenges like meeting type mismatches. Subscribe via link in Comments section below. What percentage of your meeting rooms are designed for the workflows and events that actually happen in them? #MicrosoftTeamsRooms #EASEMethodology #AVTweeps #HybridMeetings #AVUserGroup #LTSMG #Schoms #AVIXA #AVMag #InAVate #InstallationMagazine

Why we are starting to shift towards the importance of our office at trumpet 🎺 and I'll be honest I have changed my day-to-day because of it... I fell into the "comfortable" trap of working from home too much, especially as a founder, but the last few months I've personally turned this on its head and been in the office way more than I'm not...and I've been loving it. There is magic in a team working shoulder to shoulder. For an early‑stage company those collisions often beat any tool or process. But I get it...working from home matters to plenty of great people. Talent is everywhere, life situations differ, and focus time can be better at home. Here is how we balance both without losing what makes the office special: ✅ Core collaboration days. Set days in the office for brainstorms, planning, and collective problem‑solving. Remote days stay sacred for deep work. ✅ Clear in‑person purpose. Try and encourage managers to set their own team's days in the office so there is shared purpose with everyone in rather than one team member alone with headphones on all day ✅ Live docs or chats of key decisions. No secrets in hallway chats. Outcomes go straight into Notion (etc) so remote teammates stay in the loop ✅ Office as a tool, not a rule. We treat the workspace like any other resource. Use it when it amplifies output, skip it when it does not. ✅ Focus focus focus. Quiet zones, call booths and plenty of meeting rooms that let people grab deep work on office days too ✅ Celebrate both modes. Wins are shared in person and on Slack. Culture should not depend on postcode. Why I believe the office still gives us an edge: 💡 Faster feedback loops. Questions get answered in thirty seconds, not thirty messages. 💡Stronger learning curve. Juniors overhear seniors problem‑solving and pick up skills daily. 💡Momentum you can feel. A tight room buzzing with progress keeps energy high when the grind gets real. 💡Serendipity. The best product tweaks often start as a scribble on the corner of a whiteboard or an out-loud chat 💡 Tough moments feel lighter. Celebrations and setbacks hit different when you share them face to face. 💡Shared identity. Rituals like team lunch or hackathons build a culture faster than any virtual event. An office gives a startup speed, energy, and shared context, but only if it respects flexibility and documents everything.

Claude's "Artifact" Feature Now Generally Available! 🎉 As an avid user of Claude, Anthropic's AI assistant, I'm sharing some exciting news about a feature that's transforming how we interact with AI: Artifacts But first, what are Artifacts? Artifacts are dedicated spaces within Claude where AI-generated content lives. They're like specialized windows for viewing, editing, and iterating on work you create with Claude. This can include code, diagrams, prototypes, and even interactive experiences. Why are Artifacts helpful? 🎨 Clarity: Complex content gets its own space, separate from the chat. ✏️ Easy Editing: Modify and refine AI-generated work effortlessly. 🔄 Iterative Collaboration: Build upon ideas more efficiently. 📤 Exportability: Created content is ready for use outside the chat. Artifacts are now available for all Claude.ai users across Free, Pro, and Team plans, and on iOS and Android apps! This means every team can use Claude to create high-quality work products faster than ever before. For example: 💻 Developers can make architecture diagrams from codebases 🚀 Product managers can create interactive prototypes for rapid feature testing 📊 Marketers can design campaign dashboards with performance metrics I used Claude to generate an architecture diagram for our Green Software Foundation Impact Framework. The ability to visualize and refine complex structures in a dedicated space is incredibly powerful. Here's a small snippet for reference. #AI #Anthropic #ClaudeAI #ProductivityHack #ArtificialIntelligence

You are using one Claude mode There are actually THREE. Most people use Claude like a chatbot. That's leaving 80% of its power on the table. Claude has three distinct modes: Chat, Cowork, and Code. Each is built for a different type of work. Using the wrong one is like using a screwdriver to hammer a nail. It works. But poorly. Here's how they differ, and how I use each one daily: CLAUDE CHAT → Think ↳ The conversational interface. ↳ Best for brainstorming, exploring frameworks, drafting content, researching a topic from scratch, processing half-formed thoughts into something structured. ↳ Not for: Tasks that need to work with your actual files or produce finished deliverables directly. ↳ How I use it: Every new idea starts here. When I'm building a framework or exploring a content angle, Chat is where I go. My thinking partner. CLAUDE COWORK → Execute ↳ You point it at a folder on your computer, describe the outcome, and it plans and executes. ↳ Best for: Working directly with your local files. Organizing documents, synthesizing research across multiple sources, creating formatted reports. ↳ Not for: Quick one-off questions (Cowork consumes usage allocation much faster than Chat). Not for software development. Still in research preview, so expect rough edges. ↳ How I use it: I point Cowork at my content folder: "analyze this transcript for actionable" or "create this deck using this research." It reads everything, builds a plan, delivers. No copy-pasting between apps. CLAUDE CODE → Build ↳ Originally built for developers. Its agentic architecture makes it capable of far more. ↳ Best for: Software development (writing, debugging, git workflows). Also: advanced agentic workflows. Running sub-agents, orchestrating multi-step research, automating content pipelines through MCP integrations. ↳ Not for: If you've never opened a terminal, this isn't your starting point. Start with Chat. Graduate to Cowork. Come to Code when you're ready for full agent-mode. ↳ How I use it: I run Claude Code in my IDE and desktop app to orchestrate agent-driven workflows. Automated research for LinkedIn posts, newsletter production, course material development. This is what I teach in my agentic AI workshops. One thing most people don't know: All three modes live inside the Claude Desktop app. One app, three modes. Download at claude.com/download. Chat is on free plans. Cowork and Code require paid plans. The mental model: ↳ Chat = Think ↳ Cowork = Execute ↳ Code = Build Start with Chat. Move to Cowork when you need real file-level work done. Graduate to Code when you're ready to build systems that work for you while you sleep. --------- I am Priyadeep Sinha and I help you go from AI Anxiety to AI Expertise one strategy at a time Every week, I share one complete AI workflow system for leaders, consultants and knowledge workers in my newsletter Work in Beta: https://lnkd.in/gPqYEzaJ

Are you tired of jumping between different views just to align a branch, connect a pipe, or rotate a valve? MEP modeling in Revit shouldn't be this frustrating. In our latest update, we are introducing the MEP Assistance toolset—designed specifically to eliminate repetitive clicks and keep you focused on your 3D workflow! 🚀 Here is how these four lifesavers will speed up your routing: 🔄 Rotate Element: Rotate valves or accessories around their own center axes at any custom angle. The best part? You can select and rotate multiple elements simultaneously with just one click! 📐 Branch Alignment: Say goodbye to connection errors. This tool instantly aligns your branch line axis exactly perpendicular to the main line, guaranteeing a standard, flawless connection every time. 🔗 Align and Connect: Why stop at aligning? This powerful command instantly aligns two separate elements and locks their connection together in a single move. ↪️ End Elbow: Need to change direction quickly? Instantly drop an elbow at the free end of any pipe or duct, facing exactly the direction you need. Watch this quick video to see these routing hacks in action! 👇 ─────────────────────────────── 📥 The download link is placed in the comments section below. 👇 #RevitMEP #BIM #BIMAutomation #MEPDesign #RevitAPI #PARSBIM #BIMManager #RevitPlugins #PipingDesign #HVAC #ConstructionTech