How to Create a Site Where Users Can Actually Find Information — Interview with Thom Haller

Download the MP3 file
Duration: 45 min.

Thom Haller, information architect and director of the Center for Plain Language, talks about how to create a site where users can actually find the information they’re looking for.

Specific topics in this podcast include:

  • The GECKO method (Gather, Evaluate, Chunk, Know, Optimize) for organizing content for websites
  • Arranging information based on user tasks
  • Clarity traps such as familiarity and clutter
  • Measuring the success of a well-architected site
  • Case study with plainlanguage.gov
  • Thom also talks about how the use of Plain Language helped the state of Washington collect an extra $800,000 in revenue.

In addition to his duties at the Center for Plain Language, Thom also teaches Information Design at the University of Maryland and Information Engineering at Johns Hopkins University.

To learn more about Thom, visit the following sites:

You can contact Thom at thom@thomhaller.com. You can also comment on this podcast by using the comment feature below, or by linking to this post in your own blog post.

About: Tech Writer Voices is a weekly podcast covering topics related to technical writing, featuring interviews, presentations, and other tips for technical writers. To stay updated with the latest podcasts on technical writing, be sure to subscribe to Tech Writer Voices using the e-mail subscription feature in the top-right corner of this page.

New: You can submit the questions you want to ask for the next podcast. Click the Next Podcast’s Questions button on the top toolbar and submit your question in the comments box.

follow us in feedly

Madcap FlareAdobe Robohelp

This entry was posted in podcasts on by .

By Tom Johnson

I'm a technical writer working for a gamification company called Badgeville in the Silicon Valley area in California. I'm primarily interested in topics related to technical writing, such as visual communication (video tutorials, illustrations), findability (organization, information architecture), content development (DITA, testing), API documentation (code examples, programming), web publishing (web platforms, Web design) -- pretty much everything related to technical writing. If you're trying to keep up to date about the field of technical communication, subscribe to my blog either by RSS or by email. To learn more about me, see my About page. You can also contact me if you have questions.