5.5 Problem-solution

Definition of problem-solution writing

Problem-solution writing is a type of persuasive writing that identifies a specific problem and proposes a way to fix it. Your job is to convince the reader that the issue is real, that it matters, and that your proposed solution is the strongest option available.

This pattern shows up constantly in the real world: business proposals, policy briefs, nonprofit campaigns, opinion editorials. Any time someone says "here's what's wrong and here's how to fix it," they're using problem-solution structure.

Three things define this type of writing:

• A clear problem statement that names the issue directly
• An analysis of the problem's causes, effects, and scope
• A well-argued solution backed by evidence

Purpose and goals

The primary purpose is persuasion. You want the reader to either take action or support a particular solution. But persuasion only works when it's built on substance, so problem-solution writing also needs to:

• Raise genuine awareness about the problem
• Provide a solution that's realistic and well-reasoned
• Drive decision-making in business, social, or political contexts

A vague "we should do something" isn't enough. Your reader should finish the piece knowing exactly what you're proposing and why it's the best path forward.

Key characteristics

• Clear identification and description of the problem
• Analysis of the problem's causes, effects, and significance
• A specific proposed solution (not just a general direction)
• Evidence-based arguments supporting that solution
• Honest consideration of alternative solutions and their drawbacks
• Persuasive techniques used strategically, not manipulatively
• A call-to-action that tells the reader what to do next

Structure of problem-solution writing

Introduction and problem statement

Your introduction needs to do four things:

1. Hook the reader with a compelling opening (a striking statistic, a brief scenario, a provocative question)
2. State the problem clearly and concisely
3. Provide background so the reader understands the context
4. Preview your solution in a thesis statement

The thesis doesn't need to lay out every detail of your solution, but the reader should know where you're headed. For example: "Reducing single-use plastics in campus dining halls would cut waste by an estimated 40% while saving the university money within two years."

Explanation of the problem's significance

This is where you prove the problem is worth caring about. Don't just assert that it's serious; show it.

• Use statistics to quantify the problem's scope (e.g., "Food insecurity affects 1 in 8 households in the U.S.")
• Include examples and expert opinions that illustrate real-world impact
• Analyze the root causes, not just the surface-level symptoms
• Emphasize urgency: why does this need attention now rather than later?

The goal is to make the reader feel that ignoring this problem has real consequences for real people.

Overview of potential solutions

Before arguing for your preferred solution, acknowledge that other approaches exist. This section should:

• Briefly introduce several possible solutions
• Explain how each one would address the problem
• Note the strengths and limitations of each option
• Set up a fair comparison so your recommendation feels earned, not predetermined

Skipping this step makes your writing look one-sided. Readers trust writers who've clearly considered the alternatives.

Evaluation of solution options

Now go deeper. Assess each potential solution against concrete criteria:

• Cost: What resources does it require?
• Feasibility: Can it realistically be implemented?
• Effectiveness: How well does it address the root causes?
• Sustainability: Will it work long-term?
• Risks: What could go wrong?

Be honest about trade-offs. If a solution is cheaper but less effective, say so. This analysis builds your credibility and makes your final recommendation more convincing.

Recommendation of the best solution

State your preferred solution clearly, then support it with:

• A detailed description of what the solution involves and how it would be implemented
• Evidence showing it addresses the problem's root causes
• A discussion of benefits for specific stakeholders
• Concrete implementation steps so the reader can picture how it would actually work

This section should be the most developed part of your paper. If your recommendation feels thin compared to your problem analysis, the piece will fall flat.

Call-to-action and conclusion

End by telling the reader what to do. A strong conclusion includes:

• A specific, actionable request (sign a petition, change a policy, fund a program)
• A brief reinforcement of why the problem demands action now
• A closing that leaves the reader motivated without drifting into vague inspiration

The more concrete your call-to-action, the better. "Contact your city council representative about rezoning" is far stronger than "we all need to do our part."

Techniques for problem analysis

Identifying root causes

The most common mistake in problem-solution writing is treating symptoms as causes. If student test scores are dropping, the problem might not be "students aren't studying enough." It might be overcrowded classrooms, outdated curricula, or lack of access to tutoring.

To find root causes:

1. Start with the visible problem and ask "why does this happen?"
2. For each answer, ask "why?" again. Repeat until you reach underlying factors.
3. Use cause-and-effect analysis or formal root cause analysis frameworks
4. Verify your findings with research and data

