AI Builder Readiness
A short self-reflection on how you build with AI tools: how clearly you prompt, whether you plan where the output goes next, and how you check it before use.
Persona test · Perception
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
3 patterns, each a scale between two named ends. Neither end is better: each describes a way of working.
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
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.
Whether you bring in visual detail early or settle a screen's hierarchy before you style it.
Feeds the skill Communication
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.
Whether you want a fixed brief before you design or start exploring directions while the brief is open.
Feeds the skill Learning agility
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.
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.
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.
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.
For product, UX and UI designers, design students, and developers, product managers or founders who design their own screens.
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.
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.
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.
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.
About 4 minutes. The twelve questions appear one at a time, and every answer is kept, so you can leave partway and finish later.
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.
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.
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.
Persona test · About 4 minutes
Design Thinking Style