Explain what was observed and what was not measured. Use permitted artifacts, documented decisions and completion milestones to show the work, while avoiding invented percentages or causal claims. State the missing baseline and describe a suitable future evaluation as a proposal rather than a result.
Identify what evidence actually exists
Gather the records available from the engagement: agreed drafts, issue logs, review comments, approval notes and handover files. Separate these from impressions remembered afterward. A before-and-after set of documents may show a structural change, while a completion record may show that an agreed deliverable was supplied. Neither automatically demonstrates faster work, greater satisfaction or financial improvement. Start with the evidence you have rather than selecting an impressive result statement and searching for material that seems to support it.
List the outcomes you cannot establish because the baseline or follow-up is missing. You may not know how long the previous task took, how many people encountered the issue or whether the new artifact was used consistently. Keep those unknowns distinct. The absence of one metric does not make every observation worthless, but it limits the claim you can make. A precise account of those limits is more credible than a synthetic percentage based on an informal recollection.
Describe observable changes in the artifact or process
Show a change that a reader can inspect: conflicting instructions were identified, a proposed ownership field was added, or separate drafts were consolidated into an agreed handover. Explain the comparison basis and your role. If a reviewer reported that something was easier to understand, attribute that statement accurately and only with permission. Do not silently convert a participant comment into a general finding about all users or a measured improvement in task performance.
Use wording that separates intention from observation. “The revised outline was designed to make ownership visible” describes a purpose. “The client approved the outline” describes a milestone when documented. “The outline improved productivity” is a different claim requiring relevant evidence. Keep these levels visible in the summary and title as well as the details. A cautious paragraph lower on the page cannot fully correct an opening that announces an unmeasured result as established fact.
Explain how evaluation could be improved
If useful, describe what you would measure in a future engagement. Name the task, the starting observation and the follow-up conditions rather than simply saying you would track success. A documentation review might compare how readers locate a particular instruction before and after revision. The plan should acknowledge recruitment, consent and practical constraints. Do not present a possible evaluation as work that happened, and avoid inventing a target number to make the case feel complete.
Keep the case study’s value focused on the professional work it can demonstrate. Readers can assess how you framed a problem, handled ambiguous evidence and prepared a usable artifact. They should also understand what remains unknown about its impact. If later evidence becomes available and may be published, update the case with its date and context. Do not retroactively imply that a later observation was known when the original decision was made.
Fictional example: reporting an unmeasured guide revision
A fictional writer, Omar, prepares an invented case about reorganizing internal instructions. The available example evidence includes the old outline, an issue log and a revised draft. There is no baseline for time spent locating instructions and no follow-up study. Omar states that limitation instead of estimating a productivity improvement from the reduced number of headings.
The case explains how he grouped duplicate topics and made unresolved ownership visible. Its conclusion describes the completed draft and proposes a future task-based review with actual readers. The example demonstrates an evidence boundary: an inspectable editorial change can be useful to discuss even when its operational impact has not been measured. It does not turn the fictional proposal into a real result.
A checklist for your next step
- Inventory actual project records.
- List missing baseline information.
- Separate intention from observation.
- Avoid invented percentages.
- Label future evaluation as proposed.
Common questions
Can I call a project successful without metrics?
Explain the criterion you mean, such as an agreed handover. Do not let that imply unmeasured user or business impact.
Can a client comment replace a baseline?
It can be attributed feedback when permitted. It does not by itself establish a measured change or a causal relationship.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.