Considering multiple perspectives

A problem looks different depending on who's experiencing it. A housing shortage affects renters, landlords, city planners, and developers in very different ways.

• Examine the problem from each stakeholder's viewpoint
• Seek input from experts and people with firsthand experience
• Identify how the problem creates disparities across different groups
• Use these perspectives to build a more complete picture of the issue

Writing that only reflects one perspective will feel incomplete to any reader who sees the issue differently.

Using data and research

Strong problem-solution writing is grounded in evidence. You'll need:

• Statistics and studies from credible sources (government reports, peer-reviewed research, reputable organizations)
• Primary data when possible, such as surveys, interviews, or observations
• Trend analysis that shows whether the problem is growing, shrinking, or shifting
• Data visuals like charts or graphs that make complex information easier to grasp

Data doesn't just support your argument; it shows you've done the work to understand the problem thoroughly.

Developing effective solutions

Brainstorming and ideation

Before committing to a solution, generate as many options as you can. Techniques that help:

• Mind mapping: Start with the problem at the center and branch out into possible approaches
• Freewriting: Write without stopping for 10 minutes about possible fixes
• Combining ideas: Take the strongest elements from multiple solutions and merge them
• Challenging assumptions: Ask "what if we approached this completely differently?"

The point is to avoid locking into your first idea. Your best solution often comes from exploring several possibilities first.

Feasibility vs. impact

Every solution involves a trade-off between what's practical and what's ideal. When evaluating options, consider:

• Feasibility: Can this actually be done given the available budget, time, and resources? What barriers exist?
• Impact: How much of the problem does this actually solve? Does it address root causes or just symptoms?

Sometimes the highest-impact solution isn't feasible, and the most feasible solution barely makes a dent. Your job is to find the best balance and explain why you struck it where you did.

Short-term vs. long-term approaches

Some solutions provide immediate relief; others fix the underlying system. The strongest proposals often combine both.

• Short-term: Quick to implement, addresses urgent needs, but may not last (e.g., emergency food distribution)
• Long-term: Tackles root causes, creates lasting change, but takes time and resources (e.g., job training programs)

Be upfront about which type your solution is. If you're proposing a short-term fix, acknowledge what a long-term strategy might look like. If you're proposing systemic change, explain how to handle the problem in the meantime.

Addressing potential objections

Every solution has weaknesses, and your readers will spot them. Get ahead of this by:

1. Listing the most likely objections (too expensive, too slow, already tried, unintended consequences)
2. Understanding why someone would raise each objection
3. Preparing counterarguments backed by evidence
4. Modifying your solution where valid concerns exist

Acknowledging objections honestly makes your argument stronger, not weaker. It shows you've thought the solution through.

Persuasive strategies in problem-solution writing

Establishing credibility and expertise

Readers won't accept your solution if they don't trust your analysis. Build credibility by:

• Citing reliable, specific sources rather than making unsupported claims
• Presenting a balanced analysis that acknowledges complexity
• Using a confident but measured tone (assertive, not aggressive)
• Demonstrating that you understand the problem deeply, not just superficially

You don't need personal credentials to be credible. Thorough research and fair-minded analysis go a long way.

Appealing to logic and emotion

The most persuasive writing uses both logos (logical reasoning) and pathos (emotional appeal), but in the right balance.

• Logos: Present clear evidence, sound reasoning, and logical connections between your problem analysis and your solution
• Pathos: Use specific stories, vivid descriptions, or moral framing to make the reader feel why the problem matters

Too much logic without emotion feels dry and forgettable. Too much emotion without logic feels manipulative. Aim for evidence that also resonates on a human level.

Rhetorical devices like analogies, metaphors, and brief narratives can bridge the gap between data and feeling.

Anticipating counterarguments

This goes beyond addressing objections to your solution. You should also anticipate arguments that the problem itself isn't worth solving, or that a competing solution is better.

• Present opposing viewpoints fairly before refuting them
• Use evidence and reasoning to show where counterarguments fall short
• Demonstrate that you've genuinely considered other perspectives
• Avoid straw-manning: represent the strongest version of the opposing argument, not the weakest

Using vivid examples and anecdotes

Abstract problems become real when you show their impact on specific people or communities.

• Choose examples that are relevant to your audience (a campus audience responds to campus examples)
• Use case studies that show the problem and solution in action elsewhere
• Integrate examples into your argument rather than dropping them in as decoration
• A single well-chosen example often persuades more effectively than a page of statistics

