Collaborative Design Tools for Teams

Imagine you saved the last slice of your favorite chocolate cake, carefully hiding it in the fridge. You remember generally where, but now you're desperately rummaging through leftovers, expired yogurt, and questionable takeout containers. Relatable? Happens with me all the time!  That's how many data visualization teams feel when trying to find those critical, but scattered, data insights hidden in the depths of their databases. Smaller but delicious datasets might seem easy to handle, but when they're super important (think sales figures or customer behavior) analysts need fast, reliable access. Traditional tools often mean slow queries, waiting on data refreshes, and the general sense that your insights are always a few steps behind. That's where Google BigQuery's BI Engine comes in. Think of it like a super-powered engine for your data. It's an in-memory analysis service that makes working with those high-value datasets lightning fast. With BI Engine, your data visualization team gets sub-second responses on queries. Dashboards feel alive – no more awkward pauses while data refreshes! Analysts can explore and experiment at the speed of thought, uncovering those crucial insights that might otherwise stay buried. BI Engine gets even smarter with strategies: 👉 Reservations: Guarantee yourself a slice of computing power, ensuring snappy performance even during peak usage times. 👉 Acceleration: Cache frequently used data for a serious speed boost. It's like your nose leading you directly to a fresh batch of cinnamon buns in the bakery, warm and full of chocolate. BI Engine isn't just about faster insights – it makes developers happier, too. It integrates seamlessly with BigQuery and popular visualization tools. Less time tinkering, more time building awesome, insight-driven experiences. Why BI Engine over other tools? 👉 Fast: Sub-second responses even on complex queries 👉 Scalable: Handles growing data and user demands like a champ 👉 Cost-effective: Pay for what you use, avoid overprovisioning We at Google help organizations make sense of their data chaos. If you're tired of feeling like a frantic squirrel with your most important insights, reach out! Let's talk about how to power up those dashboards and give your analytics the speed boost they deserve. Coming up tomorrow in our Data Kitchen: Google BigQuery Studio Follow Omkar Sawant for more such delicious insights! #dataandanalytics #dataanalytics #businessanalytics #businessintelligence #bi #datavisualization #visualizations #data #bigquery #googlecloud #google #lifeatgoogle

Atlassian has been fully distributed for almost five years. We don’t have all the answers, but we’ve learned a lot about how to keep teams thriving across time zones—and we’re applying those insights every day.  ➡️ Asynchronous work: Async tools are at the core of how we operate. Confluence is our virtual hub where we share stories, celebrate new hires, and collaborate effortlessly. We also use Loom to share videos and give feedback on our own time—avoiding those dreaded “this could have been an email” moments. In fact, we’ve saved nearly half a million meetings using Loom! ➡️ Designing workdays: We’ve learned to structure workdays for focus, collaboration, and meetings (only when absolutely necessary). Teams work across no more than two time zones, ensuring at least four hours of overlap to get things done together. ➡️ Intentional connection: Data shows that real connection happens when teams meet regularly—not sporadically in an office. We provide Intentional Togetherness Gatherings (ITGs), curated experiences, and focused in-person time to collaborate. ➡️ Adapting for different needs: It’s not one-size-fits-all. For example, new hires and grads often benefit from more frequent in-person meetups, so we make sure to offer opportunities for them to connect early on. https://lnkd.in/g2sSbe3v

