Information architecture

By Dana P Skopal, PhD

We have access to so much information that at times trying to locate the exact details that we need may take a great deal of time. In the days of printed reference books, we could go to the index and look for a key word. Nowadays we often rely on search engines or drop-down menus. The issue is: can content designers create a system that is logical for all users.

Information published on electronic platforms has led to the term: information architecture. This term has also been linked to Business Systems Planning and Information Systems Planning (Rocha & Sa, 2014). Stepping back, the underlying key components are planning a system that delivers easy access to its users or logical data sharing.

We have been advocating user testing for many years. Our research has shown that readers tend to look for the meaning in nominal groups as well as links between all document sections (Skopal & Herke, 2017). Readers respond positively when a written text is comprised of a combination of features such as a good blend of macro-structural signposting  (a text’s global information organisation), multi-modal design features (such as use of bold text), and shorter nominal groups.

When drafting or planning text or an information system, think about the end-user. The aim of the testing is to identify any ‘usability’ problems and see if the user can find and follow the information, and so properly use the text or platform.

Document or system usability testing can assist writers/producers in understanding how different readers may use the text, especially if they are writing for a broad audience such as the public. Usability testing can investigate if a reader can find all the information they need to act on and whether document/platform design, including the order of information, assists or hinders them. A writer/producer may make assumptions about how a reader should locate and digest the information. These assumptions may make sense to the producer, but they can make a text difficult for a reader to follow, and any problems can therefore surface during usability testing.

If you are involved in information architecture, perhaps think about it as planning a logical information system for the end-user and involve a range of end-users in your testing stages. Just as we have the saying, there is more than one way to skin a cat, our research opened our eyes to how many different ways users do read and take in information.

References

Rocha, A. & Sa, F. (2014). Planning the information architecture in a local public administration organization. Information Development, 30(3), 223–234. DOI: 10.1177/0266666913489841

Skopal, D. P. & Herke, M. (2017). Public discourse syndrome: reformulating for clarity. Text & Talk, 37 (1), 141–164,  doi: 10.1515/text-2016-0041.

Copyright © Opal Affinity Pty Ltd 2020

Leave a Reply

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