Rob Hope

Evidence in professional documents exists to support evaluation and decision-making. Claims about scope, risk, cost, timing, or outcome require data that can be examined, compared, and challenged.

When evidence is sufficient, reviewers evaluate tradeoffs and conclusions. When evidence is incomplete, review shifts toward clarification, assumption, or delay.

Evidence answers the question “Can we decide?”

Decision-makers look for enough information to make a defensible choice.

A recommendation without evidence requires the reader to supply judgment. Reviewers respond by asking for data, requesting analysis, or deferring the decision.

For example:

“This change will improve reliability.”

This statement defines an outcome but not its extent or impact.

By contrast:

“This change reduced incident frequency from an average of 6 per quarter to 2 per quarter during the three‑month pilot.”

The second statement provides a baseline, magnitude, and timeframe. The claim can now be evaluated.

Ambiguity often appears as specificity

Many statements appear precise without supporting evaluation. The issue is not the absence of data, but the absence of reference.

For example:

“Customer satisfaction increased.”

Increased relative to what metric, over what timeframe, and from which baseline?

Without these references, the magnitude and relevance of the change cannot be assessed. Readers supply assumptions in their place.

Claims that influence decisions require evidence

Statements that affect commitment require supporting evidence.

Claims about cost, risk, customer impact, performance, timelines, or resource requirements determine whether a decision should proceed. Without evidence, reviewers cannot distinguish between necessary action and precaution.

A request to delay a launch requires justification that defines impact, scope, and timing. Without those details, evaluation cannot begin.

Evidence and data serve different roles

Evidence and data are often used interchangeably. They serve different purposes.

Evidence expresses a conclusion in evaluable terms. Data supports that conclusion.

Effective decision documents separate the two:

• Evidence appears in the main body, next to the claim it supports.
• Detailed data—logs, calculations, and methodology—appears in appendices.

For example:

“During the six‑week pilot, error rates dropped from 9.8% to 3.1%, reducing rework by approximately 120 hours per week.”

The appendix contains the supporting logs and methodology.

This structure allows the reader to evaluate the claim without interruption and verify it when needed.

Percentages without context are incomplete

Percentages signal change. They do not define it.

For example:

“Error rates decreased by 30%.”

A reduction from 10% to 7% differs materially from a reduction from 0.3% to 0.21%.

A complete statement includes baseline and timeframe:

“Error rates decreased from 10% to 7% over six weeks after deployment.”

The impact can now be compared and assessed.

Timeframes define trends

Evidence requires time to establish meaning. Statements that omit timeframe describe change without duration.

For example:

“Throughput improved after the rollout.”

This does not indicate whether the change was immediate, sustained, or temporary.

A defined statement provides context:

“Average throughput increased from 120 to 165 requests per second over the four weeks following rollout.”

Timeframes distinguish transient effects from sustained improvements.

Consistent metrics support comprehension

Inconsistent metrics increase interpretive work.

For example:

“Bug volume dropped by 18%. Support tickets fell from 2,400 to 1,900. User complaints declined.”

Each statement uses a different unit and level of specificity. The reader must reconcile scale.

Consistent presentation reduces that work. Metrics align on unit, timeframe, and level of precision. Raw values and percentages are provided together where scale matters.

Consistency allows comparison without reconstruction.

Evidence should match the decision

The level of evidence required depends on what is being decided.

A low-impact change requires limited support. A multi-quarter investment requires clear baselines, quantified outcomes, and consideration of alternatives.

For example:

“This change will significantly reduce operational risk.”

This statement defines an intent but not an outcome.

A defined version states:

“This change removes manual reconciliation for high-risk transactions, reducing monthly audit findings from an average of 12 to fewer than 3.”

The claim can now be weighed against cost and effort.laim directly to measurable outcome. Reviewers can now assess whether the benefit justifies the cost.

Evidence includes method

When claims influence investment or resourcing, the method matters.

For example:

“Load testing confirms the system can handle peak traffic.”

This states a result without context.

A defined statement provides conditions:

“Load testing using six months of production traffic patterns confirms the system sustains peak loads of 10,000 requests per second with p95 latency under 300ms.”

The reader can assess reliability based on how the measurement was produced.

Lack of evidence shifts decisions towards risk

When information is missing, reviewers assume risk.

