So this is the second post about the internal workings of Codurance. While in the previous one I looked at how salary and reviews work, here I want to concentrate on something that allows me to take an active part in shaping our organisation: Initiative Circles (IC from now on).
I have always wanted to make my life and the life of my colleagues better. There is no company that will not benefit from improvements, some far more than others. At Codurance, with Initiative Circles, anyone has the opportunity to improve the lives of their co-workers, from small improvements to much more significant changes. At Codurance, through ICs, we have addressed disparate topics such as: Paid Slack, BitWarden for password keeping, the Progress Structure that is the subject of my next post, salary alignment with the local market, health insurance , Peer Review Process, The Podcasts, …
The Initiative Circles was an idea introduced by Sandro and Mash, our co-founders, with the vision to empower everyone to evolve the organisation according to the business and organisational needs. Their aim is to create a truly learning organisation.
IC are relatively simple to set up: someone has an itch to scratch, and floats the idea. If two other people like the idea and want to collaborate then the IC can proceed. “Anything” can be tackled. You seek advice from people who will be impacted, reach a resolution, communicate to people, and go ahead and implement it. Rather than seeking complete consensus we work on trust that if enough people agree with an idea then the rest will trust them to have their best interest at heart. If people don’t like the results of an IC then they can create another IC and change its outcome.
And that is basically it. Simple, isn’t it?
There is a bit more, of course. Which I will be describing now.
Communication (something that we need to revisit as Codurance grows) is important. We use Slack heavily, so there is a channel (conveniently called
#initiative-circles) where any new initiative appears when we add it on our tracker (currently we are using Taiga). Also, the person that wants the IC to happen usually links in
#general, as not everyone is on the IC channel. We usually also create a channel specific for an IC once it has started. One of the benefits of this additional channel is that people that don’t want to have an active participation still can follow how the IC evolves. Finally, once the IC has been concluded, we let the rest of the company know. At the moment the rules says that you need to do it during catch-ups or openspaces (how cool is to have your own day long unconference every two months?). But that doesn’t scale, so we are going to be looking at improving that … through an IC.
The main way to move ICs forward are meetings. And a few considerations here: because we are a consultancy, sometimes it is difficult to find the time as you are with the client. But back to the theme of responsible adults, you can join these meetings, because they are useful for Codurance. So as long as you don’t spend all your time on them, you are free to join. Secondly, all have an equal voice here. You are the ones that decided to join and actively participate on the IC. There is no person with the higher rank on an IC. Although it can be possible that one person is designated to make sure the thing moves forward and reaches a conclusion.
And the conclusion is the last bit that I want to talk about. Sometimes an IC fails to take off the ground, and never starts. That’s fine. It wasn’t an itch worth scratching. Sometimes an IC fizzles out and never reaches a conclusion. That’s fine. Maybe the priority of the IC wasn’t that big, or maybe the effort was too much for the expected outcome. And sometimes the IC reaches a conclusion with a specific outcome. Then it gets implemented. The people actively taking part in the IC need to be in agreement. That is one of the two conditions that applies to all IC conclusions. It could be possible that people from outside the IC don’t agree, but they have had the opportunity to take part. Also it is the responsibility of the IC members to seek advice from people impacted but they don’t need to follow everyone’s advice. The other condition is that you have done your due diligence, especially if there is a cost to it. You could have a preconceived idea about the conclusion, but is important to see as many alternatives as possible, in case you find a better outcome.
And I think I mislead you talking about the previous paragraph being the last thing to talk about. Like with so many things, it requires that people participate. But, unlike in any other company I have ever worked, you can be an agent of change and improvement. Before I could only complain about the situation, now I can be the change. If I don’t, well, can’t complain, can I?
And that is why I love ICs :-)
Although he started early (with QuickBasic and Turbo Pascal), took him a while to center into the developer way of living. Nonetheless, he has more than 10 years experience as software developer at different levels. His main experience is around C# and .Net, but has a keen interest in other languages, especially around functional programming.
In his experience two maxims have been revealed, Simple is Beautiful and Make Everyone's Life Easy. Because of them, his personal goal is to improve the experience of fellow developers (which always translates to happy customers)
Outside of work, you can find him either playing online or dancing away, or just improving his craft (that is the way of the developer).All author posts
Software is our passion.
We are software craftspeople. We build well-crafted software for our clients, we help developers to get better at their craft through training, coaching and mentoring, and we help companies get better at delivering software.