I've written before about the importance of keeping work discussions in public forums: Slack channels, JIRA tickets, shared docs, anywhere that's searchable and accessible. If it's about work, other people probably need to know about it. I've recommended that teams target 60-80% of their messages in public channels to preserve institutional knowledge and make information searchable for future team members.

With AI tools becoming ubiquitous, this practice has transformed from best practice to competitive necessity.

Time management lives alongside prioritization and communication as the foundational skills for being an effective team leader. Team leads (alongside everyone else in most organizations) have more work than they can handle, so what work should they do and when? The key to these decisions is understanding the three levels of time management.

Slack Analytics are a powerful tool for understanding the way your company communicates. How and where your team chats is a pillar of your overall team communication structure.

Your product will reflect the positives and negatives of how your company communicates. In this article, you’ll learn how to analyze the single most critical Slack metric and take action to improve how your company communicates.

Busy, busy, busy.

In any company (small companies especially), it’s easy for leaders to get busy. Rushing between planning meetings, standups, retros, and one-on-ones, then trying to squeeze in some dev work as well. The work adds up quickly and you can barely catch your breath.

So with all this work, how do you know that you’re making progress? What if you’re just running in place? Let’s take a step back and evaluate the difference between doing the right work and just good work.

I like to joke that every problem, at its core, is a communication problem.

It’s true more often than not, mainly when the problem involves well-meaning individuals.