Evaluation requires comparison. Without evidence, comparison cannot occur. Decisions slow while missing information is gathered or assumptions are made.

Providing evidence early allows review to focus on tradeoffs rather than discovery.

Evidence enables productive disagreement

Evidence defines disagreement.

When claims are measurable, reviewers can challenge assumptions, question methodology, and evaluate conclusions directly.

Without evidence, disagreement centers on confidence or interpretation. Resolution requires additional data before progress can continue.

Evidence structures discussion.

Evidence supports accountability

Measurable claims define outcomes that can be tracked.

When outcomes are explicit, commitments can be verified. Post-decision review becomes possible.

Qualitative claims diffuse accountability. Measurable claims make follow-through observable.

This visibility reinforces trust across decisions.

Treat evidence as part of the decision path

Evidence belongs at the point where decisions are evaluated.

When claims and evidence appear together, readers assess argument and data as a single unit. When they are separated, evaluation is delayed.

Integrating evidence into the reasoning path ensures that available data informs the decision being made.

Hopeful Writing is about writing documents that work—the kind that lead to clear decisions, shared understanding, and effective execution. It presents practical guidance grounded in expert feedback across real business documents. The result is a systematic approach to writing that prioritizes usefulness over polish.

Some words sound substantial until you ask what they mean. When examined, they provide no verifiable claim, no measurable change, and no basis for evaluation.

These are commonly called weasel words. They create the appearance of meaning while avoiding commitment to a specific claim.

In professional documents, their effect is consistent. They slow decisions, weaken trust, and obscure performance.

What weasel words do

A weasel word allows a sentence to sound informative while avoiding commitment to facts. It creates the impression of progress, success, or improvement without stating what changed, by how much, or relative to what baseline.

When examined, the claim cannot be evaluated.

For example:

“The team made tremendous progress this quarter.”

The sentence signals a positive outcome. It does not define one.

Progress relative to what? Time? Cost? Quality? Without a reference point, the statement provides no measurable information.

Why “significant” rarely is

“Significant” is one of the most common weasel words in professional writing.

Consider:

“We observed a significant improvement in performance.”

The word suggests magnitude without defining it. An improvement of 1% and an improvement of 80% can both be described as significant in casual use. Without baseline, magnitude, and timeframe, the reader cannot assess impact.

This form of language often appears credible because it resembles statistical terminology. In practice, it substitutes for it.

Readers must request clarification before they can evaluate the claim.n effort to extract the information the sentence avoided stating. This undermines trust and credibility.

Narrative claims without evidence

Weasel words appear frequently in narrative framing.

For example:

“We saved the best for last, with our best month in December.”

The statement communicates momentum and confidence. It does not define performance.

“Best” depends on context. Without a metric, timeframe, and comparison, the claim cannot be evaluated. A December result that is lower than the previous year may still be described as “best” within a limited frame.

Narrative without reference points introduces ambiguity into interpretation.

Why weasel words appear

Weasel words reduce immediate friction.

They allow writers to describe direction without defining outcomes. They delay commitment when results are incomplete or uncertain. They avoid conflict by postponing discussion about magnitude, tradeoffs, or performance.

This flexibility makes them easy to use.

It also shifts the work of interpretation to the reader.

Over time, readers learn which statements can be evaluated and which cannot. Language that cannot be tested loses influence, regardless of intent.

How weasel words affect decisions

In documents seeking alignment or approval, evaluation depends on comparison.

Decision-makers assess magnitude, risk, and trajectory. Statements such as “tremendous progress” or “significant improvement” do not provide enough information for that comparison.

Evaluation stops until clarification is provided.

Repeated cycles of unclear claims and follow-up questions increase review time and reduce confidence in the document.

Replace ambiguity with specificity

Eliminating weasel words increases precision.

For example:

“We made tremendous progress.”

can be expressed as:

“We reduced processing time from 45 minutes to 18 minutes by automating three steps in the workflow.”

The revised statement defines the change, provides magnitude, and enables validation.

Similarly:

“We saw a significant increase in adoption.”

becomes:

“Weekly active users grew from 12,000 to 19,000 over six weeks after the rollout.”

And:

“December was our best month.”

becomes:

“December revenue reached $4.2M, 12% above November and 8% below December last year.”

