I think a CTO should have several mental models for making decisions. Minimizing wrongness is just one.
Some examples:
- Is this decision reversible?
- Does this choice allow my team to grow technically?
- Will this matter a year from now?
- Is this something I can buy instead of build?
- Is this a core competency that we should invest heavily in?
- Does this decision go against the company or your personal values?
- Is quick and dirty good enough for this?
There are several ways to orient the problem to help make a decision. But the OP is totally correct, this decisions will usually be made without all the data and with a lot of people looking at your decision.
> When problems reached him in the White House, he said, it was because they were unsolvable. He generally was being asked to choose between two bad options. “By definition, if it was an easily solvable problem, or even a modestly difficult but solvable problem, it would not reach me, because, by definition, somebody else would have solved it,” he said. “So the only decisions that came were the ones that were horrible and that didn’t have a good solution."
This should probably be a must read for any wanna be presidents and leaders who are only after the power and glory.
Which isn't to say they should be unaccountable. But these are people who make impossible choices all the time
The child comment about The President doesn't use the phrase "by definition" at all
There is a balance between empowerment and the higher-ups taking responsibility. I've been in an organization where-in the higher-ups just abdicated all responsibility and avoided making any technical decision (maybe for fear of making a wrong decision) and so the small teams had to make every decision which led to chaos and lack of direction.
Sometimes, it is the job of the architect or CTO to make those big decisions; their job is not to code, their job is to weigh the possible options and make a decision to give direction to the team.
There's a cautionary tale buried here. Many seemingly Type 2 decisions are actually Type 1 decisions in disguise. Case in point, Amazon's decision to not allow warehouse workers to have their phones when working in the warehouse has resulted in the 6+ deaths and many more injuries that we saw in the tornado last Friday. Now there's no going back, and Amazon may (and should) be held accountable. Pretty grim for a seemingly Type 2 decision.
There are multiple ways of looking at any decision: perhaps, for example, employees with cellphones were more distracted and thus more prone to accidents.
My eleven-year-old daughter has no cellphone because we don't think being connected at her age is good for her (she also seems indifferent to having one, unlike my son, who is all about being connected). We also let her walk home from school on her own, and have for a couple of years now, because we believe she should be independent. I can imagine (although I try not to) situations in which those two decisions interplay and lead to a bad outcome, but I still think they are the right decisions for her.
The "dunk" is a side effect. Amazon's decision making on this issue does a really good job of illustrating situations where you make a seemingly harmless decision that you feel you could revoke at any time, but things take a turn for the worse and regardless of your ability to revoke the decision, you can't revoke the damage it caused, the preventing of which is the whole purpose of having this system of type 1 vs type 2 in the first place. AKA the type 1 type 2 system is imperfect and can lead to miscalculations, like this. A more useful framework might be "can I prove, convincingly, that there is a 0% chance this decision will lead to irrevocable significant negative consequences, if so then it is type 2, otherwise type 1"
2 way doors aren't about making bad choices, they're about the response time and cost for when you identify that the choice was bad. You can make bad choices for 1 way and 2 way doors.
The best example I can think of for your argument is the flint water system. What looked like a 2 way door was actually a 1 way door, when the choice to switch water sources completely destroyed the pipes beyond usability, and any water flowing through the pipes would be contaminated, regardless of the source.
A 2 way door equivalent would stop being contaminated once they switched the water source back, even though people had drunk contaminated water
If they are breaking the law lets prosecute them. If there is a law you want changed vote for a legislator to back it. If you don’t like them, don’t buy from them. This isn’t complicated.
If so I hope you reconsider one day.
I am saying hijacking a comment on decision making to leverage a tragedy in order to make some thoughtless “amazon bad” claim is kinda weird.
There is no right to your phone at work. Should there be? I dunno, probably not, but if you feel there should be then vote for it.
Did Amazon do “the right thing” I dunno but that reply isn’t bringing any clarity to that discussion either.
I agree we should have moral/ethical duties. Unfortunately society has degraded to moral relativism mixed with tribal absolutism. So what that would even mean these days is fraught
And it can be really hard for someone who loves to code to realize that this is primarily their job now. And they're always going to be kind of wrong
And, if you can't figure out which is least-wrong, just make a decision, any decision. Don't become a roadblock. If the problem has already gone from junior->intermediate->senior->architect->cto it's already taken a whole lot of time and energy. It's software - you can fix almost anything (except certain security, reliability and financial controls) later if its wrong so making any decision is more important that making the optimal one.
I've definitely worked at startups where the CTO was the blocker for the longest time and we'd wait weeks on them when another senior people could have done the work immediately. Try to delegate and trust people as quickly as you can.
The nuance here is if you're making a decision that has a gross positive value, then you likely have a large number of "wrongness" choices that still result in a net positive. If you're not sure which of them to take then take any one that has a positive EROI (the ambiguity makes them all appear similar returns). Remember that EROI is marginal so even if you end up in a lossy situation _after_ the decision, so long as it's less loss than before you're net better off than you were.
If you're making a decision which all decisions seem to have a net negative EROI, then there is no opportunity at hand. Keep looking for a real opportunity.
Depending on the problem, it may be you need to experiment, research or call in an external expert. As a leader, you may need to make the call as to which approach but the execution itself should be handled by the problem owner.
Remember, as CTO, your primary responsibility is making the tech deliver the bottom line sustainably. Not impress other devs.
*there are some things the supreme court does around consistency which aren't like this.
Recently I had to implement interpolation in my game engine, before looking at that I tried laying out animations in memory and noticed a 3x speedup. So when it was time to decide I took the seemingly coward route of exporting animations in 120 FPS instead, hitting disk ×5 and RAM ×2 but saving CPU ×3.
Time will tell if this was the right choice, ie. will games render at >120FPS. The debt was moved from technical to energy saving, from complex to simple, from now to the future (since exporting in 120 FPS takes a little more time every animation that goes into the game)
I'm going to keep investing in low power because that is more guaranteed than everything else.
I heard it on a podcast, though I'm pretty sure he didn't coin the phrase.
Leadership is hard and it's hard because you're making bayesian calculations on suboptimal choices. Almost by definition.
Say a Jr. dev has a problem that they can't solve. They kick it to an intermediate.
The intermediate can't solve it so they kick it up to a senior.
The senior can see a couple of solutions, but want's to run it past the architect.
The architect takes these options, weighs them against n number of considerations + the dev roadmap and sees strengths and weaknesses to all of them.
They package those pros and cons and brings them to you, the CTO to make a decision between these sub-optimal choices.
In this kind of environment EVERY move you make is going to be a little bit wrong. You just kind of have to minimize the wrongness