Skip to content
Anslation

Persona test · Perception

Design Thinking Style test

Design Thinking Style is a short self-reflection test on three habits in design work, not on design knowledge. Twelve statements place you on noticing where a user may hesitate, settling a screen's hierarchy before its visual detail, and exploring while a brief is still open.

You sign in or create an Anslation account to take it; your answers save as you go.

By Anslation Editorial Team · Page updated · How scoring works

At a glance

Who it is for
Product, UX and UI designers, design students, and developers, product managers or founders who design their own screens
Time
About 4 minutes
One question at a time
Questions
12 questions
One at a time
What you get
Where you sit on 3 patterns
A band for each, and practice steps in Grow
Account
Needed for a scored result
Your answers save as you go
Try first
Preview the first questions without an account
Nothing is scored

What it looks at

3 patterns, each a scale between two named ends. Neither end is better: each describes a way of working.

  • Friction Sensing

    Whether you call a screen done once its main action works or look for the places a user may hesitate.

    Feeds the skill Analytical thinking

    What the 3 Friction Sensing bands mean

    Toward the high end, people tend to notice the moments a user may stall before finishing an action, such as an icon with no label, a field that asks for more than it needs or an error message that does not say what to do next. That can catch snags early, though the list of fixes can outgrow the time available. Toward the low end, people tend to confirm the main task can be completed and call the screen done. That keeps each screen quick to finish, but small points of hesitation can reach users before anyone on the team sees them.

    Checks that it works
    You tend to accept a screen as fine when its main action works, which keeps work moving but can leave the places where users hesitate unnoticed.
    This week, ask one person to complete a task on a screen you made, and note every place they pause or reread.
    Watches the key steps
    You catch where a user might hesitate on the steps that matter most to you, and let the rest go once they work.
    Pick one screen you rarely revisit, such as settings or an error state, and list each point where someone could get stuck.
    Looks for hesitation
    You tend to look past whether an action works to where someone might stall, such as a vague button or an extra step. That can surface problems before users meet them, though not every snag is worth the time it takes to fix.
    Sort the snags you find on one screen by how often users are likely to meet them, and fix the most common one first.
  • Visual Order

    Whether you bring in visual detail early or settle a screen's hierarchy before you style it.

    Feeds the skill Communication

    What the 3 Visual Order bands mean

    Toward the high end, people tend to settle what matters most on a screen, group and space elements to match, and add colour or imagery only once that order holds. Their screens are usually easy to scan, though they can feel plain. Toward the low end, people tend to bring in visual detail while the layout is still moving. That can set a product's mood early on, but the next action can get lost, and some detail may need redoing once the hierarchy settles.

    Adds detail early
    You often reach for colour, imagery or decoration before the hierarchy is stable. That can give early drafts a distinct feel, but the next action may be hard to pick out.
    Before you style your next screen, lay it out in grey boxes and check that the next action stands out.
    Sets the main order
    You usually decide what a screen shows first and what comes next, though some detail goes in before that order is fixed.
    For one screen this week, write down what a user should see first, second and third, then check the design against it.
    Hierarchy before detail
    You tend to fix the hierarchy and scan path before any styling, so the next action is easy to find. Holding to that order can make a bolder layout harder to try.
    Make one deliberately expressive version of a finished screen, and keep any idea that leaves the scan path clear.
  • Ambiguity Play

    Whether you want a fixed brief before you design or start exploring directions while the brief is open.

    Feeds the skill Learning agility

    What the 3 Ambiguity Play bands mean

    Toward the high end, people tend to start sketching before the brief is settled and explore more than one direction before picking the cleanest. That widens the choice, though a decision can arrive later than the people waiting on it would like. Toward the low end, people tend to want the problem, constraints and goals fixed before design work starts, then take one direction forward. That keeps effort on the stated problem, but in open early work it can mean waiting for answers that a rough sketch would draw out.

    Starts from a brief
    You prefer a fixed brief before you start designing, and often follow one direction rather than several. That gives your work a clear target, but it can slow the unclear start of a project.
    When your next brief is vague, sketch two rough directions and use them to ask what the brief leaves open.
    Explores once framed
    You try a few directions once a problem has some shape, but want firmer edges before starting on work that is wide open.
    Next time a task feels too open, write a one-line problem statement yourself and start sketching from it.
    Tries several directions
    You can start without a fixed brief and tend to try several directions before settling on the cleanest. That keeps more options in play, though exploring can run past the point where a choice is needed.
    Before you start exploring on your next project, set the day you will choose a direction, and tell whoever is waiting on it.

About this test

Design Thinking Style is a self-reflection test about three habits in design work: noticing where a user may hesitate, building a clear order into a screen, and working while a brief is still open. You rate twelve statements about what you usually do on real projects, from strongly disagree to strongly agree. Each pattern runs between two named ends, such as starting from a brief and trying several directions, and the result marks your position on each with a band named in the test's own words.

Read more about this test