Each version allows the reader to evaluate the claim directly.

Treat weasel words as signals

Weasel words indicate missing information.

They often appear where:

• data is incomplete
• baselines are unclear
• magnitude has not been defined
• confidence exceeds available evidence

Replacing them requires resolving those gaps.

The result is language that reflects measurable reality and supports comparison.

Hopeful Writing is about writing documents that work—the kind that lead to clear decisions, shared understanding, and effective execution. It presents practical guidance grounded in expert feedback across real business documents. The result is a systematic approach to writing that prioritizes usefulness over polish.

Active and passive voice are often introduced as grammatical concepts. In professional documents, voice carries meaning beyond grammar. It signals ownership, level of commitment, and whether an action will happen.

Voice also determines whether responsibility is visible.

Documents depend on language to express ownership and commitment. Active voice is one of the most direct ways to make that explicit.

Active voice assigns responsibility

A sentence is in active voice when the subject of the sentence performs the action. For example:

“The platform team will deploy the new service in Q3.”

The actor is explicit. The action is clear. The timing is stated.

Active voice answers three questions at once: who is acting, what they are doing, and when it will happen. These elements allow planning, sequencing, and accountability.

This completeness is why active voice appears consistently in effective business documents.

Passive voice removes the actor

A sentence is in passive voice when the action is described without a clear actor. For example:

“The new service will be deployed in Q3.”

The outcome is defined, but responsibility is not.

A single passive sentence may be easy to interpret. Across a document, multiple passive statements introduce ambiguity. Readers cannot determine who owns each commitment. Review shifts toward clarification. Ownership must be established before evaluation can proceed.

In this state, the document describes outcomes without defining who is responsible for producing them.

The “by dolphins” test

A simple way to identify passive voice is to add a “by” phrase.

If the sentence still makes grammatical sense after adding an arbitrary actor, it is passive.

For example:

“The new service will be deployed in Q3.”
→ “The new service will be deployed in Q3 by dolphins.”

The sentence remains structurally valid. The actor can be inserted after the fact. This indicates passive voice.

Compare that with:

“The platform team will deploy the new service in Q3 by dolphins.”

This construction breaks. The actor is already defined, and the sentence does not accommodate an additional one.

Passive voice allows the actor to be optional. Active voice requires it to be explicit.

Why passive voice appears

Passive voice appears for predictable reasons.

It allows outcomes to be described without identifying ownership. It delays commitment when ownership is not yet resolved. It reduces direct attribution in situations with organizational complexity.

These properties make passive voice easier to write.

They also shift responsibility away from the document and into interpretation.

During execution, ownership gaps surface. During review, ambiguity slows evaluation. Readers recognize the absence of ownership even when it is not explicitly called out.

When passive voice is appropriate

Passive voice has a role when the actor is not relevant to the decision.

For example:

“Customer data is encrypted at rest.”

The statement describes a condition. Ownership does not change how the statement is evaluated.

Passive voice is also appropriate in informational contexts where responsibility is not part of the question being answered.

In documents that require alignment or approval, ownership is part of evaluation. In those contexts, passive voice obscures information needed to assess feasibility.

Passive voice in decision documents

In documents seeking approval, reviewers evaluate whether the proposed outcome can be delivered.

For example:

“Integration testing will be completed before launch.”

The statement describes an outcome and a timeline. It does not identify who is responsible for delivering it.

Without that information, reviewers cannot assess feasibility. Questions about ownership, capacity, and coordination are deferred to review.

Active voice provides those answers directly.

Active voice clarifies thinking and supports execution

Converting passive voice to active voice makes ownership explicit.

Changing:

“The migration will be completed by the end of the quarter.”

to:

“The infrastructure team will complete the migration by the end of the quarter.”

introduces an actor, a commitment, and a timeline.

If that information is not known, the gap becomes visible. That visibility is useful. Ownership can be established before the document is reviewed.

Active voice aligns language with how work happens. Actions are taken by people and teams. Documents that name actors allow those actions to be evaluated.

Clarity at the sentence level supports decisions at the document level.

Hopeful Writing is about writing documents that work—the kind that lead to clear decisions, shared understanding, and effective execution. It presents practical guidance grounded in expert feedback across real business documents. The result is a systematic approach to writing that prioritizes usefulness over polish.