Why do software designers want their work to appear more complex instead of less? That’s a question David Pogue poses, and I’m sure it’s one that you’ve asked too. Whether as a user of software, or in your role as a technical communicator.

In decrying complex, cluttered interfaces Pogue hits the problem squarely on the jaw:

it’s less effort to make the end user jump through a bunch of hoops than to make your own software more intelligent.

Documentation can help explain a complex UI. But, as Aaron pointed out in a previous post, You can’t paper over bad design, no matter how hard you try.

It takes more than that, and technical communicators can play a role. I remember a quote I read on the User Advocacy blog:

[Technical communicators] can also become a part of the development team that ensures the interface is consistent, the application works from a user’s point of view, all of its parts work correctly and the experience confronting the user is one they will want to return to. We will be instrumental in communicating application to user, and user to application.

Thoughts? Feel free to leave a comment.

Related posts:

1. User interfaces: don’t try to be too cute
2. Putting the user back in user documentation
3. Making yourself part of the team