I think I would avocate actually against processes. Processes are nice, handy, and sage, but that assumes you have unlimited time. A baby crying and death approaching really make you rethinking useless 1-1s and meetings.
Your counter is that death is a better motivator as well as being a desperate parent?
Well, main generational challenge is procrastination with too many unlroductive time sinks available.
I think I would avocate actually against processes. Processes are nice, handy, and sage, but that assumes you have unlimited time. A baby crying and death approaching really make you rethinking useless 1-1s and meetings.
I feel like the way you're using 'process' and the way TFA is using it are not the same, which makes this comment orthogonal to the point TFA is trying to make.
It hurts my soul to read of "Agile" as a fixed process consisting of arbitrary decisions like two-week sprints and 9:30 stand-ups. Agile is "responding to change over following a plan". https://agilemanifesto.org There's surely something to be said for bundling behaviors and triggers, but I do wish the world of software development hadn't missed the whole damn point of agile.
Still reading but I like how Cat Hicks in Psychology of Software Teams (2027) confronts this dilemma on page 9: "Agile Manifesto said, 'Individuals and interactions over processes and tools.' DevOps made the argument that cohesive processes in software development needed to be invested in... Agile, DevOps, Platform Engineering, or DevEx, every engineering organization I've ever met with is struggling with implementing these ideals in the real world."
> The ‘optimal’ approach would be to check traffic, analyze the data, and shave off five minutes from my journey. Why not letting Google Maps decide?
Then you are spending a bit of attention on an ongoing basis following the instructions given by the nav. If you're basically driving the same route every time regardless, you'll completely detach from having to pay any attention to it at all, it becomes muscle memory. AKA highway hypnosis.
> Both of these examples demonstrate a process, or a decision made in advance A decision made in advance is not a process. Unlike all the other real-world examples of committed processes in the article, premade decisions don't require discipline - the actual substitute for motivation - to execute in a meaningful way that ensures actual progress.
I can make a decision to go to gym tomorrow.
My process/playbook for determining if I go to the gym is I go if I didn’t go the day before.
This is both a premade decision and a process that requires discipline to execute on.
So why isn’t a decision made in advance an example of a simple process?
A good process deletes decisions (the Glasgow northbound rule) by focusing you on exactly the steps you need to take. A bad one might remove a few but spawn fifty more (suddenly you're debating story points/t-shirt sizes, velocity arguments, Definition of Done, but hey, at least you know it's all scheduled to start at 09:30)
This is a good one. Sometimes it doesn’t even matter if the made decision is suboptimal. It’s better than no decision. Opinionated linters is an example. Sometimes you just gotta turn your brain off and move forward.
Agree. My team standardized on black in our Python CI/CD pipeline and precommit hooks and it was surprising how much time we reclaimed from not having to review coding style and discuss patterns. The compromise was to apply black and not think about it. And it worked out really well. This was back in the days when humans still wrote code XD
> Both of these examples demonstrate a process, or a decision made in advance A decision made in advance is not a process. Unlike all the other real-world examples of committed processes in the article, premade decisions don't require discipline - the actual substitute for motivation - to execute in a meaningful way that ensures actual progress.
The useful part of deciding in advance isn't that discipline disappears, it's that you remove one place where you can negotiate with yourself