Done Means Done: How to Build and Make Your Quality Standard Visible
Undefined standards are invisible organizational drag that cost you millions in rework, revision, and lost velocity. Here's how to fix it at the root.
Issue #10 | April 16, 2026 | 8-minute read
Welcome (back) to đ VELOCITY by Kristin Skinner
If this is your first issue, hereâs my operating principle: In a world obsessed with outcomes, I show leaders how to master the inputs. Because how your teams work together is just as important as what they deliver.
In this issue Iâm making visible what your revision cycles are actually telling you: undefined quality standards are coordination overhead, role blur, and handoff failure all at once, and your organization is paying for it every day.
Iâm Kristin Skinner: advisor, author, educator, and auto enthusiast. I work with Founders, Operators, CEOs and executive teams on one of the most expensive problems in business today:
Organizational Drag, the invisible friction and systems that determine how fast organizations can actually move.
To receive new posts and support my work, consider becoming a free or paid subscriber.
The Work Is Done. Or Is It?
Someone on your team finishes a deliverable and turns it in.
You look at it and think: this isnât what I asked for.
They think itâs done but you know it isnât. The gap between those two positions is where the rework lives. It has nothing to do with effort or intent, and everything to do with a standard that was never made explicit.
Now multiply that by every deliverable, every team, every week.
The cost of rework quietly hides inside delivery timelines as unexplained delays. It shows up in your teamâs capacity as âweâre too busyâ when the work volume hasnât actually increased. It surfaces in exit interviews as âendless revision cyclesâ and âmoving goalposts.â And it sits entirely outside your dashboard, untracked, unbudgeted, unnamed.
What Your Rework Rate Isnât Showing You
You track revenue, retention, and roadmap progress. You probably track delivery velocity.
What rarely gets tracked: how much of your output was already âdoneâ once before it landed.
Hereâs what it costs in a 100-person organization when quality standards are implicit rather than explicit:
Rework Rate Calculation
3 average revisions per deliverable before acceptance
4-6 hours of combined time per revision cycle
(creator + reviewer + stakeholders)
50 active deliverables at any given time
ââââââââââââââââ
= 600-900 hours of rework per month
x $175/hour (blended hourly rate)
ââââââââââââââââ
= $105K-$157K per month in rework
= $1.3M-$1.9M per year
Thatâs $1.3M-$1.9M per year in work done, reviewed, rejected, and done again.
Every revision loop adds days. Days become weeks. Weeks become the quarter where your roadmap slipped and no one could explain why.
Unlike every line item on your P&L, this cost doesnât appear anywhere. Your board never asks about it. Itâs quietly compounding on every team, on every deliverable, right now.
And itâs invisible on your dashboard.
Where the Standard Gap Hides
Quality problems rarely look like quality problems. They typically look like three other things. Here are the patterns I see across Fortune 500 executive teams and founder-led businesses alike, at every stage of growth.
1. The Revision Loop
Work comes back for changes more than once. Timelines slip. Stakeholders express vague dissatisfaction thatâs hard to act on. The team works harder on the same deliverable with diminishing returns.
Whatâs actually happening: No shared definition of done existed at the start. The standard lived in the reviewerâs head, communicated through reactions (approval or disappointment) rather than criteria. The team learned to read signals rather than meet a bar.
A Head of Design at a scaling tech company put it exactly right when she asked me this in a Design Leadership at Scale Executive session:
âHow do you establish and measure quality? Do the levers change by company, and do you need cross-functional buy-in first, or does your function own this?â
My answer: your function owns the definition. Cross-functional alignment is needed on two specific things: instrumentation (getting quality metrics prioritized so theyâre actually built and tracked) and time (protected capacity to act on what the data tells you).
Without those two, a quality framework lives in a document. A quality framework that lives in a document is just a more sophisticated version of âIâll know it when I see it.â
The Test: Pull your last 10 completed deliverables. How many required more than one revision cycle? More than 4 out of 10 signals a standards gap, not a performance gap.
The Fix: Define done before work starts, not after it lands. Three questions for every significant deliverable:
What does this need to accomplish? (outcome, not output)
What are the specific criteria for evaluation?
Who has final say, and by what standard?
Your homework: Pick one deliverable type this week and answer those three questions before the next one starts.
2. Quality as a Person
One or two people on your team are the informal quality gatekeepers. They âjust knowâ what good looks like. Work that passes through them lands well. Work that bypasses them gets kicked back, often without clear explanation.
Whatâs actually happening: The quality standard is a person, not a system. The criteria exist, trapped in someoneâs institutional knowledge rather than documented where the whole organization can use it.
From a Fortune 500 VP of Operations: âWhen I left, my replacement didnât know the criteria Iâd been applying to everything before it reached the C-suite. Within two quarters, materials going to leadership required three to four revision rounds. The instinct was to look at the new hire. The actual gap was documentation.â
My answer: Talented people compensate so effectively for a missing system that the system never gets built. It looks like excellence and, in the individual, it is. At the organizational level, itâs risk hiding in plain sight.
The Test: If a key person left tomorrow, could the next person in that role produce work to the same standard? An honest ânoâ means institutional knowledge is doing the work that organizational systems should be doing.
The Fix: Extract the standard from the person and put it in writing. The simple conversation: âWalk me through how you evaluate this. What makes you say yes vs. no?â Document those criteria, test them against real work, calibrate until they hold without the person in the room.
Your homework: Identify the person on your team who is the standard. Have that conversation this month.
3. The Checkpoint Trap
Review cycles keep getting added. Approvals multiply. The process gets slower and more bureaucratic each quarter. People flag the overhead. Leadership adds more oversight to identify, validate, and address the friction.
Whatâs actually happening: Every review layer was added after something went wrong, e.g. a deliverable missed the mark, a launch landed badly, a standard wasnât met. Instead of diagnosing why, the organization added a checkpoint to catch it next time.
Each mistake becomes a permanent layer. The process gets heavier and the rework rate doesnât drop. It just gets caught later, at higher cost. The root cause, an undefined standard, stays intact.
Real example: I worked with an executive team where a significant deliverable went through seven review layers before reaching the CEO. Each layer was added after a different failure. None were removed once that failure was resolved. Total time from draft to approval: 22 business days. The CEOâs actual changes: two paragraphs.
When we mapped what each reviewer was checking for, three of the seven layers were evaluating the same thing, something that a single shared standard at the start would have addressed entirely.
From the CEO afterward: âWe built a bureaucratic process to compensate for not having a definition. It cost us months of slow decisions before we saw it for what it was.â
The Test: Map your last major deliverableâs review process. Count the reviewers. Ask what each one was checking for. Overlap means a standard is missing, not that more oversight is needed.
The Fix: Before adding a review cycle, ask: what standard failure is this designed to catch? Then: could that standard be defined upfront instead? Upfront clarity is always cheaper than downstream inspection.
Your homework: Count the approval steps for one recurring deliverable. If the number has grown in the last year without improving quality, youâre adding layers where you need definition.
The Three Levels of âDoneâ
Quality isnât a single thing. It operates at three levels:
Level 1: Task Complete The work exists. The deliverable was produced. This is where teams stop when they say something is âdone.â Necessary. Not sufficient.
Level 2: Standard Met The work meets explicit criteria agreed upon before it started. Reviewers evaluate against something specific. Feedback is criteria-based, not taste-based. This is the level thatâs almost always missing.
Level 3: Value Delivered The work accomplished what it was intended to accomplish. It moved the needle on the outcome it was meant to move. This is where quality becomes strategic.
The rework cycle lives in the gap between Level 1 and Level 3, with no Level 2 to bridge them. Work gets produced to the letter of the request. The reviewer reacts to whether it worked. The creator has no way to know what âworkedâ means until after the fact.
Define Level 2 before work starts. Thatâs the lever.
The Pattern Underneath All Three
Each of these is the same problem in different form.
Every layer of coordination overhead, role blur, and handoff failure is bandwidth leaders canât reclaim. Undefined quality standards create all three simultaneously:
Work loops back (coordination overhead)
The standard lives with one person (role blur)
Deliverables fail at the handoff between creator and reviewer (standard met checkpoint)
Itâs an operating model that hasnât kept pace with the organizationâs growth.
The leaders who scale well treat quality standards with the same rigor they apply to strategy. They make the implicit explicit by defining âdoneâ before work starts. They extract criteria from the people who hold them and put them into systems that outlast any individual. They reclaim the bandwidth that rework was consuming and redirect it toward the next level of growth.
A higher bar no one can see is just a more sophisticated way of staying stuck.
Pick an Invisible Problem to See Whatâs Hidden
Diagnostic: The Rework Audit
Pick one recurring deliverable type: a report, a brief, a presentation, or a proposal. Run this audit.
Step 1: Count the cycles How many rounds of revision does this deliverable type typically require before acceptance? The actual number, not the ideal.
Step 2: Identify the standard Write down, in specific terms, what âdoneâ looks like for this deliverable. Not âhigh qualityâ or âexecutive-ready.â Actual criteria. If you canât write it down, you have a preference, not a standard.
Step 3: Find where the standard lives Is it documented? Is it consistent across reviewers? Does the person creating the deliverable have access to it before they start, or only after they submit?
Step 4: Calculate the cost Revision cycles Ă hours per cycle Ă fully-loaded hourly rate Ă deliverables per month. Then compare that number to what it would cost to define the standard once and train to it. The gap is your opportunity.
What Iâm Building
The standards framework in this issue is one piece of something larger.
VELOCITY OS is an always-on diagnostic and strategist built to tell leaders the size of organization theyâre capable of running and whatâs standing between them and the next level. The Organizational X-Ray, one of the core diagnostic tools inside VELOCITY OS, surfaces the systems gaps, including quality standards like the ones in this issue, that are compounding invisibly before they become the ceiling on your next stage of growth.
Founding access is open. Pricing locks permanently for early members.
đ velocityco.io/velocity-os
Your Turn
Run the Rework Audit on one deliverable type. The number will tell you more about your quality infrastructure than any performance review.
And if youâre the one whose judgment determines whether something is âdone,â ask yourself whether that judgment is documented anywhere the rest of your team can access. If it isnât, youâre the standard that is one departure away from disappearing.
Give it a structural home.
đ Under the Hood
WHAT IâM OBSERVING
The rework conversation is the one that consistently catches leaders off guard. Calendar overhead, role blur, decision drag land quickly because people identify with them. Quality is different. There is an assumption that standards exist, that people are familiar with them, and that the bar is shared even when it has never been written down. This realization that I just shared lands hard.
THE MANUAL (Books and Reading)
Asanaâs Anatomy of Work Index: How work about the work gets in the way of real work
Rid Your Organization of Obstacles That Infuriate Everyone: Why organizational layers compound and how to remove them (requires HBR subscription)
The Checklist Manifesto by Atul Gawande: On what explicit standards do for complex work (the clearest case Iâve found for why defining done isnât bureaucracy, itâs intelligence)
Org Design for Design Orgs by Skinner and Merholz: shameless plug, but the 12 Qualities framework (including Quality 7: Establish and Uphold Standards of Quality) applies well beyond design
Team Topologies, second edition 2025, by Skelton and Pais: on flow, cognitive load, and how team interaction modes determine whether quality standards travel or evaporate
THE TOOLKIT (Resources You Can Use)
The Rework Audit: Use the four-step Diagnostic above. Or hit reply and Iâll send you the free template.
Calendar Test + Decision Velocity Test: velocityco.io/free-diagnostics
VELOCITY OS (founding access): velocityco.io/velocity-os
VELOCITY by Kristin Skinner publishes bi-weekly for executives, founders, and operators who want to move faster by finding and fixing the invisible friction slowing them down.