🎬 Slack School | Let's talk huddles bit.ly/4u1DHeL Huddles in Slack are like a virtual tap on the shoulder when you just need to talk things out face-to-face with your teammate or...with your cat 😻 Mike Reynolds demos how to jump into a quick video chat in Slack, use AI take your notes during the call notes, and even doodle on shared screens to solve problems in real-time. Plus, a chance to win your own Slack huddles record! 🎶 Class dismissed! 🔔 📚 Absent from class? Watch all Slack School episodes here: sforce.co/4ktLPkx

You answer the same SOP question 4 times a week. Different person. Same answer. Different format every time. Once for Slack. Once for email. Once when someone asks in a meeting. You're a human FAQ, but there's a 3-minute fix covered in this clip from last month's Copilot Deep Dive. 3 minutes of setup gives you hours back over the next quarter. The work doesn't go away, it just stops eating into the work that actually matters. This was one of 5 workflows from the full session. Full recording is in the comments 👇

This is a subtle but important shift. Slack You’re not just redesigning a homepage… You’re redefining where attention lives inside work. And that’s the real battleground. Because productivity tools don’t fail from lack of features They fail from fragmented attention loops. If this new experience can: Reduce context-switching Shorten decision cycles And surface “what matters now” faster… That’s not a UI update. That’s a behavioral upgrade. Most teams will underestimate this. #uiuxdesign #slack #productivity #aiinmarketing #automation

𝗙𝗔𝗜𝗟𝗨𝗥𝗘 𝗧𝗢 𝗙𝗢𝗥𝗧𝗨𝗡𝗘 They sold only 600 copies in the first year. The game looked destined for the scrap heap. Refund requests piled up. Nobody believed in Slack. Founders felt defeated. They addressed flaws in their product. They focused on user feedback. They turned it into a communication tool. The pivot paid off. Slack gained 8 million users in just two years. Today, Slack is a staple in workplaces worldwide. 💡 𝗧𝗵𝗲 𝗚𝘆𝗮𝗮𝗻𝗦𝗲𝘁𝘂 𝗜𝗻𝘀𝗶𝗴𝗵𝘁: Failure often precedes success when you adapt and learn. What lessons can you extract from your own setbacks? Optional learning community: : https://lnkd.in/gDi-Br8X

Got a little reminder of how far we’ve come last week when Slack released an update just for us. It’s kind of embarrassing, but until a week ago when using Chaser to create a task in Slack, any hyperlinks in your task would automatically get removed. Full typed-out URLs worked fine, but not hyperlinks. It caused a ton of confusion/frustration but there was nothing we could do because it was happening on Slack’s side, not ours. Well, we’ve grown a lot over the last few years and now Slack is replying to our emails. Last week they pushed out a change specifically for us. Chaser users, your hyperlinks are safe now. Thank you Slack!

𝗟𝗜𝗙𝗘 𝗢𝗙 𝗔 𝗦𝗟𝗔𝗖𝗞 They lost their core product. They built a game in a week. They aimed for a fun distraction during a conference. It failed to attract users. They faced a crisis. They pivoted back to their original product. They integrated communication tools into workflows. Today Slack supports millions of users. They thrived because they listened and adapted. 💡 𝗧𝗵𝗲 𝗚𝘆𝗮𝗮𝗻𝗦𝗲𝘁𝘂 𝗜𝗻𝘀𝗶𝗴𝗵𝘁: Adaptation during failure creates pathways to success. What changes are you ready to make? Optional learning community: : https://lnkd.in/gDi-Br8X

You can now use Assist directly inside Slack. Ask questions, run workflows, trigger agents — all from the channel you’re already in. No new tools. No extra tabs. Just build once and use where your team already works.

Slack is the main way that I work my my agent team so this is a huge feature for me. For example, I have an agent in my infra channel that is connected up to Axiom (where my logs are) and my coding agents. When there an increased error rate on Assist platform the ops and coding agent together run an analysis of the issue and work on a pull request to fix whatever the issue is.

This GitHub Copilot feature that lets you create issues directly from Slack sounds genuinely useful. Imagine the time saved not having to switch contexts for every bug report or feature request that comes up in a quick chat. Pretty neat. #DevTools #Productivity

𝗟𝗢𝗦𝗜𝗡𝗚 𝗜𝗦 𝗧𝗛𝗘 𝗡𝗘𝗪 𝗪𝗜𝗡𝗡𝗜𝗡𝗚 They faced bankruptcy in 2002. More than 90 percent of their users stopped using the product. Engineers folded their arms while executives argued. They stripped the app down to its core function. They focused on seamless communication. Now, Slack has millions of users and a multi-billion dollar valuation. They turned failure into a foundation for success. 💡 𝗧𝗵𝗲 𝗚𝘆𝗮𝗮𝗻𝗦𝗲𝘁𝘂 𝗜𝗻𝘀𝗶𝗴𝗵𝘁: Simplicity often outlasts complexity in business. What will you simplify today? Optional learning community: : https://lnkd.in/gDi-Br8X