Adapting to audience and purpose

Analyzing audience needs and expectations

Before you write, answer these questions about your reader:

• What do they already know about this problem?
• What are their likely concerns or biases?
• What kind of evidence will they find most convincing?
• What action are they actually in a position to take?

A proposal to a city council requires different framing than an op-ed for a student newspaper, even if the underlying problem is the same. Tailor your content, tone, and persuasive approach accordingly.

Formal vs. informal tone

Match your tone to the context:

• Formal: Academic papers, policy proposals, professional reports. Use precise language, avoid contractions, maintain objectivity.
• Informal: Blog posts, opinion pieces, advocacy campaigns. More conversational, direct, and emotionally engaged.

Whatever tone you choose, stay consistent throughout the piece. Shifting between formal and casual within the same document is disorienting for readers.

Inspiring action vs. informing decisions

Your purpose shapes how you write the entire piece:

• Inspiring action: Use stronger emotional appeals, paint a clear picture of what success looks like, and end with specific steps the reader can take right now.
• Informing decisions: Present a more balanced analysis, give weight to multiple options, and let the evidence guide the reader toward a conclusion rather than pushing them there.

Most problem-solution writing leans toward action, but know which mode you're in so your tone and structure stay aligned with your goal.

Organizing and structuring content

Linear vs. non-linear approaches

The standard problem-solution structure is linear: describe the problem, then propose the solution, then call for action. This works well for straightforward issues.

For more complex problems with multiple stakeholders or interconnected causes, a non-linear approach can be more effective. You might weave problem analysis and solution discussion together, or organize by stakeholder group rather than by the problem-then-solution sequence.

Whichever approach you choose, the reader should always know where they are in your argument and where you're heading next.

Using headings and subheadings

Headings aren't just formatting; they're navigation tools. Good headings:

• Break content into logical, manageable sections
• Tell the reader what each section covers before they read it
• Use parallel structure (if one heading starts with a verb, the others in that group should too)
• Create a clear hierarchy that mirrors the structure of your argument

Incorporating visuals and graphics

Visuals can make your argument more accessible and more convincing, especially when you're presenting data.

• Use charts or graphs to show trends, comparisons, or scale
• Choose visuals that are clear and directly relevant to your point
• Always label visuals and reference them in the text
• Make sure visuals support your argument rather than cluttering it

Writing effective transitions

Transitions keep your reader moving smoothly from one idea to the next. Without them, even well-organized writing can feel choppy.

• Use transitional words and phrases to signal relationships between ideas (however, as a result, in contrast, building on this)
• Write bridge sentences at the end of paragraphs that connect to what comes next
• Vary your transition types: addition, contrast, cause-effect, sequence
• If you find yourself writing "additionally" for the fifth time, switch it up

Editing and revising techniques

Checking for coherence and clarity

During revision, read your draft with fresh eyes and ask:

• Does each section logically follow from the one before it?
• Does every paragraph support your thesis or purpose?
• Are there any gaps where the reader might get lost or confused?
• Is your language clear and direct, or are you hiding behind vague phrasing?

Reading your draft out loud is one of the fastest ways to catch awkward phrasing and logical gaps.

Eliminating redundancy and wordiness

Problem-solution writing tends to get repetitive because you're circling the same issue from multiple angles. Watch for:

• Sentences that repeat what the previous sentence already said
• Filler phrases like "in order to" (just say "to"), "due to the fact that" (just say "because"), or "it is important to note that" (just state the point)
• Paragraphs that can be combined because they cover the same idea
• Every sentence should earn its place. If cutting it doesn't weaken the argument, cut it.

Proofreading for grammar and style

After revising for content and structure, do a final pass for surface-level errors:

1. Check for grammatical, spelling, and punctuation mistakes
2. Verify consistent verb tenses and pronoun usage
3. Confirm proper citation formatting
4. Use proofreading tools, but don't rely on them entirely; read through manually as well

Seeking feedback and input

Your draft will improve significantly if other people read it before the final version.

• Share with peers who can flag confusing passages or weak arguments
• Seek feedback from people who hold different views on the issue; they'll catch blind spots
• Ask specific questions: "Is my solution convincing?" or "Where did you lose the thread?"
• Revise based on patterns in the feedback. If multiple readers stumble at the same point, that section needs work.