Inspiration

Complexity shouldn’t be a barrier to clarity. For enterprise architects at global leaders like Devoteam and major financial institutions, the challenge is often the same: fragmented tools and siloed data obscure the "big picture." 🖌By moving to a centralized, visual repository, these teams are replacing weeks of manual documentation with real-time, data-backed blueprints. This single source of truth aligns technical infrastructure with business goals, ensuring every stakeholder is in sync from day one.And the results are measurable:One global athletic brand reduced its ERD creation time by 75%. A top bank reclaimed 80 hours of meeting time through asynchronous collaboration.Whether you are using AI to generate diagrams or data linking to refresh architectures in seconds, the right visual workspace doesn't just document workflows—it accelerates them. 🏎From a 600x increase in data update speeds to saving $500,000 annually per project team, the impact of streamlining your visual stack i

I just ran into this question internally at my company. I do a lot of very large, multi-app workflow diagrams as part of creating tech designs.The only sensible solution I’ve come up with is to do overview diagrams first that fuzz out a lot of the details, and then separate diagrams that give details on a particular area or sub-flow. In the most complicated cases (like the one I’m working on now...) I’ll zoom in “part way” to show more details but still fuzz some of it out, before finally doing the most details level of particular elements.I think Lucid supports internal links between tabs, but I haven’t started using it yet. I’m hoping to find that there’s a robust feature set that makes it easy to “feel” like you’re navigating a single, very complex “picture” of the design.

Hey community 👋 We've heard a great story from SNP Group, a global software team with product folks spread across multiple time zones and products. They were dealing with something a lot of product teams recognize:Roadmaps living in scattered places, Prioritization feeling more subjective than strategic, Limited visibility into customer feedback, Teams unintentionally working in silos. After working with a dedicated product management platform, they ended up with a single source of truth where everyone from cross-functional teams to customers and partners could see what’s happening, share feedback, and even contribute ideas. A few highlights that stood out to me:      → Shared visibility: Everyone can see the same roadmaps and priorities, which helped them break down silos.      → Feedback from more voices: They opened up channels for internal teams and external stakeholders to influence               what gets built next.      → More democratic prioritization: Instead of “the loudest

Hello, Lucid Community! 👋🏼I’m Emma, and I work in the marketing team at airfocus by Lucid. We’re happy to be here, sharing content with you that we hope you’ll find valuable. My team and I create content for product managers: things like how to improve stakeholder management, create visibility, make more data-driven product decisions, or reduce backlogs.But it's not all serious. Here's a little video about stakeholder management we made last year… I'm pretty sure it'll resonate beyond product leaders…Let me know if you think we missed one in the comments! EmmaSr. Content Manager, airfocus by Lucid

Hi – I design diagrams for Salesforce’s documentation. We have put a lot of effort into coming up with a branded style that includes using our products’ defined colors, clean organization and focused grid structure. Trying to visually simplify what can be very complex topics, while also making them look nice. I am not seeing any posts in these forums that specifically relate to the graphic design/information design aspect of using Lucidchart. There must be others out there who are doing similar things though – and if any of you happen to see this post, I’d love to have a thread here that shared some Lucidchart design inspo! (And perhaps there are forums elsewhere that share those types of things?) Here are a few diagrams I’ve done for our documentation, to get the ball rolling:  

I’m excited to share Lucid’s new business transformation framework, developed by Jeff Rosenbaugh, Sr. Director of Professional Services at Lucid ​(@Grizz).Whether you’re preparing for AI transformation, navigating an acquisition, or any other transformation, this framework will help you:Assess the current state of your business and market Define a target operating model and plan for getting there Design pilot programs and scale what works across the businessUnlike many existing frameworks available, Lucid’s business transformation framework doesn’t just tell you what needs to be done—it shows you how to put those recommendations into action with 15+ templates and tips (including new templates for aligning on a strategic vision, tracking pilot program results, and more).👉 Get the full guide + templates here: https://lucid.co/blog/business-transformation-framework Lucid’s business transformation framework  Let us know in the comments below if you plan to try the new framework and templa

Hi everyone,Following up on this month's theme of kicking off the year with strategic alignment, I'm jumping in to offer a tip from the product team here at airfocus. We know that sometimes the hardest part of OKRs is just getting the structure set up.To help you hit the ground running, I wanted to share our ready-to-use Objectives and Key Results template. It is pre-configured to help you instantly map out your goals and connect them directly to your product roadmap, saving you the setup time so you can focus on the "what" and the "why."🚀 Get started with the template here: Objectives and Key Results TemplateTo access and edit the OKR template:In the link above, select 'Get this template' and type in your email. Download the template as a PDF or Google Slides. If you select Google Slides, you'll need to select 'Make a copy' on the next screen. From here, you can adjust this template to fit the needs and goals of your team. You can add or remove rows or make modifications to add any m

