HeatEXTEND
Prophet
So-called self-organizing companies have a corporate arm somewhere controlling the entire operation from “above”. Find them and their friends to figure out who has the real power.
What you’ll find is that the corporate arm influences, controls, and “anxiety spikes” the self-organizing arm nearly constantly. It’s not self-organizing, it’s a company with opaque managers ruled through mass anxiety and fear.
If you’re at a place like this, you must learn who the corporate managers are, who are their friends, and the cliques. They are the ones with real power and everything else is an illusion.
At self-organizing companies with bonuses, workers will watch for rivalries between other coworkers to exploit. They will team up with one dev to bring the other (disliked) dev down a notch in some way. (I’ve seen this several times.)
At self-organizing companies, coding must be done super defensively as anyone can come in and “turd up” the code you’re working on. You must design your systems for this inevitability.
Related: At places like this, you dare not depend on other systems actually working for any period of time. Copy/paste/rename the helper functions you depend on so others can’t quietly break or jankify your systems and make you look bad.
On a competitive team within a self-organizing company, avoid asking for help unless you absolutely, positively need it. Any information you receive may be purposely distorted in some way. If you do ask for help, gather consensus from multiple devs.
Related: Route around problems vs. asking for help or modifications on these teams. Once you ask for help the other dev(s) have control and may purposely send you down a blind alley.
On teams like this, it’s the Wild West. The devs aren’t working for the greater good of the company, they are working for good bonuses. This is one reason why bonuses in this type of environment are a really bad idea.
At self-organizing companies you must be very social. Early on you need to identify who is closely interacting with the corporate arm, who their friends and cliques are, and what they find valuable. If you fall outside this group’s favor be prepared for pain.
Related: You need a powerful “Sponsor” or “Baron” to back you. Figure out what they want and like. Watch or read “Hunger Games”. Once you get to this level you are almost untouchable.
At a self-organizing company you must pay attention to subtle hints from the corporate arm. They just won’t come to you and say “work on this”. Events will just happen and you need to be wise and realize that nothing happens by accident at places like this.
Your mental model should be a hierarchical corporate arm with a self-organizing layer underneath. The corporate arm will reach into and influence the self-organizing arm using various tools.
Some tools are key strategic hires forced into the system, random firings, hints placed with devs that something is valuable or interesting, exposing devs to extra resources like the ability to pay contractors, destroying resources like test labs, or bonus payouts.
You can also just reach in and grab devs and force them to a new team. (That’s why you have wheels on your desk.)
If at one of these companies you find yourself in the basement with a stapler, working alone: be prepared to be fired unless you have a strong Sponsor and are taking an approved break.
If you’re running a self-organizing company, you need to have a measure and understanding of the current average and peak Anxiety Level within the self-organizing arm. Or it blows up and talent walks.
Random firings, messing around with key resources like test labs, encouraging toxic behaviors through massive bonuses, and forcing devs to move around randomly are all anxiety increasing/morale decreasing events.
And this is why I walked away from a self-organizing company 1 week after being given options. It was just too unhealthy a workplace, and it impacted my health too much. I would say most of my coworkers where ridiculously stressed out (I learned some had to go on meds to cope).
Another type of temp strategic hire you can make is to recruit a well-known author, a famous dev, or a person with specialized skills (like an economist). Have them write gushingly about their amazing experiences at the company. Once you’re done with them quietly let them go.
And so this is a form of Developer Marketing. Hire some key person, push them to write or blog, then once you’re done with them let them go. The “pawn” won’t complain too much as their career will be enhanced by being associated with your company.
What the developer actually writes is actually consensus based mumbo-jumbo. It’s just marketing. It’ll be based off the version of reality the corporate arm wants to market to developers they haven’t recruited yet.
If you run a self-organized firm and you have turned up the anxiety levels too high, your company will become brittle and prone to mass talent flight. Wealthy competitors can come in and make offers and basically steal all your tech and devs right out from under you.
Corporatism at it's best, sounds exactly like my workplace lmfao