The starting point is a concrete problem of understanding
Comprehensible content is often justified with general advantages: more satisfaction, fewer questions and greater reach. These statements may be true, but are not sufficient for an investment decision. Managers need to know where the problem occurs and who it affects. An application with many incorrect submissions provides a clearer starting point than a blanket statement that the entire website is too complicated.
Describe the task involved from the reader's perspective. Do people not find a prerequisite, do they misunderstand a technical term or do they not know what happens next after reading? Add what consequences arise from this. This could be an aborted process, unnecessary contact or the loss of a claim. This makes it understandable why linguistic quality has an operational and social impact.
Limit the first case to an important, observable area. A complete overhaul of all content seems big, but is difficult to connect to a single problem. A prioritized service, a frequently used form or a series of customer communications creates a comprehensible connection. This area can be learned from later without promising benefits for every side right from the start.
Today's situation requires more than individual complaints
Collect existing clues about the problem. Support requests, abandonments, incorrect forms, long processing times and recurring complaints can show where content isn't working. However, numbers alone rarely explain the cause. A high abandonment rate can also arise from a technical error or an inappropriate prerequisite. Therefore, supplement data with conversations and observations of actual usage.
Distinguish direct evidence from conjecture. If 300 queries concern the same unclear term, the connection is clearly visible. If managers just assume that better copy will generate more sales, that assumption needs to be tested. An honest starting point does not weaken the business case. It shows where a limited experiment should provide new insights.
Pay attention to people who remain invisible in general metrics. If you don't start a process at all, it may not appear to be aborted. People with learning difficulties or poor language skills may turn to family members instead of support. Target group discussions and tests therefore supplement operational data. They make it clear whether a seemingly small number masks a significant access problem for a particular group.
The proposed improvement must directly address the problem
A business case should not stop at the diagnosis. He must explain what change is planned and why it can help. If readers miss prerequisites, a clear heading, better ordering, and concrete examples can be useful. However, a translation into other languages does not solve a problem that arises from hidden information in the source language.
Choose the language form based on the intended readership. Simple language can improve the common main version for a wide audience. Easy language offers people with a significant need for understanding their own access and requires appropriate technical and target group-specific testing. Standard language can remain correct for a familiar specialist audience. The investment should serve real needs and not just introduce a known method.
Also describe what remains unchanged. Understandable texts do not fix a faulty form, a lack of service or difficult to reach support. If several causes interact, they must either be dealt with together or taken into account in anticipation. A close connection between problem and action prevents the language revision from later being held responsible for outcomes that it alone could not influence.
Benefits arise via a comprehensible impact path
There are several steps between a clearer text and an organizational result. Readers must find the information, understand it correctly and act accordingly. Only then can fewer questions or errors arise. Write this connection in simple sentences. The more unsubstantiated jumps are necessary, the less certain the claimed effect is and the more important practical testing becomes.
An example: A reorganized appointment page lists required documents early and clearly. More visitors bring complete documents with them. This means that appointments have to be repeated less often and employees spend less time making additional requests. Every connection can be observed. On the other hand, the statement that understandable language automatically improves the reputation of the entire organization would be much more distant and more difficult to clearly prove.
Consider alternative explanations. If the form is simplified, a campaign is launched and more staff are deployed at the same time, a change cannot be attributed to the text alone. This does not mean that several improvements must be avoided. The business case should only openly show which effects arise together and where an exact allocation is not possible.
Not every valuable advantage has to be converted into euros
Some benefits can be approximated financially. Fewer avoidable contacts can free up working time, and fewer incorrect applications can reduce follow-up work. Time released does not automatically translate into household savings. It only becomes a financial benefit when expenses actually decrease. Often the honest advantage is additional capacity for more complex cases or shorter waiting times.
Other effects are important in their own right. Better access to rights, greater independence and less stress cannot be meaningfully reduced to a monetary amount. Managers should visibly consider such results alongside financial impacts. Public and social offerings in particular pursue tasks whose value lies in fair access and correct use. Artificial conversion can distort rather than strengthen this meaning.
Risk avoidance also belongs in its own picture. A clear security warning can prevent a serious error that occurs rarely and cannot be reliably calculated as an average amount. Carefully describe the likelihood, possible consequence, and contribution of the more understandable information. Avoid claiming that the intervention completely eliminates a risk when technology, behavior and support still play a role.
Assumptions should remain visible and testable
Every future estimate contains assumptions. How much content is actually revised, how many people use it and what proportion of questions are related to comprehensibility? Write these sizes down with their origin. Observed data, empirical values and pure estimates should be distinguishable. This allows decision-makers to identify which parts of the case are resilient and which are particularly sensitive.
For uncertain assumptions, use a plausible range. If between ten and thirty percent of contacts could be avoidable, a single average shows false precision. Consider whether the investment remains sensible even with a cautious assumption. A case that appears positive only under the most optimistic combination needs further evidence or a smaller first step.
Beware of benefits counted multiple times. The same processing hour saved cannot be fully added up as lower costs, additional capacity and faster service. Choose the effect that is actually expected or show alternative uses. This clarity prevents inflated amounts and makes subsequent reports of realized benefits much more credible.
A limited experiment can provide crucial evidence
If the initial situation is uncertain, a limited experiment with important content is advisable. Choose an area with sufficient usage and a clear problem. Before making the change, capture how people accomplish the task and observe the same characteristics afterward. The experiment should run long enough so that random fluctuations and special weeks are not confused with an effect.
Combine usage data with direct testing. A declining abandonment rate indicates a change, but does not explain whether readers understood terms correctly. Give people from the target group specific tasks and have them explain their decision in their own words. This makes it clear which formulation helps and where dangerous misunderstandings remain despite better metrics.
Before you begin, determine what results justify continuing. This doesn’t have to be a rigid success number. A significant improvement in an important task, reasonable editorial effort and no new technical errors can together be convincing. It should also be clear when the measure will be revised or ended. An experiment is valuable if its findings can change a real decision.
The organization must be able to sustain the change permanently
A one-time revision only creates temporary benefits when new content appears again in the old form. The business case should therefore show which skills and responsibilities are necessary. Editorial teams need linguistic orientation, departments need to clarify questions promptly and technical templates should support understandable content. These requirements are part of the investment and not an incidental implementation after the decision.
If there are multiple language versions, additional maintenance is required. If deadlines or requirements change, all affected versions must be updated. Simple language may require another technical and target group-specific examination. Limit the scope so that the organization can reliably keep it up to date. A few important and well-maintained contents are more useful than a large collection, the most accessible versions of which soon become outdated.
External support can supplement a lack of competence, but should not completely replace internal understanding. The organization remains responsible for the content, purpose and publication. Plan which knowledge must remain with your own teams and which services will be purchased sensibly. This means that the improvement survives a change of provider, a new technology or personnel changes without having to start every linguistic decision from the beginning.
Leadership requires a decision with clear boundaries
Summarize the case in such a way that the decision is clear. Which problem should be solved in which area, which groups benefit and what effect is realistic? State the magnitude of the necessary investment and show what uncertainties exist. An extensive collection of positive arguments is less helpful than a clear choice between a limited launch, a wider rollout, or abandonment.
Also show which alternative remains without investment. Perhaps support requests are increasing, important content remains inaccessible to a known group, or employees continue to revise texts individually without a common basis. The comparison should not artificially worsen the current situation. Some problems can be solved with small editorial changes, while others warrant systematic language performance and target group testing.
Assign responsibility for results and learning. Management can release funds, but the editorial team, departments and service must monitor the impact together. A single project leader cannot guarantee that readers understand content. Clear ownership means that someone consolidates decisions, resolves obstacles, and reports openly when assumptions do not materialize or another action is necessary.
Credibility comes from benefits that can later be verified
Once the decision has been made, the same logic should apply to the evaluation. Has the intended content been improved, is it reaching the readers described and are they completing their task correctly more often? Compare results with baseline and take other changes into account. A report that only counts pages produced shows activity but no benefit to people or the organization.
Align expectations with real insights. Perhaps queries are decreasing less than expected, while target group tests show a strong improvement in independence. Maybe the effect is good, but the care is more complex. Such results do not render the original case worthless. They enable better decisions about expansion, different priorities or changed support.
A robust business case does not promise automatic returns through clear words. It connects an observed problem of understanding with an appropriate change, a plausible pathway and testable assumptions. Financial, operational and social benefits remain distinct. In this way, managers can assess understandable content as a concrete improvement to the offer and not just as a general communication ideal.