Writing About Work You Cannot Measure Yet

TL;DR

• Main decision: report completed deliverables honestly without inventing outcomes — describe what was delivered, the scope of contribution, and the current evaluation state when it matters.
• Useful method: place work on a delivery timeline using four stages—proposed, built, released, evaluated—to choose accurate verbs and avoid implying unmeasured results.
• Limit/check: label targets, forecasts and observations distinctly, note pending evaluations where they would imply a result, and be ready to answer “How do you know it worked?”

Distinguish completed work from a result still being evaluated

You may need to apply for a job before the outcome of your latest project is known. A feature has shipped but adoption is still being observed. A training program has launched but follow-up assessment is pending. A process change is in use but the comparison period is incomplete.

Do not invent a result to make the bullet feel finished. Describe what you delivered, the scope of your contribution and the current evaluation state when it matters. A completed artifact is real evidence even when the longer-term effect remains unknown. The key is to avoid presenting an intended benefit as an observed outcome.

Locate the work on a delivery timeline

Use four stages to review the claim: proposed, built, released and evaluated. These are an editorial aid, not a universal project lifecycle. Your organization may use different terms, but the distinction helps you choose accurate verbs.

Consider fictional project coordinator Ellis, who introduced a revised onboarding checklist:

If Ellis has reached rollout, “reduced onboarding errors” is premature unless those errors have already been measured appropriately. “Rolled out a revised onboarding checklist with guidance for team leads” describes the completed work without borrowing evidence from a future stage.

Make the delivery itself specific

A vague bullet such as “Worked on improving onboarding” leaves the reader with little to assess. Add the actual responsibility: mapping missing steps, coordinating reviewer feedback, preparing the checklist or organizing the rollout. Include the audience or process where that context helps.

A stronger fictional version is: “Mapped recurring onboarding handoff gaps and coordinated a revised checklist with HR and team leads before rollout.” It shows analysis and coordination without claiming that Ellis controlled every part of onboarding.

If another person approved the process, preserve that boundary. If rollout covered only a pilot group, name it as a pilot rather than implying organization-wide adoption. The resume accomplishments guide can help identify concrete evidence when a headline performance metric is unavailable.

Label targets, forecasts and observations differently

A target is what the project hopes to achieve. A forecast is an estimate. An observation is what the available evidence shows. Do not combine them in a sentence that makes the target sound measured.

“Designed to shorten onboarding time” describes purpose, but it is often weaker than explaining the actual change. “Reduced onboarding time by the target amount” is not defensible merely because the business case contained that number. If you include a target at all, label it explicitly and consider whether it adds enough value to justify the space.

Early feedback also needs a boundary. Positive comments from a small pilot can support a statement about that feedback, not a universal claim about effectiveness. Avoid converting “participants said the instructions were clearer” into “proved the program increased productivity.” Those statements answer different questions.

Decide whether to mention the pending evaluation

Not every bullet needs “results pending.” If the sentence makes only a delivery claim, it can stand on that evidence. A pending note is useful when the surrounding wording would otherwise imply a result, or when evaluation is an important part of your ongoing responsibility.

For example: “Launched the pilot checklist and established a review log for onboarding exceptions; follow-up evaluation remained in progress at departure.” This may be appropriate when the candidate left before the review. If still employed, describe your current evaluation task accurately rather than predicting its conclusion.

Keep the resume concise. CareerOneStop's work-experience guidance emphasizes relevant context around tasks and outcomes. Your job is to select the strongest available evidence, not to produce a project status report with every unresolved dependency.

Preserve a version you can update honestly

Maintain a private evidence note with the delivery date, current scope, measurement definition and what remains unknown. When new evidence arrives, review the claim again. A later metric should not be added automatically if it covers a different audience, period or team contribution from the original bullet.

Use clear resume version names so you know which claim appeared in each application. If an interviewer has an older version, explain the update plainly: the earlier resume described rollout; the later evidence addresses the subsequent evaluation.

Finally, prepare an answer to “How do you know it worked?” You can say what is known, what is not yet known and how evaluation was designed. That is more credible than forcing certainty into an unfinished project. A resume can demonstrate judgment through accurate delivery claims and thoughtful measurement boundaries, even before the final outcome is available.