Perla › Manifest › a UX designer
Manifesting a UX Designer the redraw after testing
This job is often pictured as one clean, final screen. Most of it is a rough wireframe, a user testing session that reveals what you missed, and the redraw that follows. This script is the redraw, not the polished mockup.
- A full script for a UX designer, written in the present tense and ready to read tonight.
- Shorter versions — one for falling asleep, one for the morning, and one line to carry with you.
- How to use it: Read this before a design critique you're nervous about, or right after a user test surfaces a flaw you didn't expect.
- The common mistake: Polishing a design too early and then defending it in critique instead of treating early feedback as useful information — a rough version tested honestly beats a beautiful version tested defensively.
The script
Read it slowly, in the present tense, as though it has already happened. It is written to be spoken aloud, but silently is fine.
I watch the recording from yesterday's user test before I do anything else — the same moment where three of five people paused on the same screen, unsure which button actually moved them forward. It's not a big flaw, but it's a real one, so I open the wireframe and try two versions of the fix, not attached to either yet. I sketch it rough first, on purpose, because a polished version too early makes people react to the polish instead of the flow. In the design critique at eleven, I show both versions and actually listen to the pushback rather than defending my favourite — one colleague spots a problem with version two I hadn't noticed, which saves me from building the wrong one. I pick a direction, refine it properly this time, and prep it for next week's testing round. Over lunch I tidy the sticky notes from yesterday's session into a proper list, because half-remembered feedback is worse than no feedback. By the afternoon the flow that confused people yesterday makes sense on paper, though I won't know for certain until it's tested again. That's the job: never quite finished, always one round closer.
Shorter versions
Two for the ends of the day, and one line to carry through the middle of it.
The wireframe's updated, the sticky notes turned into an actual list, nothing left as loose scribbles I'll forget by next week. That confusing screen from yesterday's test has a real fix now, even if it still needs testing again before I trust it. My laptop's closed. Whatever next week's testing round shows, I'll deal with it then, not tonight.
I open yesterday's notes before I open the design file, so I remember exactly where the confusion was instead of guessing from memory. There's a critique this morning where I'll show a rough version on purpose, not the polished one, because rough gets more honest feedback. The work today is the redraw, one flow closer to making sense.
Sketch it rough first, listen properly in critique, redraw before it's tested again.
How to use it
Read this before a design critique you're nervous about, or right after a user test surfaces a flaw you didn't expect. A portfolio, real testing experience and shipped work are what actually build a UX career; what follows is only for staying open enough in the room to hear the feedback that improves the next draft.
The mistake to avoid
Polishing a design too early and then defending it in critique instead of treating early feedback as useful information — a rough version tested honestly beats a beautiful version tested defensively. The other trap is skipping the plain write-up of user testing notes because the session already felt clear in the moment, then losing half the insight by next week.
Questions
Does picturing a finished design actually help you design it?
Not directly — good design comes from testing, iteration and honest feedback, not from picturing the end result. This is for staying open through the messy middle part of the process.
Is user testing really where most of the actual design work happens?
For a lot of designers, yes — the redraw that follows real feedback is where a flow actually gets fixed, more than the polished mockup that comes before anyone's tried it.
How much should a design change after just one round of testing?
Sometimes significantly, and that's usually a sign the process is working — a design that never shifts after testing is more often a sign nobody looked closely at the results.
Have this written about you
The script above is written for anyone. Perla asks about your actual situation, writes it as a present-tense narrative and reads it back to you — in a calm voice or your own, recorded once. One ritual instead of ten apps.