Miro

On September 28 teams turned stalled ideas into working automations at the Miro x n8n NYC hackathon. They mapped workflows in Miro, built them in n8n, and wrote the results straight back to the board. Here are our winners! 🎉 🏆 Best Overall This team built an AI sales coach using call and Salesforce data for live and post-call coaching in Miro helping reps improve while saving managers time. Team: Matt Auster, Precious M., Gideon Chiaet, Jessica Yu Jin, Amaurys Valdez 💛 Better together: Best use of Miro x n8n Our Better together winners developed a full-stack, securely deployed app enhancing AI assistance for sales management. Team: Joshua C., Peggens Altidor, Bertrand Besson 💪 Most ambitious - The Most ambitious award went to a team that built a tool to help you hunt for an apartment in NYC finding those with hidden issues lurking. Team: Sahil Pardasani, Tanmay S.

AI gives you the floor. Your job is to raise it to the ceiling. That’s what Ralf Gehrig, Global Chief Experience Office at wongdoody tells his team. We talked to Ralf and his colleague Kim Abbott, Head of Experience Design EMEA, about where that edge actually comes from once everyone has the same AI tools - and why "human in the loop" isn't the right model for getting there. Read the full conversation, plus our new companion playbook, "Beyond the human in the loop: A guide to rebuild collaboration in the age of AI," accessible via the post: https://lnkd.in/eqHeybmx

When PRs keep coming, it gets harder to see how each change affects the system as a whole. Horea Porutiu, Senior Developer Advocate at Miro, set up a scheduled Claude task that checks for new PRs and turns the latest changes into an updated architecture diagram in Miro. The result is a visual map of what was removed, what was added, and how the proposed architecture compares to what’s already there. Each snapshot sits next to the last one, so your team can look at the proposed change in context and decide together what ships. How does your team review architecture changes today?

News travels fast down here… Try Mermaid in Miro today: https://lnkd.in/eJ8YwAPP

What if AI set up your team's product workshops, and your agents picked up every decision the team made? In this live session, Mike Mitchell of Equal Experts shows the loop his team runs in Claude Code, with discovery work kept right next to the code. Michael Luchen of Miro shows how teams who don't work directly in a repository can run the same loop. Join us! October 14 at 10am CT.

The Miro plugin in ChatGPT is now available. Start your next prompt with "@Miro" to summarize and search boards, build new ones from scratch, bring research onto the canvas, or visualize complex ideas as diagrams, tables, docs, images, and sticky notes. The thinking that happens in your individual window becomes a board your whole team can see, comment on, and build from. Get the Miro plugin in ChatGPT: https://lnkd.in/ehM9VeNb

Nobody warns you about building solo. You're the founder, the developer, and the auditor, and you're stretched too thin to be good at all three at once. Leandro B. is a solo founder building Epilog, an epilepsy tracking app he started while navigating epilepsy with his son, having to track everything by hand just to have a productive conversation with a doctor. The app is close to 1,000 users now. Leandro is moving fast, but he’s the only one checking his own work, which means he knows something’s probably slipping through. So he got the right context into one place: his GitHub repo, his legal docs, and his UX, all on one Miro canvas, with Flows running checks across all of it. Read how he built it and grab his template: https://lnkd.in/ewEKxKRz

Not another "AI is changing everything" webinar. This one's practical: how to actually spot decision latency, review fatigue, and accountability gaps before they wreck a quarter. Dom Katz, Dave Sammut, and João Rosa have all lived this and will be sharing how to approach AI acceleration. Oct 8, 11am CEST.

Matt Przegietka spent a year getting better at prompting before he worked out why: his context was scattered across a Figma file, three Slack threads, and a call transcript nobody reopened. Every prompt was a compressed summary from memory, with the model guessing at the rest. So he flipped it. Instead of starting with the prompt, he now starts with the context: dump everything on the canvas, structure it, pressure-test it, and keep the reasoning behind every decision. For your next build, try Matt's approach: https://lnkd.in/eBkbTwHk

Join Onna and Miro for a candid conversation about what governance looks like when work is visual, collaborative, and increasingly AI-assisted. You'll walk away thinking differently about: * Why visual, real-time collaboration breaks assumptions baked into most governance programs * What a meaningful audit trail looks like for content that never stops changing * How AI-generated and AI-assisted work is reshaping discovery and compliance risk * What forward-thinking legal and IT teams are doing now to prepare Register here: https://lnkd.in/eNiRRtJZ