Best LLM-based Open-Source tool for Data Visualization, non-tech friendly CanvasXpress is a JavaScript library with built-in LLM and copilot features. This means users can chat with the LLM directly, with no code needed. It also works from visualizations in a web page, R, or Python. It’s funny how I came across this tool first and only later realized it was built by someone I know—Isaac Neuhaus. I called Isaac, of course: This tool was originally built internally for the company he works for and designed to analyze genomics and research data, which requires the tool to meet high-level reliability and accuracy. ➡️Link https://lnkd.in/gk5y_h7W As an open-source tool, it's very powerful and worth exploring. Here are some of its features that stand out the most to me: 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐜 𝐆𝐫𝐚𝐩𝐡 𝐋𝐢𝐧𝐤𝐢𝐧𝐠: Visualizations on the same page are automatically connected. Selecting data points in one graph highlights them in other graphs. No extra code is needed. 𝐏𝐨𝐰𝐞𝐫𝐟𝐮𝐥 𝐓𝐨𝐨𝐥𝐬 𝐟𝐨𝐫 𝐂𝐮𝐬𝐭𝐨𝐦𝐢𝐳𝐚𝐭𝐢𝐨𝐧: - Filtering data like in Spotfire. - An interactive data table for exploring datasets. - A detailed customizer designed for end users. 𝐀𝐝𝐯𝐚𝐧𝐜𝐞𝐝 𝐀𝐮𝐝𝐢𝐭 𝐓𝐫𝐚𝐢𝐥: Tracks every customization and keeps a detailed record. (This feature stands out compared to other open-source tools that I've tried.) ➡️Explore it here: https://lnkd.in/gk5y_h7W Isaac's team has also published this tool in a peer-reviewed journal and is working on publishing its LLM capabilities. #datascience #datavisualization #programming #datanalysis #opensource

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?

Building a real time Dashboard with Data Engineering skills. Ever wondered how those mesmerizing real-time dashboards come to life? Buckle up, data enthusiasts, because we're diving deep into the engineering magic behind them! 🪄 📌The journey of building a real-time dashboard, from data acquisition to visualization. The tools that make it tick, like: ✅Data pipelines: Python and Airflow orchestrate the smooth flow of data from various sources. ️ ✅Streaming technologies: Apache Kafka ensures real-time updates, keeping your dashboard always fresh. ⚡ ✅Visualization libraries: D3.js and Plotly paint the data into insightful charts and graphs. 🔖But it's not just about tools! We'll also explore the thought process behind: 👉Defining key metrics: What data truly tells the story you want to convey? 👉Designing for clarity: How to present information effectively and avoid visual overload? 👉Ensuring performance: Keeping the dashboard snappy even with constant data updates. ⚡️ Share your favorite real-time dashboards and why they rock! #dataengineering #dataanalytics #datavisualization #kafka #data

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!

𝗧𝗵𝗲 𝗞𝗲𝘆 𝘁𝗼 𝗘𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 𝗧𝗲𝗮𝗺 𝗖𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻 When was the last time you really got to know someone on your team? Not just their job title or their role, but their skills, their passions, and what makes them tick? If you’re like most of us, it’s easy to get caught up in the day-to-day tasks and forget that the people we work with are more than just colleagues; they’re individuals with unique strengths that can add incredible value to the team. Whenever I’m asked to lead a training or workshop on team collaboration, I make it my mission to ensure it’s not just another lecture. Let’s face it: no one wants to sit through a one-sided session where they’re just being talked at. Instead, I focus on making it interactive, engaging, and, most importantly, meaningful. I use tools like Slido to encourage real-time participation and embed videos that tell powerful stories. One of my favorite videos to share is this clip from 𝗧𝗲𝗱 𝗟𝗮𝘀𝘀𝗼 where he talks about the importance of 𝗯𝗲𝗶𝗻𝗴 𝗰𝘂𝗿𝗶𝗼𝘂𝘀, 𝗻𝗼𝘁 𝗷𝘂𝗱𝗴𝗺𝗲𝗻𝘁𝗮𝗹. It’s a simple yet profound message that resonates deeply with teams. Here’s why curiosity matters: when you approach your team members with curiosity instead of judgment, you open the door to understanding. You start asking questions that activate empathy and help you see the value each person brings to the table. For example, have you ever asked a colleague about their hidden talents or skills? These conversations not only build stronger connections but also help align individual strengths with team objectives. As a leader, I know you want to win. But here’s the thing: winning isn’t just about hitting targets or meeting deadlines. It’s about building a team that knows how to collaborate effectively, a team that trusts each other, and a team that feels valued. When your team members feel seen and heard, they’re more likely to bring their best selves to work. And that’s when the magic happens. So, how can you start fostering this kind of collaboration in your team? Here are a few actionable steps: 1. 𝗔𝘀𝗸 𝗯𝗲𝘁𝘁𝗲𝗿 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀. Don’t just focus on tasks; ask your team about their ideas, challenges, and goals. 2. 𝗘𝗻𝗰𝗼𝘂𝗿𝗮𝗴𝗲 𝗰𝘂𝗿𝗶𝗼𝘀𝗶𝘁𝘆. Build a culture where it’s safe to ask questions and explore new ideas. 3. 𝗖𝗲𝗹𝗲𝗯𝗿𝗮𝘁𝗲 𝘀𝘁𝗿𝗲𝗻𝗴𝘁𝗵𝘀. Recognize and highlight the unique skills each team member brings. Remember, effective collaboration isn’t just a benefit for the team—it’s a win for you as a leader and for the organization as a whole. When you’re looking for ways to inspire and activate your team to embrace effective collaboration, send me a DM. Together, we can create a culture of collaboration that drives success. Be curious, not judgmental. Let’s start the conversation today. #effectivecollaboration #psychologicalsafety #leadership #inclusion #culturalintelligence

