Personal need: What people actually understood
As a designer building my own portfolio, I wanted to know what people understood about my experience, capabilities, and the problems I could solve, not just whether they liked the design, but what they took away from it.
I started asking people to look at my websites. Their answers revealed a gap between what I thought I was communicating and what they actually understood.
You know what you meant to say. They only know what they can see.
Read the full story
As a designer building websites and developing my own portfolio, I wanted to understand something that wasn't obvious from looking at the finished product. What did people actually understand when they landed on my website? What did they think I did? What did they assume about my experience, my capabilities, and the kind of problems I could solve?
I didn't want to know whether people liked the design. I wanted to understand what they took away from it.
So I started asking them.
I'd talk to different people, ask them to look at my websites, and listen to how they interpreted what they saw. Their answers often revealed a gap between what I thought I was communicating and what they actually understood.
That gap fascinated me.
It also made me realize how difficult it is to see your own work objectively. You're too close to it. You know the thinking behind every decision, the challenges you solved, and the work that went into getting it right. But none of that is automatically visible to the person looking at your portfolio.
You know what you meant to say. They only know what they can see.
I wanted a better way to understand that difference.
