User experience architecture as problem-framing

September 25, 2012 § Leave a comment

One of the things we saw from the best designers is their use of prototypes to explore the problem. The prototype is the instrument they used to uncover previously hidden constraints and to see the shifts in the outcome of the design.

– Jared Spool, Exploring the Problem Space Through Prototyping

I’ve been thinking a lot about this concept lately — prototyping as a way to think about the problem — and how it relates overall to my role in bringing concepts to life. Early on in my first full-time job as a user experience architect, I remember taking wireframes and sketches to a feedback meeting and feeling like a failure when, 5 minutes into the discussion, there were so many problems with the concept pointed out.

It took me a while to realize that early sketches, wireframes, and prototypes are never going to be “right.” That’s not the point of making them. I may present them as potential solutions, but in reality I’m creating them to facilitate a discussion about what we’re trying to do and what our goals and limitations are. Only then can we begin to understand what the real potential solutions might be.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

What’s this?

You are currently reading User experience architecture as problem-framing at Julie's Notebook.


%d bloggers like this: