To all the software development teams using Kiwi Dials:
We're not exactly sure how you found us, but we're glad you did.
Turns out, a surprising number of teams using Kiwi Dials are writing software, and that had us scratching our heads. After all, why wouldn't all kinds of teams want to have a transparent, honest, and anonymous way of tracking team engagement? Why so many software development teams?
In the year or so since we launched Kiwi Dials to the public, we've noticed that the idea of openly sharing engagement scores with the entire team gives some managers the cold sweats. The worry seems to be that if the team sees some bad scores, that might cause them to feel worse, which could drive the scores down even lower.
To be clear, the truth of the matter is that seeing how your teammates feel about the quality of collaboration, communication, recognition, progress, and so on, strengthens connection and gives everyone a chance to get better. When something works, you can see it in the numbers right away. But even if you decide to take our word for it, using Kiwi Dials still takes some courage, especially if you are a manager.
But maybe, if you are a software team running agile, you're already committed to the power of collaboration and principles of self-organization. You value individual contributions and team autonomy. You are drawn to data, because understanding where you are is the first step in getting where you want to go. For these teams, Kiwi Dials is a no-brainer.
While we hope that someday, HR departments everywhere will embrace Kiwi Dials to provide critical insights to intelligent and talented managers, we're happy that we've found some kindred spirits while we wait.
Now that we've loosened our ties a bit, here's our favorite baby elephant gif.