SousMeow
Design & Brand Intermediate Available now Free

Critique a Screen

Critique one screen with clear findings and next fixes.

A useful screen critique stays close to what is actually visible. This Cookbook helps you frame the user goal, describe the screen, list clarity and friction findings, prioritize fixes, write fix notes, and package a plain critique memo. Prompts separate observations from assumptions so the critique does not invent user data.

Made for
Designers, founders, and product teams reviewing one screen before changing it
You leave with
screen frame, visible description, clarity findings, friction findings, prioritized fixes, fix notes, and critique memo
Time
about 40 minutes
Steps
7 guided steps
Requires
any AI you already use (a free chat account is usually enough); sample answers included where available
Completed runs
143 (demo metric)
Average rating
4.6 / 5 (demo metric)

Also in Start Here Selected by SousMeow Recently Added Deep Workflows

Start free to begin

Have an account? Sign in.

Stages

3 stages in sequence
  1. 1

    Frame

    Name the user goal and describe only what is visible.

    2 steps
  2. 2

    Findings

    List clarity and friction findings grounded in evidence.

    2 steps
  3. 3

    Fixes

    Prioritize fixes, write notes, and package the memo.

    3 steps

Workflow steps

7 steps · completed in order

Stage 1: Frame

  1. 1

    Name the user goal

    Frame the screen around the real user goal and success condition.

    A critique without a goal becomes personal taste. The user goal makes findings testable.

    • Goal is user-centered The goal says what the user is trying to do.
    • Success is plain Success is observable in the screen experience.
    • Evidence boundary is explicit The critique will not invent user data.
  2. 2

    Describe the screen

    Write a neutral description of what is visible and what is not known.

    Observation comes before judgment. This step keeps later findings anchored to the real screen.

    • Description stays neutral Visible elements are described before judgment.
    • Missing evidence is named Unknown states are not assumed.
    • Lens ties to goal The critique lens matches the approved user goal.

Stage 2: Findings

  1. 3

    List clarity findings

    Identify where copy, labels, or states may be hard to understand.

    Clarity findings show what the screen needs to explain so users can act with confidence.

    • Findings are about clarity Each finding concerns understanding, labels, or state.
    • Evidence is visible The support comes from the screen description.
    • Questions do not masquerade as facts Unknowns remain questions.
  2. 4

    List friction findings

    Identify where the screen may slow, worry, or block the user.

    Friction findings connect the visible screen to the user's next action without claiming unseen behavior.

    • Findings name friction Each finding addresses possible effort, worry, or blockage.
    • Evidence stays supplied Findings cite visible or provided friction only.
    • Assumptions are blocked Unseen behavior is named as not assumed.

Stage 3: Fixes

  1. 5

    Prioritize fixes

    Choose the first fixes based on goal impact and constraints.

    Prioritizing prevents the critique from becoming an unranked list of possible changes.

    • Fixes are ranked The recommendations have an order.
    • Order follows goal impact The rationale connects fixes to the user goal.
    • Constraints are respected Tradeoffs acknowledge limits instead of ignoring them.
  2. 6

    Write fix notes

    Turn priorities into specific copy, layout, and validation notes.

    Fix notes make the critique actionable while staying inside known constraints.

    • Notes are concrete The fixes include specific wording or placement guidance.
    • Validation is goal-based The check asks whether the user goal is clearer.
    • Constraints remain intact The fix does not expand scope silently.
  3. 7

    Pack critique memo

    Assemble the screen critique into a plain memo with findings and next fixes.

    The memo gives teams a shared record of what was observed, what matters, and what to try next.

    • Memo stays evidence-based The summary does not add user data or unseen behavior.
    • Findings are summarized Clarity and friction issues are easy to scan.
    • Next check is actionable The follow-up can be used to review the revised screen.

Your information

7 details, answered once
  • Screen name Name the exact screen being reviewed.
  • Product context What product is this in, and what part of the product does the screen support?
  • User goal What the user is trying to do on this screen. Known goal only.
  • What you see Describe visible elements, labels, controls, and copy. Avoid interpretation.
  • Known friction Known concerns, feedback, or suspected problems. If unknown, say unknown.
  • Constraints Design, product, engineering, or content constraints already known.
  • Success looks like What a better screen helps the user understand or do.

Finished files

What you export when every step is approved

One Markdown file per approved step, plus kit.html (opens in any browser, offline) and a README of what you approved.

  • kit.html Offline HTML reader for every approved step
  • 01-name-the-user-goal.md Name the user goal
  • 02-describe-the-screen.md Describe the screen
  • 03-list-clarity-findings.md List clarity findings
  • 04-list-friction-findings.md List friction findings
  • 05-prioritize-fixes.md Prioritize fixes
  • 06-write-fix-notes.md Write fix notes
  • 07-pack-critique-memo.md Pack critique memo
  • README.md Manifest of what you approved
Nearby guided projects you can start next
Design & Brand Available Name Your Brand Voice Define a brand voice you can reuse in every sentence. 7 steps · 30 min · Beginner · 4.8 ★ · Free