Course Contents
Projects to Proof Converter >
Finding Your Numbers. What to Do When You Think You Don't Have Any
Article 11 of 15 / Projects to Proof Converter
Article Objective:
Develop systematic, practical strategies for identifying, calculating, estimating, and framing quantifiable impact across every project type, including the ones that appear to resist measurement entirely.
Finding Your Numbers. What to Do When You Think You Don't Have Any
Of all the sticking points in this course, one comes up more consistently than any other:
“I don’t think my work can be quantified.”
It’s said by the HR professional who spent six months redesigning an onboarding experience. By the operations coordinator who untangled a supply chain process that had been creating downstream errors for years. By the communications manager who rebuilt an internal knowledge base. By the project manager who delivered a complex, multi team initiative on time despite scope changes. By the trainer who built a curriculum from scratch. By the analyst who built the dashboard that changed how the senior team made decisions.
In almost every case, when you sit down with that person and work through the four categories below, you find numbers. Not always the obvious kind, not always a revenue lift or a campaign metric. But numbers that are real, honest, specific, and credible. Numbers that, when included in a bullet or a case study outcome section, transform a vague claim into an evaluable piece of evidence.
The belief that professional impact can’t be quantified is almost always the product of a too narrow definition of what counts as a number. This article is designed to expand that definition permanently.
Why the "No Numbers" Belief Is So Common
Before the strategies, it’s worth understanding why so many people arrive at this belief because understanding the source makes it easier to push past it.
The professional world constantly and implicitly teaches people that certain kinds of numbers are legitimate and prestigious while others are peripheral or insufficient. Revenue generated. Pipeline value. Percentage of quota attained. Return on ad spend. Net promoter score. These are the numbers that appear in dashboards, in quarterly reviews, in the metrics slides of company all hands presentations. They’re associated with sales, marketing, and finance, functions that exist specifically to produce and track financial results.
For everyone else, the implicit message absorbed over years of professional experience is: your work doesn’t produce the kind of numbers that matter. You do important things, but they’re not measurable things.
That message is wrong. But it’s understandable why it takes hold. And dismantling it requires not just a new attitude but a new toolkit, a practical, systematic set of categories and questions that surface the numbers that are actually there.
Category 1: Numbers You Already Have
This is where every search for numbers should begin, not with calculation or estimation, but with retrieval. In most cases, someone has already measured or reported on the work you did. You may just have forgotten where to look.
Performance reviews and check in documentation. Both formal annual reviews and informal quarterly check ins frequently contain specific language about outcomes. “Significantly improved team response time” in a performance review is your starting point: if your manager noticed it and documented it, the underlying metric likely exists somewhere, in a team dashboard, a help desk report, a call monitoring system. The language in the review is a breadcrumb that points toward a number.
Project wrap up communications. End of project summary emails, retrospective documents, stakeholder updates, and launch announcements often contain metrics that were shared at the time and subsequently forgotten. Search your email archive for project names, launch dates, and team names. Look for messages that include phrases like “happy to report,” “results are in,” “metrics from,” “update on.” These communications were written in the aftermath of success and often contain the most specific data you’ll find.
Analytics platforms and reporting tools you had access to. If your work touched a product, a process, a campaign, or a system that was tracked, and most work in modern organizations is tracked somewhere, the data exists in a platform. Even if you no longer have access, you may remember key metrics from regular reporting cadences. Remembered numbers, presented with honest framing (“based on the reporting I reviewed regularly during my time in the role”) are usable.
Meeting decks, presentations, and reports you produced. Any time you presented results to a manager, a leadership team, or a client, you almost certainly included numbers in the presentation. Those decks are likely in your email archive, on a shared drive, or in a tool like Google Slides or Notion. Finding the deck from the project retrospective is worth spending thirty minutes on. It probably contains everything you need.
Feedback emails and recognition messages. A specific compliment from a senior stakeholder, “Your analysis identified exactly the right issue”, may not be a number in the traditional sense, but it’s qualitative evidence that can be incorporated into a case study or a STAR story even when no quantitative metric is available.
Category 2: Numbers You Can Calculate
When archived records don’t surface an existing metric, the next step is calculation. You know more about your work than you might initially realize, and the numbers that can be derived from what you know are just as legitimate as the numbers found in a report.
Time savings. This is one of the most commonly available calculated metrics, and one of the most underused. If a process that used to require four hours now takes forty five minutes, the time reduction is 81%. If twelve people use that process weekly, the team saves 38.25 hours per week, roughly 1,900 hours annually. That number is real. It came from your knowledge of the before and after states. It belongs in your proof content.
Error rate or rework reduction. If a manual step was producing errors at a known or estimable rate, and your intervention brought that rate down, the reduction is calculable. “Our vendor invoice matching had an error rate of roughly 8% before the automation we built; post implementation monitoring showed it at under 1%” is a calculable result that came from observation and system data.
Volume and scale. How many people did the training reach? How many customers used the new process? How many reports were generated? How many markets were served? Volume is always a number, and it contextualizes impact meaningfully even when percentage change isn’t available. “Designed and delivered a training program that reached all 47 employees in the North American division” is a number, and it communicates scope in a way that “trained employees” completely fails to do.
Cost avoidance. Many of the most significant impacts in operational, administrative, IT, and HR functions come in the form of costs that were prevented rather than revenues that were generated. A vendor contract renegotiated at 18% lower than renewal terms. A compliance process redesigned to eliminate a fine risk that had averaged $30K annually. A system migration that discontinued a $15K monthly licensing fee. These are quantifiable results. They simply appear in the avoided cost column rather than the generated revenue one, and many professionals don’t think to count them.
Comparative performance. “Onboarding completion rates 23% above the prior year cohort average.” “Response time in the top quartile of the team for the full duration of the role.” “Project delivered 12% under budget against a portfolio average of 4% over budget.” Comparative metrics against a prior period, a team benchmark, or an industry standard are legitimate and often compelling evidence, particularly when the absolute metric is unavailable.
Category 3: Numbers You Can Estimate
When you can neither retrieve nor calculate an exact figure, estimation is both valid and professionally appropriate, with two essential conditions: the estimate must be conservative, and it must be clearly labeled as an estimate.
Professional estimates are not exaggeration. They are informed approximations derived from observation and professional judgment. Hiring managers who have worked in real organizations, which is most hiring managers, understand that not every outcome is formally tracked, not every system captures the data you need, and not every manager documented results in a retrievable format. A well framed estimate signals professional judgment, honest self assessment, and the willingness to engage with impact rather than retreat into vague language.
The framing language matters as much as the number itself:
“Reduced processing time by an estimated 30%, based on before and after time tracking I conducted informally over a two week period following the process change.”
This sentence does several things simultaneously. It names the result (30% reduction in processing time). It signals honesty (estimated). It provides the basis for the estimate (before and after time tracking). And it demonstrates the analytical instinct to measure, even informally, rather than just act and move on. That combination is significantly more credible than “Significantly reduced processing time.”
When estimating, always round in the conservative direction. If your genuine estimate is “somewhere between 25% and 40% improvement,” the honest conservative estimate is 25%. Under claiming a real result is safe. Over claiming, even slightly, creates a credibility risk if the estimate is challenged in an interview. A conservative estimate that you can defend fully is always worth more than a generous one that makes you hesitate.
Category 4: Qualitative Proof When Numbers Genuinely Don't Exist
There are professional roles and project types where quantitative proof is genuinely sparse. Strategic advisory work. Organizational culture development. Executive communication support. Long cycle relationship management. Creative direction. Political navigation within complex stakeholder environments. These are real, valuable professional contributions, and they often resist numerical measurement in any form that is honest and specific.
In those cases, qualitative proof presented with precision is the appropriate alternative. “Qualitative proof” does not mean vague praise or general statements of success. It means specific, attributable, contextual evidence of impact that doesn’t happen to take numeric form.
Attributed feedback from specific people in specific positions. “The Chief Operating Officer included this initiative in the company’s annual impact report as one of the year’s three strategic milestones” is qualitative evidence. It’s specific. It’s attributed. It’s contextually meaningful. It’s vastly more credible than “received positive feedback from leadership.”
Adoption as proof of value. “The framework I designed has become the standard approach used by all eight regional teams” is evidence, not of a metric, but of an outcome. The adoption is the proof. It tells the reader that the work was not just completed but valued enough to be institutionalized.
Promotions, expanded responsibilities, or recognition tied to the project. If a specific piece of work was cited as a factor in your promotion, in a public recognition, in your selection for a high visibility initiative, that recognition is evidence of impact even without a numeric metric. Name it specifically: “This analysis was cited in my promotion rationale as having changed how the leadership team thought about market segmentation.”
Temporal and relational outcomes. “The project delivered in full despite a six week scope expansion introduced at the midpoint” is a qualitative outcome with precision. “The client relationship was restored and the account was retained for the following year after a difficult implementation” is a qualitative outcome with a specific consequence. These statements are not vague. They are specific, verifiable, and meaningful.
A Practical Exercise for Every Project
For every project on your list, work through the four categories in sequence:
- Spend ten minutes searching your archive, email, cloud storage, shared drives, message history, for any existing data, metrics, or feedback associated with this project. Write down everything you find.
- Using what you know about the before and after states, calculate any derived metrics that are mathematically available to you, time savings, error reduction, volume, cost avoidance.
- For any dimension of impact that can’t be retrieved or calculated precisely, formulate a conservative estimate with a clear basis for the estimate. Write it as a full sentence including the framing language.
- For dimensions that genuinely can’t be quantified, write one or two sentences of qualitative proof, specific, attributed, contextual.
At the end of this exercise, you will almost certainly have more material than you expected. The professional instinct that “my work isn’t measurable” is typically a failure of search and framing, not a reflection of a genuine absence of evidence.
The Core Reframe
The useful question is not “Do I have a number?” because that question is shaped by a definition of “number” that’s too narrow to serve you.
The useful question is: What changed because of my work, and can I describe that change specifically enough for a reader to understand its magnitude and significance?
If something changed, and in almost every professional project, something did, there is almost always some form of quantification available to describe how much it changed. The work of finding that quantification is not optional decoration. It is the difference between claim and evidence. And evidence is the only currency that earns trust from a skeptical evaluator.
Key Takeaway:
The four category framework, numbers you already have, numbers you can calculate, numbers you can estimate, and qualitative proof when numbers genuinely don’t exist, covers every project type. Work through all four categories before concluding that a project can’t be quantified. The conclusion is almost always premature.
Action Step:
Choose the project on your list that you’ve most consistently assumed was “unquantifiable.” Apply the four category framework to it systematically, spending at least five minutes on each category. Write down every piece of evidence you find, numbers, estimates, qualitative proof, before filtering. Then read what you’ve found. The evidence is almost always there.
- The next module applies the complete framework to three different project types in fully worked examples, showing the transformation from raw input to polished, proof ready output across all three formats.