In How Big Things Get Done authors Flyvbjerg and Gardner talk about why large projects fail.
They look at case studies ranging from Hendrix’s perfect recording studio to the most-failed home project (kitchen renovations) and how come China builds more infrastructure faster than The West.
A few themes keep coming up:
- maximizing over satisficing
- slow iteration
- invention instead of reuse
- scope creep
- work in progress
We’ve talked about how work in progress kills your progress. Starting new projects before you finish the old projects is a recipe for overwhelm, multitasking, and slowly poking around instead of finishing work with force.
Scope creep happens every time you go “We’re here, might as well do X, Y, and Z cleanup”. Make it work first. Don’t solve problems you’re not here to solve.
Maximizing over satisficing means that you’re looking for the perfect solution instead of something good enough. This often leads to invention instead of reuse where you spend too much of your budget (time, money, brainpower) building a custom thing instead of choosing a good enough solution that you can start using immediately.
All this leads to slow iteration, which is what really kills big projects. We spend so much time planning and maximizing the project before the work even starts that by the time we start, our plans are outdated and don’t fit anyone’s needs.
Plans always need revision anyway – you find new details when doing the work. Instead of big upfront design, get started sooner with a less detailed plan that’s easier to change. Architecture is like a path in the woods after all.
Cheers,
~Swizec
Did you enjoy this article?
Continue reading about Why software projects fail
Semantically similar articles hand-picked by GPT-4
I write articles with real insight into the career and skills of a modern software engineer. “Raw and honest from the heart!” as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec’s Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
“Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll
till the end. And wow always take away lessons with me.
Inspiring! And very relatable. 👌”
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companies
Learn more
Have a burning question that you think I can answer? Hit me up on twitter and I’ll do my best.
Who am I and who do I help? I’m Swizec Teller and I turn coders into engineers with “Raw and honest from the heart!” writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉
ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand
with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️
#software #projects #fail #Swizec #Teller
