The Definition of "Done. by Wubbz"
In the Scrum web‑production process, the “Definition of Done” is a simple but powerful idea: it’s a clear checklist that defines exactly what “finished” means. No exceptions. No “we’ll fix it later.” Nothing swept under the rug.
Across my career and the many clients I’ve worked with, I’ve seen the same pattern repeat itself—missed opportunities that could have been avoided. Companies invest heavily in designing and launching a new website, but once it goes live, the attention fades. Budgets shift, staff changes, agencies transition, or teams simply don’t have the experience to maintain the site properly. Quality slips, technology evolves, devices change, and the site slowly falls out of alignment with modern standards.
My perspective on “Done” has been shaped not only by decades in the web world but also by lessons learned from other industries. One of the clearest parallels comes from construction—especially the philosophy championed by Mike Holmes and his “Make It Right®” approach.
With more than 35 years as a professional contractor, Holmes doesn’t just complete the job; he ensures the final result meets his standard of excellence. That mindset resonates deeply with me. It’s not about checking a box—it’s about craftsmanship, integrity, and walking away knowing the work is truly complete.
I often reference the old saying: “Good, Fast, or Cheap. Pick two.”
- If it’s fast and good, it won’t be cheap
- If it’s good and cheap, it won’t be fast
- If it’s fast and cheap, it won’t be good
Quality work—whether in construction or design production—requires clarity, commitment, and a shared understanding of what “Done” really means. That’s the standard I bring to every project.
Quality is non‑negotiable — but how we get there depends on the goals, the budget, and the realities of the project.
Mike Holmes (photo courtesy of makeitright.ca)
Done Right... the first time
I pride myself on paying close attention to detail and bringing a critical, experienced eye to everything I touch. That mindset started early in my career.
Like Mike Holmes, I also bring more than 35 years of professional experience to my craft. Working with corporate clients such as 3M, GE, John Deere, and Rockwell Collins (now Collins Aerospace), I’ve seen firsthand what it takes to earn—and keep—high‑expectation clients. In environments like those, there’s no room for shortcuts, sloppy execution, or “good enough.” The work has to be right.
That’s the standard I hold myself to. I will always deliver good work—work that’s thoughtful, complete, and built to last.
From there, it’s up to us to determine the right balance of budget and timeline to achieve the results you need.
Budget is Big. Effort is Relative.
I don’t sell products—I provide services shaped around your goals, your needs, and your budget. What I don’t do is price work solely on “effort,” because effort is always relative to experience. What might take someone else days may take me hours, and vice‑versa. The value is in the outcome, not the stopwatch.
Over the years, I’ve worked on everything from simple text updates to complex customer portals with layered security, user stories, and cross‑team workflows. I’ve helped prepare logos for distribution, built design systems for enterprise teams, and supported projects of every size and complexity.
But one of the achievements I’m most proud of goes back to the very beginning. In early 1998, I was hired to build two public‑facing websites—one for a company and one for an event—both due the following month. I had never built a website before. They handed me a license for Microsoft FrontPage, and I taught myself everything I needed to know: the software, the structure, the source code, the hosting. That project launched my career. Self‑taught. Short timeline. As much effort as it took to get it done.
That same willingness to learn, adapt, and deliver still drives how I work today.
If I haven’t done it before, I put in the effort to learn what it takes to meet our shared definition of “Done by Wubbz.”
Deadlines Define the Work
A clear understanding of key checkpoints and deadlines is essential. I don’t like leaving anything to assumption, so our first conversations will always include open, practical discussions about timelines. Due dates are often fixed, which means something else—scope, budget, or approach—may need to flex.
In my experience, timeline directly influences both budget and effort.
When we agree on what ‘Done’ means — in quality, budget, and timeline — we set ourselves up for work we can both stand behind!