Hi everyone,I’ve recently started using Lucidchart to map out a large cross-team workflow, and the diagram is getting bigger than expected. I’m trying to keep everything readable, but once multiple layers and decision paths are added, it starts feeling cluttered.For those experienced with large diagrams: Do you prefer containers or nested pages for organizing major sections? How do you maintain clarity when multiple teams need to collaborate and edit the same diagram? Any Lucid best practices for scaling a diagram without losing structure? Additionally, I’m upgrading my home setup and researching the best pc gaming computer that can handle heavy design work, multitasking, and occasional gaming. If anyone here uses Lucid on a high-performance machine, your hardware suggestions would be appreciated.

Welcome to 2026! 🎉 We hope you all enjoyed the break, and you're ready to take this year on…We spent some time reflecting on what's coming this year, and have some interesting predictions for you.If 2025 had a soundtrack, it would have been a loop of AI jargon. Agentic workforce. LLM-powered. Vibe coding. Product sense.
It was everywhere — in every deck, keynote, strategy doc, and investor update.But inside actual product organizations, the vibe was very different.Teams on the ground, the ones responsible for decisions (not slides), discovered something uncomfortable: Most companies were wildly unprepared for the AI they were racing to implement.The AI hype machine ran into operational reality. And product leaders learned the hard way that buzzwords don’t build winning products. Systems do. We spoke to:Chris Butler, Director of Product Operations at GitHubLauren Kearney, Director of Health & Platform at TwitchCommentary from Malte Scholz, Head of Product and co-founder of airfocus

Hey everyone! Patrick here. As a solutions consultant, I often see engineering teams hitting a velocity ceiling. Not because of the code itself, but because of the massive overhead in mapping processes and aligning stakeholders. While many engineers are already using AI to support coding activities, I see an untapped opportunity to automate the heavy lifting across the development lifecycle. I recently sat down to share my thoughts on how Lucid AI accelerates the engineer’s workflow. Here are two key highlights:Diagram generation: Instead of wrestling with a blank canvas, you can instantly generate ERDs, sequence diagrams, or class diagrams from unstructured requirements, allowing you to jump straight into the technical iteration that actually moves the needle. Design partner: One of the coolest ways I’ve seen teams use Lucid AI is to bridge the gap between complex architectures and non-technical stakeholders. You can use AI summarization to turn a dense system diagram into a high-leve

Thank you to those who attended our “Hands-on workshop: AI diagramming in Lucid” webinar! We got a lot of great questions during the session. Here’s a roundup of the most asked questions (and the answers) about diagramming with Lucid AI. Does Lucid use customer data to train AI models / LLMs?No. Using Lucid’s AI capabilities doesn’t result in customer data being used to train any generative AI models available to third parties. Lucid stores anonymized and redacted prompts and responses for its own internal error handling and analysis, ensuring there is no direct connection to individual Lucid users or documents. Both Lucid and Microsoft adhere to stringent policies that segregate user data from model training processes, ensuring customer data remains a standalone entity used solely for its intended purpose and maintaining a high standard of user privacy and data confidentiality. Learn more. How do I use Lucid AI to create swimlanes in my diagram?We recently released swimlane creation w

Every project has a story, but the most successful teams take the time to uncover valuable learnings, no matter if the project was considered a “win”. I recently compiled our popular retrospective templates designed to help you uncover valuable insights for every project. From quick pulses to deep dives, these boards help you bypass the awkward silence and get straight to the questions that drive alignment. Here are a few that I’ve highlighted:For efficiency - Start, stop, continueFor agile teams - 4L’s retrospective For a creativity spark - Go-kart retrospectiveBe sure to read the full article to explore more dynamic retrospective templates. Which one are you most excited to try? 

Happy New Year!As we settle into January, many of us are focused on one big thing: setting the stage for a successful year ahead. That often means defining our "North Star" and ensuring our teams are aligned on how to get there.If you are planning your Objectives and Key Results (OKRs) for the year, you know that the biggest challenge isn't just setting them, it's keeping them visible and connected to the actual work your team does every day.I wanted to share a quick overview of how airfocus is designed to bridge that gap between high-level strategy and daily execution:Create a Unified Ecosystem: Say goodbye to disconnected spreadsheets. airfocus allows you to manage your OKRs in the same environment as your product artifacts, roadmaps, and workflows. This ensures your goals aren't just a slide deck we visit once a quarter, but a living part of your product process. Link Work to Strategy: You can directly link initiatives, epics, and tasks to specific Key Results. This helps every team

The key to generating effective, accurate diagrams with AI isn’t learning how to prompt as a new skill. The key is providing AI with enough clear context to get the results you want. Birch Eve, group product manager of AI at Lucid, and I will be showing how to generate different types of diagrams with Lucid AI on an upcoming webinar.  We’ll be talking about flowcharts, swimlanes, ERDs, architecture diagrams, and more.  If you’re looking to spend less time building out and iterating on diagrams, this webinar is for you!  Hands-on workshop for AI diagramming in LucidJanuary 15, 2026 at 1 p.m. ET / 11 a.m. MT 👉Register hereNote: Lucid admins have the ability to turn off Lucid AI. If you do not have access to Lucid AI features, please check with your admin.

