# Using Slack to promote ‘Developer Democracy’

**Author**Ivo Jansch

**Date**17 February 2016

We’ve been using [Slack](http://www.slack.com/) for ages now, and we can no longer imagine what it was like to do projects before tools such as Slack existed. (We used to use Skype group chats; in hindsight that was so crappy, but there wasn’t much else — well there was IRC, but it somehow never caught on in our team).

Since slack added ‘reactions’ (the ability to add any emoticon to any message) we’ve seen an interesting trend emerge in our teams: ‘developer democracy’:

It’s annoyingly simple; you have the options, the discussions and the arguments all nicely tied together, including the actual results. Typically this leads to small incremental changes to our processes, and we try to document these on Confluence as we go along, including a link to the discussion on Slack, in case anyone wants to read back on how we arrived to a certain conclusion.

Works quite well for us so far.

(If you have an opinion on the above feature branch vote: we have [job openings](https://werkenbijdawn.tech/l/en/))

Photo credit: [pjohnkeane](https://www.flickr.com/photos/johnkeane/5695179697/) ([CC BY-SA](http://creativecommons.org/licenses/by-sa/2.0/))

[Back to overview](/en/events-publications)  Link copied to clipboard

### Build better teams, not just better software

Talk to Dawn Technology about transparent collaboration and scalable development processes.

<a id="subscribe"></a>## Curious about our latest updates?

Stay up-to-date in the digital landscape with our newsletter. Enrol and get the latest updates in your mail