Embed your vision in every layer of your studio's culture: 1. start each new project with a purpose, not just tasks. → give context on the WHY 2. create a studio zine instead of a brand guide → adapt it regularly to ensure this "living doc" encapsulates your ethos 3. hold quarterly vision sessions → let each team member bring an object/track/font that reminds them of the studio's identity 4. give vision-inspired context on creative choices instead of stressed-out "add another color here" → make sure you give empowering guidance instead of to-do's 5. emphasize studio passion projects, where you collectively create and give each team member ownership → prioritize times of exploration next to client projects Everything you and your team do should relate to your vision. Less directing, more co-creating.

Building High-Performance Remote Engineering Teams is not just about video calls.... I’ve worked with teams across the UK, Europe, and the US, and one thing is clear: remote work isn’t inherently slower. But a lot of engineering teams fail because they try to run distributed teams like co-located ones. Here’s what really makes a remote engineering team high-performing: 1️⃣ Communication by Design, Not by Chance Async-first: Chat isn’t enough. Document decisions, architectural diagrams, and API contracts in a place everyone can access. Structured updates: Daily standups are optional; status tracking through PR reviews, automated CI pipelines, and project boards is mandatory. 2️⃣ Ownership & Clear Boundaries Each engineer owns services, APIs, or modules end-to-end. Service contracts are explicit. Teams don’t block each other because ownership is clear and dependencies are well-documented. 3️⃣ CI/CD Is Non-Negotiable Remote teams must trust that pushing code won’t break production. Automated testing, linting, and deployment pipelines reduce friction and async bottlenecks. Feature flags and incremental rollouts are your best friend. 4️⃣ Knowledge Visibility Remote teams fail when knowledge lives in heads. Maintain internal wikis, architecture maps, and runbooks. Code reviews aren’t just for QA—they’re the primary async learning tool. 5️⃣ Metrics That Actually Matter Velocity in story points? Fine. But measure deploy frequency, mean time to recovery, bug escape rate, and codebase health metrics. These metrics highlight systemic issues instead of punishing individuals. 6️⃣ Tech Stack Choices Matter Prefer tools that support async collaboration: GitOps, Slack with integrated threads, Jira/Trello boards, distributed logging, observability dashboards. Avoid systems that require constant synchronous attention or centralised knowledge bottlenecks. 7️⃣ Culture Is Explicit, Not Implicit High-performing remote teams share principles in writing: “We merge only green builds,” “We document before we ship,” “We pair when ownership overlaps.” Bottom line: Remote engineering success is built on process, ownership, tooling, and visibility, not on heroic effort or long hours. If your team is still treating async work like a co-located office, you’re leaving productivity and sanity on the table.