Problem–solution writing: defining the problem and testing remedies

Problem–solution writing makes a case for a change by connecting a clearly defined difficulty to a response that can plausibly improve it. The form appears in proposals, policy briefs, workplace memos, and essays. Its strength is not the neatness of a two-part outline. A persuasive piece identifies who experiences the problem, shows how it arises, weighs alternatives, and explains what evidence would count as success. Otherwise the proposed remedy can sound appealing while failing to address the actual cause.

Suppose a university reports long waits for academic advising. A writer might immediately propose hiring more advisers. That may help, but the wait could also reflect a scheduling system that sends every routine question to a specialist or a seasonal surge before registration. A better argument measures the wait, distinguishes kinds of appointments, and checks whether available capacity is used where students need it. The proposed solution can then match the mechanism rather than the most visible symptom.

Define the problem in problem–solution writing

Name the affected group, the setting, the size of the gap, and the standard against which it is judged. “Advising is bad” gives a reader little to evaluate. “First-year students wait twelve days on average for a course-planning appointment during registration, while the university’s stated target is five days” identifies a measurable difference. If the numbers are unavailable, say so and propose a reasonable way to collect them rather than inventing precision.

Explain why the audience should care. Students may miss course choices; advisers may spend time correcting rushed decisions; administrators may face a cost when delayed advice extends time to degree. Each audience needs different evidence and has different authority to act. A department chair could change scheduling rules but might not approve a new institution-wide budget. The writer’s proposed action should fit the decision maker’s scope.

Define terms that could hide disagreement. Does “wait time” start when a student requests any meeting, or when they request a particular adviser? Do same-day drop-in visits count? A problem statement built on an ambiguous measure can produce apparent improvements that students never experience.

Investigate causes before selecting a solution

Separate evidence of harm from evidence of cause. A survey showing dissatisfaction tells us that a problem may exist; it does not show whether staffing, appointment length, inaccessible booking hours, or confusing guidance drives the delay. Compare appointment logs, repeat visits, peak periods, cancellation rates, and interviews with students and staff. Look for patterns that can discriminate among explanations.

In the advising example, appointments might be booked solid for two weeks, suggesting a capacity constraint. Alternatively, half of reserved sessions might be abandoned because reminders fail, suggesting an access problem. A single average hides important variation: students with urgent financial aid questions could wait much longer than those choosing electives. Ask who is least well served before treating a general improvement as sufficient.

Avoid turning an individual account into a universal claim. A vivid student’s story can show why a delay matters and what it feels like, but the scale of the problem needs broader evidence. Equally, an aggregate statistic can conceal practical barriers. Use both kinds of evidence for the jobs they can actually do.

Compare remedies with stated criteria

Generate more than one plausible response. The university could add temporary appointments at peak times, route routine questions to well-trained general advisers, improve self-service guidance, adjust booking rules, or hire permanent staff. Each option has costs and possible unintended effects. Automated guidance could shorten simple visits while confusing students with complex circumstances; extra appointments could appear only during hours many students cannot attend.

Set criteria before declaring a winner. Consider expected reduction in waiting, access for students who need accommodations, staff workload, cost, implementation time, and the risk of incorrect advice. A small table in a proposal can show which evidence informs each criterion and where the writer is uncertain. If a solution wins only because the writer ignored its implementation cost, readers should see that omission.

The strongest choice can be a staged response. Pilot a new triage process in one faculty during a registration period, reserve rapid appointments for urgent cases, and collect data about rebookings and errors. Expand only if the observed improvement survives the pilot and does not transfer the burden to another queue. A proposal should tell readers what would make the team revise or abandon the idea.

Build an argument from evidence to action

An effective structure follows the reader’s questions: What is happening? Why is it happening? What options are available? Why choose this one? How will it work? What could go wrong? The introduction can briefly preview the recommendation, while the body earns it through evidence. A paragraph describing the remedy belongs after the reader understands the cause it addresses.

Use transitions to show the reasoning. “Because most delays occur before registration, year-round staffing alone may use funds inefficiently” explains why an observation changes the recommendation. “However, the same logs miss students who gave up trying to book” signals a limitation. These connections matter more than a formulaic sequence of “first,” “second,” and “finally.”

Represent counterarguments fairly. An administrator concerned about cost may be right to demand a budget; a student concerned about privacy may reasonably reject a tool that exposes sensitive information. Respond with a cost comparison, a privacy design, a narrower pilot, or a concession that the proposal must be modified. Dismissing objections weakens credibility because those objections often identify conditions for success.

Specify implementation and success measures

Name the responsible people, resources, sequence, and evaluation period. A proposal to change advising might specify who trains triage staff, who owns the booking rules, how students can reach a human when a question is complex, and how complaints are escalated. A clear plan makes the recommendation possible to assess even if the reader eventually chooses another option.

Choose outcome measures that correspond to the original problem. Median and long-tail waits, missed appointments, accuracy of guidance, and students’ ability to obtain required courses may tell a richer story than a single satisfaction rating. Record a baseline, compare similar periods, and check whether groups with the longest initial waits benefit. If the intervention improves the headline average but leaves urgent cases stranded, it has not solved the stated issue.

Problem–solution writing ends with a conditional, testable recommendation. It gives the reader a reason to act now, a way to implement the change, and a reason to revisit it when new evidence arrives. The form works best when the proposed action follows visibly from the problem rather than being a solution searching for one.