• Skip to primary navigation
  • Skip to content
  • Skip to primary sidebar

Simplicity Rules

Adam DuVander on keeping it simple

  • About Adam

Stop thinking like a technician

July 5, 2007 by Adam DuVander

Think like a user. That’s the basis of any good approach to usability.

The trouble is that it has become meaningless. It is easy to say I am considering user experience, but how do I hold myself to the standard?

I actively try not to think like a technician. I try to remove from my brain the knowledge of how web sites and applications are made. When I jump too quickly from problem to technical solution, I am grasping at what is easiest to implement, not what would be best for the user. Sometimes I have to ask, simpler for whom?

Technical knowledge can be a burden. It can cause one to see a problem from the wrong direction. Having a non-technician plan user experience is sometimes a perfect fix. If he doesn’t know the guts of how hard a perfect solution is, he isn’t tempted to tweak the user experience in the name of easy coding.

On the other hand, the non-technician might hand a web developer something unnecessarily difficult or impossible. It’s not his fault, because he doesn’t know a database or Javascript or whatever works that way. I think that is a pretty good trade-off.

Like the incrementalist and completionist, the non-technician and technician can work together to make something great. And if you’re patient and focused, you can even play both roles.

Comments

  1. Mike Duffy says

    July 5, 2007 at 9:10 am

    Beginner’s mind, grasshopper.

    Reply

Trackbacks

  1. Simplicity Rules » Knowing nothing can be good says:
    July 9, 2007 at 1:08 pm

    […] My dad is a technician. With a degree in mechanical engineering, he knows his nuts and bolts. So, he devised a puzzle that fooled fellow technicians, but was solvable by those blissfully ignorant of his mechanical ways. The solution required someone to not think like a technician. […]

    Reply
  2. Simplicity Rules » Knowing too much can be bad says:
    July 10, 2007 at 11:15 am

    […] If Fritz knew all the toil it would take to make the system count his rodents, he might have acquiesced to the poor solution. But Fritz was not thinking like a technician, so he was able to come up with the optimal solution. […]

    Reply
  3. Simplicity Rules » Think of the possibilities says:
    July 15, 2007 at 8:40 pm

    […] Some might call this thinking outside the box. I’d say it’s a darn fine example of not thinking like a technician. But I think it goes beyond that, to say a lot about humans’ innate ability to let go of constraints and be passively creative (much different than brainstorming on a whiteboard and voting on the “best” ideas later). […]

    Reply
  4. Simplicity Rules » Education in a Taxicab says:
    January 10, 2008 at 12:05 am

    […] Just try not to think like a technician (or a member of the elite). […]

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Simplicity Series

  • Designing the Obvious
  • Paradox of Choice
  • Laws of Simplicity

Copyright © 2025 · Elevate on Genesis Framework · WordPress · Log in