I thought it'd make sense to share how we're internally using DailyBot, to build DailyBot. This will give you a better picture. 1. We run daily stand-ups 2. E

I thought it'd make sense to share how we're internally using DailyBot, to build DailyBot. This will give you a better picture. 1. We run daily stand-ups 2. Every Friday, there is a 3 questions retrospective, really good to reflect about work and priorities 3. On Monday, we run an icebreaker, the team tells stories about how the weekend went, it helps us stay connected at a human level 4. Every 2 weeks, we get a #watercooler prompt with very random questions that create discussions among the team 5. Whenever we're launching a release, we trigger the command "Coderelease" that shows a native form that the technical leads fill out. The data is posted in a #releases channel, then everyone sees what new things are being launched, we use that data as change control, and PMs use the notes to prepare product updates for users, etc. 6. When we get any idea/feedback, we register that through a form that we can trigger in chat "@dailybot customer feedback" 7. Every week, the team is paired randomly to have virtual coffees (those are optional to opt in, but nice to keep our team connected) 8. We run polls/surveys from time to time with DailyBot 9. I have built a few commands to query internal data, like product top KPIs This is how adaptable DailyBot can be.