Hey all,I’m picking up and it’s easy to feel overwhelmed. How do you stay productive while learning something new? Any tips or habits that actually work?

Hi everyone!I am excited to be writing my first post here in the Lucid Community. My name is Denia, and I'm the Director of Customer Success at airfocus. At airfocus, we are all about giving product teams a modern, modular home for product management. Our mission is to help teams manage strategy, understand user needs, prioritize, and align their roadmaps.Now that we are part of Lucid, our focus is on helping our customers bring together Lucid’s visual collaboration and airfocus’s product management solution, a game-changing combo for product teams everywhere.What to Expect in Future PostsMy team is excited to share actionable insights that will help you build better products, and we will be posting content such as prioritization framework tips, going from whiteboard to roadmap with Lucidspark and airfocus, gaining stakeholder alignment, and more.Let’s Connect!I would love to learn how you are currently using Lucid in your product workflows. Here is a question to kick things off:What i

Ever feel like you’re playing a game of hide-and-seek with your project documentation? You waste hours digging through folders and chasing down stakeholders for access, plummeting your momentum. According to a recent study commissioned by Lucid, the top barrier to following processes is simply not knowing where to find documentation.Insert: process repository. Think of a process repository as your organization’s single source of truth, providing a centralized home for every workflow and strategy. Building one can initially be a heavy lift, but it has a big payout. Process repositories connect knowledge silos and ensure that when experts move on, their insights stay. Here is a high-level overview of how to build a repository within your organization that actually sticks:Organize and evaluate: Mirror your existing department structure or value streams so the navigation feels intuitive, then break broad processes into manageable subprocesses. Standardize for consistency: Use shared templa

Picture this: A project kicks off with perfect energy, only for a mid-sprint change request to derail your velocity and scramble your dependencies. Sound familiar? Engineering is complex enough without the added friction of misalignment, outdated documentation, and siloed coordination. When teams rely on dense text or tribal knowledge, critical context falls through the cracks, turning minor shifts into major roadblocks. 😵‍💫To maintain momentum, engineering teams need a living blueprint. In Lucid, you can transform static docs to a single source of truth. Features like data linking, embedded links, and the Cloud Accelerator automate your documentation, while team hubs and team spaces ensure that cross-functional stakeholders and developers are looking at the same map.Whether you’re mapping intricate processes or navigating a complex project kickoff, these Lucid features will help you bridge the gap between planning and execution. Stop losing time to miscommunication and start buildin

Thank you for joining us for our webinar, “How Lucid supports enterprise architects”! (If you didn’t have the chance to join, you can access the webinar on demand here.) Check out these additional resources: Features mentioned during the webinarLucid Ardoq integration The Ardoq + Lucid integration story Generate a diagram with Lucid AI ERD import Cloud Accelerator Process Accelerator SAP LeanIX integrationCase studies Devoteam Customer examples: How EAs use LucidAdditional resources for enterprise architectsLucid solutions for enterprise architects How to develop an enterprise architecture repositoryLeave any follow-up questions you have from the webinar in the comments below so that a Lucid team member can help answer them.

It’s a fact: visuals are the powerhouse of effective communication. And now, with AI, we can generate them in seconds! At Lucid, we are all about helping teams collaborate visually and efficiently, so we know the massive time-saver AI can be for this.Specifically, with Lucid AI, teams can rapidly create complex visuals, saving countless hours. That speed is incredible for prototyping or transforming a text outline into a diagram. But how do you know if AI is the best route for what you’re trying to create?I broke this down in a recent blog post. Generally, you’d use AI to quickly sketch an idea or get your initial thoughts out.  Lean on a template when you need a standardized, collaborative structure. Our templates strike the perfect balance, providing a proven structure for standard processes and team collaboration. And, honestly, sometimes a project is just too unique and specific, and that’s when you build from scratch on a blank canvas. The good news is, you can do all of that in L

Documenting your enterprise architecture is no easy feat. But with a solution like Lucid, it becomes much more efficient. In our upcoming webinar, we’re talking about how Lucid, and its integration with Ardoq, can help make your enterprise architecture documentation more visual and collaborative. During the webinar, we will cover documenting and standardizing architecture, comparing future states, creating a single source of truth, and streamlining stakeholder approval. See you there! How Lucid supports enterprise architectsDecember 4, 2025 at 11 a.m. MT (1 p.m. ET) 👉 Register here

If you’ve ever tried to document a process, then you know that it can sometimes be a messy operation. But good documentation is the key to smooth operations and mutual alignment within a team or organization.We recently posted an article about our top eight Lucid features to make business process documentation a breeze.Here’s a sneak peek:Actions: Quickly perform certain actions with shapes on your board. Conditional Formatting: Set up specific rules to automatically highlight elements in your documentation that need your attention. Dynamic shapes: Bring your data to life to visually represent statistics or percentages, making your documentation more engaging. Layers: Organize your documentation with Layers to show different phases or details without overwhelming viewers. Be sure to read the full article to explore all the ways to improve business process documentation. Have you tried any of these features? Let me know in the comments below!