It suits product, UX and UI designers, design students, and the developers, product managers and founders who design their own screens. It asks about habits rather than your knowledge of the design thinking process, so there is nothing to study first. Neither end of a pattern is better. Waiting for a fixed brief can save rework, and adding detail early can give a team something concrete to react to, but each habit has a cost too.

Use the result to choose one small experiment for your next project, such as showing a colleague a screen for a moment and asking what they noticed first. It reflects your own view of how you work today, so a new team, a tighter deadline or some practice can shift it. It says nothing about how good a designer you are and should not be used for hiring, promotion or portfolio reviews.

What you will answer

The test asks 12 questions, one at a time. Answers are saved as you go. The examples below are answered on a 5-point scale, from "Strongly disagree" to "Strongly agree".

  • Friction Sensing

    I notice where a user may hesitate before they complete an action.

  • Visual Order

    I organise a screen so the next action is easy to find at a glance.

  • Ambiguity Play

    I try several directions before I choose the cleanest one.

Examples from this test, shown as text. There are no right or wrong answers.

What you get

A result is a map of your patterns, not a type or a label.

  • Where you sit on Friction Sensing: how readily you notice where a user may hesitate.
  • Where you sit on Visual Order: adding visual detail early, or settling the hierarchy first.
  • Where you sit on Ambiguity Play: wanting a fixed brief, or exploring while it is still open.
  • A band for each pattern, named and described in this test's own words.
  • Practice steps in Grow, picked by fixed rules, and an optional share link that shows band names only.
Anslation Persona · Design Thinking StyleSample
Sample: a result places you on each pattern's scale and names the band you are in. The dots here are an illustration, not anyone's answers. Sample rows: Friction Sensing: Watches the key steps; Visual Order: Hierarchy before detail; Ambiguity Play: Starts from a brief.

Who it is for and your answers

Who it is for

For product, UX and UI designers, design students, and developers, product managers or founders who design their own screens.

Your answers and your result

  • Before the first question, you are asked to agree to how your answers are used.
  • A completed result is visible to you and to Persona managers, who can also open your answers in Persona's data tables.
  • A share link is your choice: it shows the test, when you took it, your headline and the band you fall in on each pattern, never your answers, positions or scores, and every link expires.
  • Managers see group figures only once at least 5 people have results, and never a ranking of people.
  • How long each answer takes is recorded, to find questions that are hard to answer.
What you agree to before the first question
I understand this is a self-reflection exercise about my design habits, not a diagnosis or a hiring decision. I agree to my answers being saved to build my result, and to the time each answer takes being recorded to find questions that are hard to answer. People with Persona manager access can open my answers and my result in Persona's data tables.
Self-insight, not a diagnosis or a hiring decision.

Sharing a result safely

Is this test accurate?

It is a self-report: it shows how you see your own habits today, not how others see you, so read it as a starting point. Persona publishes no accuracy or reliability figure for any test. These are the rules this one follows.

  • ConfidenceAnswer at least 11 of its 12 questions for Strong confidence, and at least 6 for Moderate; fewer reads Limited. It says how much a result rests on, not whether it is right.
  • Band edgesEvery pattern: 0–34, 35–65, 66–100. A position between two bands takes the nearer one, and exactly halfway goes to the higher band. Neither end of a scale is better.
  • Enough questionsA test page goes into search only when the test has at least 6 scored questions; this one has 12.
  • Reliability checksOnce 10 people have answered every question, Studio checks how well each pattern's questions agree (Cronbach's alpha). Persona publishes no reliability figures.
  • Version 2Published 10 Nov 2026. A result keeps the scoring of the version it was taken on.

Questions about this test

What is a design thinking style test?

It is a short self-reflection on how you work as a designer, with no right or wrong answers. In this test, the three patterns are how readily you notice where a user may get stuck, whether you settle a screen's hierarchy before adding detail, and whether you can start before a brief is fixed. You see where you sit between the two ends of each, so the result shows patterns, not labels.

Does this test check what I know about design thinking?

No. There are no questions about the stages of design thinking or any other method. It asks what you usually do in your own projects, for example whether you explore several directions before choosing one, or call a screen finished as soon as its main action works.

How long does the Design Thinking Style test take?

About 4 minutes. The twelve questions appear one at a time, and every answer is kept, so you can leave partway and finish later.

Do I need an account to take the Design Thinking Style test?

Yes. A scored result needs an Anslation account, and your answers save as you go, so you can stop and come back. Each of your three design patterns then gets a band named in this test's own words.

Who can see my result?

Your result is visible to you and to people with Persona manager access, who can open a completed result. Nobody outside Persona sees it unless you choose to share it. A link you share carries your band names, never your answers, and stops working once it expires or is turned off. Team figures need at least 5 people besides the person reading them, and nobody is ranked.

How should I use my result in my design work?

Pick the pattern that matters most on your current project and change one habit for a week, such as reading every label on your next screen as someone new to the product would. Neither end is the goal: notice what your habit gives the work and what it costs. After a few weeks, take the test again and compare.

Take Design Thinking Style. About 4 minutes, one question at a time. Your answers save as you go.

Persona test · About 4 minutes

Design Thinking Style

Start the test