Writing Better Project Briefs with the STAR Method.

STAR project brief concept: Situation, Task, Action, Result arranged as a simple process

A well-written project brief can make or break a design engagement. Done poorly, it’s a loose checklist of features. Done well, it’s a story that aligns teams, clarifies goals, and keeps everyone focused on outcomes.

One framework that works brilliantly for briefs is the STAR method. It’s usually taught as an interview technique, but its structure maps perfectly to product and UX work.

Why Use STAR for Project Briefs?

The STAR method — Situation, Task, Action, Result — is simple, memorable, and outcome-focused. It forces clarity and makes success measurable.

  • Situation grounds the project in context.
  • Task defines the objective.
  • Action outlines how the team will approach it.
  • Result sets expectations for success.

Breaking Down STAR for Briefs

  1. 1. Situation

    Describe the current state and what triggered the project. Be specific and evidence-led.

    Example: “Our e-commerce platform sees high traffic but a 60% checkout abandonment rate on mobile.”

  2. 2. Task

    Clarify the problem to solve and the objective to achieve. Keep it outcome-oriented.

    Example: “Reduce abandonment by improving the mobile checkout experience.”

  3. 3. Action

    Outline the approach, methods, and scope. Name the levers you’ll pull.

    • Run usability tests on the current flow
    • Simplify form fields and error handling
    • Prototype a mobile-first, two-step checkout
    • A/B test shipping/payment variations
  4. 4. Result

    Define success with measurable targets and timeframes.

    Example: “Increase completed checkouts by 15% within three months of launch.”

A Simple STAR Brief (End-to-End)

Here’s how a content redesign brief might read using STAR:

  • Situation: “The blog attracts readers but converts poorly to newsletter sign-ups.”
  • Task: “Increase blog-to-newsletter conversion.”
  • Action: “Redesign the template to surface CTAs, add contextual prompts, and A/B test sign-up flows.”
  • Result: “Increase sign-ups by 25% in the next quarter.”

Why This Works

Using STAR stops briefs from being vague (“make the site better”) and reframes them as a narrative with context, approach, and measurable outcomes. It also helps stakeholders see the value of design in business terms.

Call to Action

Next time you’re writing or reviewing a project brief, try STAR. You’ll create alignment faster, set clearer expectations, and ship work that’s easier to measure.