Back to Blog
GoScript Journal

Structuring Your Case Study From Problem To Outcome

·7 min read·GoScript Team /Research

Problem, move, outcome

The simplest structure for a case study video is three parts: the problem, the move you made, and the outcome you measured. Everything else is decoration. If a scene does not serve one of those three, cut it.

I like to map the script on a page before I record anything. Draw three boxes and force every line into one of them. The exercise exposes filler fast, because most of it belongs to none.

Make the problem specific

A vague problem produces a vague video. Instead of saying traffic was low, say the channel was stuck under a thousand views per upload for five months. Specificity gives the viewer something to compare against their own situation.

Name the constraint too. Was it time, budget, skill, or a platform that would not cooperate? A problem with edges is easier to follow than one that floats in the abstract.

Show the move as decisions

The middle should read like a series of choices, not a checklist. For each step, say what you considered and why you picked one path over the others. That reasoning is the part other people can borrow.

Keep the sequence tight. If you made twelve edits, group them into three phases. A numbered list of twelve small actions bores people; three named phases keep the logic visible.

A case study is not a log of everything you did. It is an argument that one path caused one result.

Measure the outcome with a baseline

An outcome without a baseline means nothing. Before the result, state the starting number. After, state the ending number. The gap between them is your evidence, and the gap is what the viewer came for.

Pick one headline metric and let the rest support it. If you lead with five numbers, none of them sticks. One clear figure with two assistants behind it is easier to remember.

Key takeaways

  • Force every scene into problem, move, or outcome.
  • Describe the problem with numbers, constraints, and a time frame.
  • Present the move as decisions, grouped into a few named phases.
  • Always pair the outcome with the baseline it improved on.
  • Lead with a single headline metric instead of a wall of them.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel