The Difference Between Finished and Done
For years, I had a sticker on the corner of my laptop that read, Stop Starting. Start Finishing.
It survived more laptops than I can remember. It sat through architecture reviews, quarterly planning meetings, budget discussions, and enough roadmap debates that the edges eventually began to curl. More than once I found myself pointing at it instead of repeating the same argument yet again. Software organizations have an extraordinary ability to create work. Every successful initiative somehow becomes permission to begin three more. Before long, every team is busy, every roadmap is full, and nothing ever seems to make it across the finish line. The sticker wasn't there because I thought software development was complicated. It was there because I believed that focus was one of the few competitive advantages a team could actually control.
I still believe that.
Imagineering a Candy Store
Several years ago, I spent an afternoon talking with one of Disney's Imagineers. Like almost everyone who hears the title "Imagineer," I expected stories about Space Mountain, Pirates of the Caribbean, or whatever ambitious new attraction happened to be under construction at the time. Instead, he spent hours talking about the candy store on Main Street. I kept waiting for the conversation to move on to the rides everyone travels across the country to experience. It never did. As far as he was concerned, this wasn't a detour. This was the story worth telling.
I remember trying to steer the conversation toward the attractions everyone recognizes. He always found his way back to the candy store. He described how guests entered the building, where their attention naturally drifted, why certain displays had moved while others hadn't changed in years, and how seemingly insignificant details subtly influenced the experience of walking down Main Street. He wasn't describing a retail renovation. He was describing an experience so carefully considered that most guests would never consciously notice the work at all. The details themselves have faded over the years, but the feeling hasn't. I remember leaving that conversation genuinely puzzled that Disney had assigned one of the most respected creative engineering organizations in the world to rethink a candy store.
At the time, I chalked it up as another wonderfully eccentric Disney story. Of course Disney would overthink a candy store. Of course Disney would apply Imagineering to something most companies would hand to a facilities department. It felt excessive in the way Disney often does. I told the story a few times because it made people smile, then I quietly forgot about it. It became another interesting memory that didn't seem connected to anything else.
Until this week.
The Construction Walls Never Leave
I found myself sitting on a bench in Magic Kingdom while my family wandered into another gift shop. It wasn't a profound moment. I wasn't looking for inspiration. I was simply watching people. Big Thunder Mountain Railroad had just reopened after months hidden behind construction walls. Carousel of Progress was closed for refurbishment. Around the park, construction crews worked quietly behind temporary barriers while thousands of guests walked past without giving them a second thought. Fresh paint appeared on buildings that hadn't looked like they needed painting. Landscaping crews replaced plants that seemed perfectly healthy. Somewhere another team was rebuilding something that, from the outside, appeared to be working just fine.
The construction itself wasn't what caught my attention. Disney has always been rebuilding something. What struck me was how completely everyone accepted it. Parents pushed strollers around construction walls without slowing down. Children pulled their families toward Big Thunder because it had finally reopened. Guests glanced at signs announcing temporary closures, adjusted their plans, and kept walking. Nobody seemed irritated that Disney was investing millions into attractions people already loved. If anything, the construction almost inspired confidence. There was an unspoken assumption that whatever disappeared behind those walls would eventually come back better than before.
That's when I remembered the Imagineer. Not because I was thinking about candy, but because I suddenly realized the candy store and the construction walls were telling exactly the same story. For years, I'd thought the Imagineer had been talking about a remarkably detailed renovation. Sitting on that bench, it finally occurred to me that he and the crews rebuilding Big Thunder were doing exactly the same job. One happened before opening day. The other happened years afterward. Both existed for exactly the same reason.
Preserving What People Remember
As I walked through the park that afternoon, I started noticing something I had somehow managed to miss after decades of visiting Disney. Almost nothing around me was exactly as it had been when it first opened. Pirates of the Caribbean has changed repeatedly over the years. Haunted Mansion has quietly evolved while somehow remaining unmistakably Haunted Mansion. Restaurants have been redesigned. Hotels have been refreshed. Main Street itself has been subtly refined in countless ways that most guests will never consciously recognize. Disney isn't trying to create a different Magic Kingdom every few years. It's trying to preserve the feeling people remember while continuously improving everything underneath it.
That might be the hardest kind of work there is. Building something new is exciting. Everyone celebrates opening day. There are ribbon cuttings, announcements, and headlines. Improving something that already exists is quieter work. It rarely earns the same attention because, when it's done well, most people barely notice it happened. Guests don't walk through Magic Kingdom saying, "The guest flow through the candy store feels much better than it did five years ago." They simply leave with the same feeling they had the last time they visited, somehow unaware that hundreds of people have spent years making sure that feeling survived another generation.
When Finished Becomes Done
Software isn't all that different. We celebrate launches because they're visible. We celebrate new products because they're tangible. We reward the teams that create something where nothing existed before. Then, almost without realizing it, our attention shifts to the next initiative. The product that just launched enters a different phase of its life, one we often describe with words like maintenance or support, as though the work of caring for something is somehow less important than the work of creating it. The projects are finished, so we begin acting as though the products should be finished too.
Disney never seems to make that mistake. Big Thunder reopened because Disney decided a successful attraction was still worth improving. Carousel of Progress closed because Disney believes an attraction built generations ago still deserves investment. The candy store wasn't redesigned because it had stopped selling candy. It was redesigned because Disney believed a tiny piece of the guest experience was still worth making better. None of those decisions were reactions to failure. They were commitments to success. Disney wasn't fixing things that people had stopped caring about. It was investing in the very things people cared about most.
Walking back down Main Street before leaving the park, I found myself looking at that candy store a little differently. Years ago, I thought the Imagineer had wasted an afternoon explaining something too ordinary to matter. Now I wonder if he had been trying to explain Disney's philosophy all along. He never once talked about building attractions. He talked about caring for experiences. I was the one who kept trying to change the subject.
Worth Making Better
I still believe in the sticker that sat on my laptop for all those years. Teams absolutely should stop starting and start finishing. Projects deserve finish lines because unfinished work rarely creates value. But somewhere over the years, I quietly started applying that philosophy to the things we build instead of the projects we use to build them. Sitting on that bench in Magic Kingdom, watching one attraction reopen while another disappeared behind construction walls, I realized Disney has never confused those two ideas.
The older I get, the less interested I am in building things that can be finished. I'd rather build something that, years from now, someone still believes is worth making better.