As engineers, our decisions shape the quality of our deliverables. Yet, our decision-making process can be flawed. In this comprehensive guide, uncover the three crucial levels of decision-making
The 1-way vs 2-way door decision is huge. There was one time I was shipping a change that was a big change to development workflows--essentially preventing any new JS file into the codebase, but it was easily reversible. We could just comment out the line that is adding this form of linting.
Although it was a big change to workflows, it was a small change code-wise and easy to reverse. I was able to use that to argue why we should try it, because we could easily go back if people don't like it.
Comparatively, if it was something that had a high cost of reversal, it would have been a much harder sell
Most companies embrace agile methodologies, experimenting and failing fast. 2-way door decisions are a good argument to bring because it's speaking in the language of the business. They can understand :)
I'm a big fan of the 2-way door decisions. During freelancing, I always felt like an added extra that I could tell the client the what-if scenarios and ensure them that we consider longevity and maintainability when picking our technologies and solutions.
As for data-driven, it depends on what data you rely on: GitHub Star count 😃, market research, and estimating your potential user base and needs. Then, pick the technology that makes the most sense financially for your case. Because, in the end, it all comes down to finances.
Fran, fantastic insights! I resonate with the principle of quick commitment, yet I’m cautious about irreversible decisions. I prefer to reflect, invoking the deliberate thought Kahneman highlights in “Thinking, Fast and Slow.” This balanced approach aids in nuanced decision-making.
Great article, Fran and thanks for the mention!
The 1-way vs 2-way door decision is huge. There was one time I was shipping a change that was a big change to development workflows--essentially preventing any new JS file into the codebase, but it was easily reversible. We could just comment out the line that is adding this form of linting.
Although it was a big change to workflows, it was a small change code-wise and easy to reverse. I was able to use that to argue why we should try it, because we could easily go back if people don't like it.
Comparatively, if it was something that had a high cost of reversal, it would have been a much harder sell
Thanks for sharing your experience, Jordan!
Most companies embrace agile methodologies, experimenting and failing fast. 2-way door decisions are a good argument to bring because it's speaking in the language of the business. They can understand :)
I'm a big fan of the 2-way door decisions. During freelancing, I always felt like an added extra that I could tell the client the what-if scenarios and ensure them that we consider longevity and maintainability when picking our technologies and solutions.
As for data-driven, it depends on what data you rely on: GitHub Star count 😃, market research, and estimating your potential user base and needs. Then, pick the technology that makes the most sense financially for your case. Because, in the end, it all comes down to finances.
Thanks, Akos!
Yeah like any metric, you can game it and make an argument for whatever you want :)
Fran, fantastic insights! I resonate with the principle of quick commitment, yet I’m cautious about irreversible decisions. I prefer to reflect, invoking the deliberate thought Kahneman highlights in “Thinking, Fast and Slow.” This balanced approach aids in nuanced decision-making.
Great read, Fran! I think making decisions based on facts and referencing them, saves a lot of back and forth time.