Jimmy Chandler sitting at a desk working; photo taken when he still had short hair.

Jimmy Chandler, User Experience Architect

I'm here to help you create more usable, useful, and engaging digital products. How can I do this for you? That's a good question, with a four-part answer: Assess, Research, Design, Train.

Combine these methods with my emphasis on collaboration, agile/lean processes, and always putting you and your customers first, and together we can improve your digital products and services.

Contact me for a free, one-hour initial assessment of your product and user experience needs. I look forward to hearing from you.

Contact Me

How I Can Help You


I will look your existing digital products and help you unearth the real problems. I always deliver my findings in a way that is easy to understand and to convey to others within your organization.

  • User interface (aka heuristic) evaluation
  • Problem discovery
  • Team methodology (UX process, Agile/Lean)
  • Accessibility (WCAG, Section 508)


Once we understand the problem, we can work together to solve it. We start by formulating a hypothesis. Then we test that hypothesis with real human beings—your customers. We test often throughout the process to confirm that we are on the right path.

  • Interviews
  • Task analysis
  • Competitive research
  • Card sorting
  • Usability test (lab, remote)


Design is the problem solving. The format is just the delivery mechanism. Designs can take many formats, and together we will create the design you need to meet your goals.

  • Sketches
  • Wireframes
  • Prototypes (Paper, HTML/CSS, Axure)


If you want your team to grow their UX skills and methods, or to evangelize UX within your organization, I can devise a customized training or mentoring solution for you; ranging from a one hour presentation to a week-long workshop.

  • UX methods and skills
  • Agile and Lean processes
  • Accessibility

Thoughts on UX

UX Principle #1: Why Ask Why

Often, the most important role of the user experience designer is to be the person who asks the question “why?”

This may be a strategic why, a tactical why, a process why, or a discovery why. But the question must be asked, often at many different points over the life of a project. If you are not the one asking why, it’s possible that no one on your project will.

So are you?

Read full article Posted March 26, 2015