In a former workplace, we had a process that was close enough to what’s recommended in the blog, and it worked well. Really well even, there were hardly any ego clashes, everyone would negotiate a consensus and we had “spike” tasks in our sprints so that we can take the time to think about and research complex problems.

And then the fire nation attacked…

A director left the firm and they hired someone from Amazon. He said that we should have a “bias for action”, and got rid of this process, and a lot of other stuff we had going for ourselves using other such catch phrases.

Getting him as a director was probably the worst thing to happen as we were under pressure to deliver stuff quickly all the time, and we’d then have to rework most of the shit because of missed requirements, or tools used not being insufficient for the task at hand etc. He was okay with it though, because “we delivered (shit) quickly”, and “our efficiency went up as indicated by the team velocity charts”.

Pretty much the entire team had left the company in ~1.5 years, and customer satisfaction metrics were in the gutter when I left.

I don’t know if he misunderstood “bias for action” and implemented it badly or if that’s genuinely how people at Amazon operate, but I won’t even think of joining AWS. Fuck that noise.

If anyone still sees messages from the spammer in the comments let me know, federated removals are wonky sometimes

Getting stuff down in writing is a good step; crucial for sure. But the process/ritual of decision logs doesn’t necessarily get you great analysis or effective outcomes. Two stories:

… or if your team uses arguments such as “let’s use X because Microsoft uses it too”, “let’s do X because everyone else does”, or “I used it in my previous project and it worked well, so let’s use it here too” then your decisions are likely suboptimal in the long term.

I’ve read decision logs and design docs that have included this kind of reasoning. Many meetings, everyone gets their say, it’s all written down. One time, I arrived a year or two into a project and I could indeed see how exactly they came to the decision that they did. The problem was that the reasoning was super weak. Over-emphasis on process, little on problem solving skills.

Other teams I’ve been on were fantastic problem solvers but super sloppy. If the right people were around, in the same room, they could solve things more cleanly in a fraction of the time of some company 10x the size. But for new staff, or if those key people were not around: chaos!

I guess my conclusion is that effective decision-making comes down to balancing a whole bunch of different behaviour.

In short: software is tricky.

I can’t say what their corporate culture is like now, but they’ve had a pretty poor reputation in the past, including the notion that the lowest performing 10% should be fired every year. The Amazon folks I’ve known have been great people - not at all the Gordon Gecko types you’d imagine from that - but culture in large corporations varies a lot by the team you’re in.

I came up with a saying back in the 90s when I was doing the startup scene - “Do you want it right, or by Tuesday?” Sometimes they do indeed need it by Tuesday. More of the time they have no idea why you need the extra days to get it right. But it’s really important for those in a leadership position - whether they’re managers or senior engineers - to push back and set expectations.

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod

Removed by mod