A project wrapped up recently, and when someone asked how it went so smoothly, I heard myself say, "Honestly, we just got lucky." Everything had lined up. The teams we depended on were ready when we needed them. The decisions that usually stall for weeks landed in days. All the stars aligned.
Then I thought about it for a second longer, and the sentence did not hold up. I had worked hard on that project, and most of that work was not code. I had worked on aligning people. I had worked on getting everyone on the same page before it mattered. I had spent time with the PMs, and with each of the teams involved, and I had been proactive about the conversations that tend to show up late. When the moment came and the other side happened to be ready to receive what we were sending, that was not a coincidence. A lot of it was the result of work I had already done.
There is an old line for this, usually credited to Thomas Jefferson even though Monticello lists it as spurious: "I'm a great believer in luck, and I find the harder I work, the more I have of it." The earliest close match Quote Investigator found is from Coleman Cox, in a 1922 collection called Listen to This. I think it is true, and I think both halves are true.
Luck is real, and it is not the whole story
I do not want to pretend luck does not exist. It does, and it is a big component of a lot of success. Timing, the people you happen to work with, a reorg that goes your way, a dependency that ships early: none of those are fully in your control. Pretending otherwise leads to the opposite mistake, where every success is proof of your own brilliance and every failure is somebody else's fault.
But "we got lucky" quietly erases the part that was not luck. In engineering, a lot of what gets called luck is a choice that turned out right: you picked the solution that held up, or you engineered the path the project took. A dependency team being ready is often the trace of a conversation you had a month earlier. A fast decision is often the result of the context you put in front of the decision maker before they needed it. The stars aligning is, a lot of the time, people aligning, and someone did that aligning.
The way I think about it now is in terms of odds. Diligence, planning ahead, and paving the path for a project do not guarantee anything. They change the odds. Each conversation you have early, each dependency you confirm before it blocks you, each piece of shared understanding you build ahead of time, takes a way the project could fail off the table. When enough of those are gone, the remaining outcomes are mostly good ones, and from the outside (and sometimes from the inside) that looks exactly like luck.
Luck compounds when you build on earlier wins
The other half is that the work carries forward. A project that went well leaves things behind: trust with the teams you worked with, relationships with the PMs, a pattern that worked, a reputation for following through. The next project starts on top of all of that. People answer faster because they remember the last time. Dependencies line up sooner because the path already exists. I wrote about this kind of carrying forward in Leverage and the Stairs You Build: each step you build makes the next wall easier to climb. Building on top of earlier success is how you get there faster, and it looks a lot like a lucky streak to anyone who did not see the stairs being built.
This is also why I think the attribution matters, and why I do not want to leave "we just got lucky" as the official story. If the success was luck, there is nothing to repeat. If the success came from aligning people early and working the dependencies before they were urgent, then that is a practice, and a practice can be done again, taught, and noticed. The same problem shows up in how work gets rewarded. As I wrote in Quality Engineering vs Engineering Quality, the work that prevents problems is mostly invisible when it succeeds, and crediting the outcome to luck makes it even more invisible.
Saying it more accurately
I still think there is room to say "we were lucky." There will always be projects where the timing simply broke our way, and saying so is honest. What I want to stop doing is reaching for luck by reflex, as if the groundwork never happened. A more accurate version is something like: "A few things broke our way, and we were ready for them because of the work the team put in early."
That sentence gives credit to luck where it belongs and to preparation where it belongs. It also tells the people who did the aligning, the planning, and the proactive conversations that the work was seen. And for me, it is a reminder of what to do next time. The harder I work on the parts nobody sees, the luckier the next project tends to get.