I believe in transparency as a philosophical basis from which to run a company. The resulting trust, loyalty, buy-in and contributions of your employees more than make up for the downsides. But there are indeed some downsides. The two I’ve been most aware of are inefficiency and unnecessary anxiety. One’s a simple tradeoff; the other I believe can be addressed with education, more transparency and increased employee responsibility.
In the early stages of the company it was possible for everyone to be involved in making decisions. My philosphy of transparency worked easily with a group of 10 or so closely-knit employees. But Atomic now stands at 31 people (plus summer interns). Thirty people could in theory contribute to each decision that needs to be made and evaluate every opportunity we face. I have no doubt all 31 atoms would have something valuable and interesting to say on most issues. But there would be a lot of overlap in those contributions, lots of discussion, and lots of software not being created as a result. Full participation just doesn’t scale well. (I suppose representative democracy was invented for similar reasons.) While Atomic is no democracy, the tradeoff of efficiency and participation seems similar. Since last year we’ve been experimenting with a governance structure of a board and executive committee. I like how it’s going so far — efficient and effective. Having a board of eight helps to disseminate the issues we are discussing and multiplies the channels for employee input.
While we now have a semi-formal governance structure, one thing hasn’t changed: we still hire people for culture-fit, and part of the culture is to give a shit, or “care deeply” as one modest candidate so aptly countered. Part of giving a shit is caring about and feeling responsible for the direction of the company. After all, we expect this sort of concern and accountability when thinking about our software practices and client projects. It’s only natural that such caring individuals will take seriously and think critically about decisions made within the company.
A consequence of our transparent culture is that some ideas are exposed without context or at an early stage. Hearing about problems or initiatives early, without having full information, can easily cause caring employees a degree of stress: they don’t agree with or fully understand the decision or direction. I’ve found it’s critical to put responsibility on every atom to engage the full complexity of decisions that, through our practice of transparency, they are exposed to. Irresponsible and unacceptable behavior includes unproductive bitching in the local bar, pessimistic extrapolations on insufficient data, questioning the motives of company leadership, continuing to debate decisions which have already been made, subverting existing policies, willful oversimplification, and lack of full consideration of all aspects of a difficult issue.
But even if everyone is exposed to the full gamut of the decision, and have had ample opportunity for clarification, there still can be some deeply-rooted differences of opinion about what’s best. Some of this can be chalked up to experience. Given the gray in my beard and the ten years I’ve spent thinking about and solving business problems for Atomic, my perspective is very different than it once was, and very different from most of our employees. I find it helpful to remind myself that I started Atomic knowing very little about business, an ignorance not uncommon among technical people whose degree programs are full enough as it is. To help address this knowledge gap, I periodically offer an “Economics of AO” class. I think it helps eliminate some of the anxiety by giving everyone a shared understanding of the business foundation of the company.
Learning more about business helps, but it isn’t enough to eliminate some of the anxiety and concomitant negative behavior of being exposed to evolving issues and initiatives. For transparency to provide its maximum benefit and avoid its significant possible downsides, everyone in the company needs to take on the responsibility of engaging complex issues fully and resisting the temptation of merely criticizing from a safe distance.
- Software Product Development in a Time of Pandemic - March 16, 2020
- Eleven unquestioned assumptions of business – and why they’re wrong - March 3, 2020
- A framework to define and describe organizational culture - January 21, 2020
- Atomic Ownership, Part 6: Lessons Learned - November 26, 2019
- Atomic Ownership, Part 5: Distributions - May 1, 2019