Interview with Louis Rosenfeld, founder and president of Argus Associates. Louis is also co-author of the best-selling book Information Architecture for the World Wide Web.

The interview is based on correspondence via e-mail, hosted by John S. Rhodes May 24, 99

What is information architecture? In general terms, what is most important?

This area of ​​knowledge is still relatively new and is under development; Therefore, the definition of information architecture depends on who gives it. Here's the definition we like:

Information architecture deals with the principles of organizing and navigating information to help people more successfully find and process the data they need.

This means that optimizing your site's search engine to help visitors find what they need faster is information architecture (IA). Optimizing the search program for load balancing is not the responsibility of IA. Development of a system of inscriptions in the navigation menu on the site is IA. The decision about what color this navigation menu will be decorated in is no longer up to IA.

Why is the IA value so high? Well, for example, imagine that you have invested several million dollars in your website. Aesthetically, it looks great, it's technologically advanced, and it's chock-full of great stuff. But now you find out that Users cannot find the information they need, and you yourself cannot determine where to put new material and when to remove the old one. This is where the need to turn to information architecture arises.

Or imagine that your company's employees are having such difficulty finding answers to questions your customers ask them that they print out every page of the intranet site because they're afraid they won't be able to find it again. Naturally, if the information on the site changes, the printouts will become out of date, but your employees will not know about this, and therefore they will provide outdated, incorrect information to your clients. It is precisely these kinds of problems that information architecture allows you to avoid. We even came across a situation where company employees themselves made up answers for clients due to the fact that the intranet site was poorly structured. Oops! It’s better to fix the site structure than to get into this situation.

What is the relationship between information architecture and usability?

Good question. But I'm not sure I have a good answer to it, at least not today. But I will nevertheless try to answer it impromptu.

I believe that usability in the broadest sense of the word applies equally well to describing procedures for testing and improving a car's instrument panel, ATMs, or websites. As an information architect, I learned a lot from usability specialists about how users behave on a site and how to evaluate the results of their work with the site. However, I don't think I can learn anything from usability experts about the information itself: how its materials and their nature affect the speed of information retrieval and processing. I also find that usability professionals don't always have a good understanding of how often a user's requirements for the same information change, and how those different requirements affect search speed.

So, I think of usability as a discipline with an extremely broad scope of application, but unfortunately insufficient when applied to specific areas. At our company Argus, we are experimenting with this problem; We recently hired Keith Instone, as well as another HCI specialist. So now our company has its own top usability experts. Then we will see what kind of services the market requires from us, and if necessary, we will mix our experience in information architecture with experience in usability. So a year or two later my answer may be completely different.

How can a well-designed website information architecture make a website more usable?

First of all, you need to understand that each information system - be it a book or an enterprise intranet - has its own information architecture. The words "well-designed" are key: many sites don't have a well-thought-out architecture at all.. They are like buildings that were built without a design: the solutions used on the site reflect the personal point of view of the designers, the site is difficult to scale over time, the design is entirely dependent on the technologies used on the site and not vice versa, and so on. So let's assume that a well-thought-out site architecture is planned from the very beginning.

If we consider that the site architecture is developed in advance, during the planning stage, it is difficult to say which approach is better to use. There are so many ways to organize information into a system that using all of these approaches together on a website would be redundant. A well-thought-out site architecture helps users by using only a certain set of all these methods, i.e. the set that is most suitable for the site based on:

• information needs of site visitors
• site materials
• goals and budget constraints

At Argus, we rely heavily on the 80/20 rule, which states that if we can use a few basic methods of organizing information that satisfy 80% of visitors, then we can confidently say that users will not get lost on our site. They will not be confused by the abundance of “information corridors”, many of which will only be used occasionally, but will require significant support costs. And also, we often notice that approximately 20% of the information that the client company presents to us satisfies all the requests of site visitors. Thanks to this rule, we can create smaller, more accurate arrays of information that are easier to work with. Without trying to embrace the immensity and satisfy all the needs and requirements of visitors, site owners and managers will spend less money and effort on maintaining sites while receiving the greatest return from it.

More specifically, a well-designed information architecture ensures that users spend less time searching for the information they need, and are almost never likely to say they didn't find something. With good architecture, they will always find that one document is linked by links to other documents on the same topic. They can always easily switch from searching for documents to viewing them and back. They will have a better understanding of what information the site can offer them. They will become kinder to their neighbors and take care of their parents. In general, you understand...

Explain why users find it difficult to find information on websites? What are the typical problems?

In general, working with information is a very, very labor-intensive process. Searching for information is like the game of broken phone: you try to convert your thoughts and images into words, and then into text or a search query. You then either have to manually go through all the site's documents (which is very inefficient), or ask a program (like a search engine) to do it for you. As a result, you get a text that, with a greater or lesser degree of accuracy, reflects the author’s original thoughts in words. Factor in the uncertainty inherent in all human languages, and you get that same broken phone.

Studies of the information search process show that the attempt to combine users' requirements for information with what the authors of this information offer them has failed. An example is the specific, highly targeted online database LEXUS/NEXUS. The Web brings even more chaos to this problem: information on it is present in many formats, on different topics, in different presentations. As a result, the volume of information grows by orders of magnitude. Let's take everyone into account Web users with all their differences, and as a result, the effectiveness of information search is reduced to zero. The more the information content varies, the worse the search results will be. You shouldn't lump everything together, but this is common practice on websites on the Web. That's why so often on every site the most popular page- this is the search page. This is why it is so often impossible to work with information on a company's intranet without getting completely confused.

Please briefly describe the key ideas of your best-selling book Information Architecture for the World Wide Web. Also, could you explain the success of this book?

Following the obligatory introductory chapters, we have two main parts. The first describes what we consider to be the core subjects of information architecture: organizing information, navigating it, labeling it, and searching. The next part describes the process itself: describing how to design and implement a website architecture. And at the end of the book we give an example of our work. We don't show you how you should design your website; there's no such thing universal method, which suits everyone. Each website's information architecture is built on its unique characteristics of users, content, and purpose. In this book, we are simply trying to introduce readers to the basic concepts of information architecture, give them terminology that will help them talk about the topic more easily, and (hopefully) design websites better.

Why is the book such a huge success? I would be happy to say that this was due to the revolutionary ideas contained in it. But I know exactly another reason: the real reason is the exact timing of the book's release. Today, web developers are dealing with the fifth or sixth reincarnation of their site. They no longer need to be taught how to optimize images on a website, how to program in Java, and so on. But they still find their sites have a flaw that stems from more abstract design concepts: information organization and usability. Web developers have already begun to realize this, and now our book is coming out. Exact time- this is the secret of success!

What is the future of information architecture? What will happen next?

Oh, if only I knew. An increasing number of XML-based content management applications for websites are being released. This will allow for more flexible architectures and also allow for more efficient use of published material. This is a very interesting phenomenon. But I'm somewhat pessimistic that there will ever be a system that will allow us to effectively organize disparate, unstructured materials into various formats and search them. Perhaps the situation with this matter is getting worse and worse. On the other hand, as a businessman working in the field of information architecture, I am full of optimism...

The most in a simple way To find out the essence of the profession for me was communication with relevant specialists. Below are some quotes from information architects.

Each quote to some extent helps to understand the essence of the profession of an information architect. But still, after conducting my own research, I came to the conclusion that none of these statements gives a complete picture of the profession of interest. An information architect fills a niche between a graphic designer, web designer, user experience designer, homepage designer, and usability expert (I've written separate articles about these professions). In fact, the work of all of these people relates to a common theme - user-centered design (see Jesse James Garrett's pdf on the elements of user experience). Over time, the responsibilities of each of these specialists became quite specific. Unlike a graphic/web designer who selects color scheme, decoration, texture, etc. to convey specific message, an information architect looks at site architecture from a more practical perspective. He may ask questions: “How many visitors come to your site?”, “How does the software help the user organize information?”, “How does the user learn about this software?”, “Does this information help the consumer (i.e., how does it stimulate him to make a decision)?”

To answer these questions, the information architect must focus on aspects such as the target audience technologies related to the website, data that is planned to be presented on the site and (preferably) the results of the first usability tests of the site.

Evolution of information architecture

Information Architects- more than just designers, planners or project managers. Information architects must draw inspiration from their work by collaborating with experts from across the company. They usually start their careers as designers or work among designers. At some point, they become interested in the requirements for website design technical requirements and begin to work in this direction. The best information architects work with multiple departments to tie all the components of a website together. They look like city planners or even ordinary architects. They have general idea about how and what works, but for more detailed study certain aspects of the system's operation, they have to go beyond the boundaries of their field of knowledge.

Perhaps you yourself are in a similar situation or are thinking about whether you can be called an information architect, judging by the responsibilities you perform. If you are impatient to draw conclusions, I advise you to take the “?” test.

Realization of your design ideas

To understand how an information architect manages a project, you can imagine that an ordinary architect is asked to work on a building after it has already been built. Although such a proposal seems ridiculous, it is often relevant today. Even after the most well-designed buildings are built, they can still be subject to change. Stuart Brand highlights this amazing phenomenon in his book How Buildings Learn: What Happens After They're Built. Again, as absurd as it may sound, we usually put information architects in a similar position - asking them to work on a website after other self-proclaimed information architects have already designed it. This is because most people are not aware that an alternative exists. The sooner you entrust your project design idea to a professional, the faster he will bring it to life.

Taking into account all that has been said, we can state the fact that most projects do not require someone who specializes solely in information architecture. This is because the responsibilities of an information architect are similar to, but not identical to, those of a project manager. A professional information architect is only needed if your site has a lot of information and especially if you offer some unusual way of processing it. This is relevant if, for example, your website offers new way searching for books.

Information architecture (IA) is equal parts science and art. Of course, you can go the “there will be content here somewhere” route, but on the other hand, you can make the project thoughtful, with a well-organized content structure. This will help make the site infinitely more user-friendly for end users.

Although not every project can afford to develop a custom information architecture, knowledge of it basic principles will help you create websites with the most accessible content.

What is information architecture?

Information architecture includes several related concepts.

The first is the structure of the available information. This is the way content on a website, intranet, online community or any other online space is organized and laid out.

Secondly, it is the art and science of organizing and marking out. An information structure in which it is easy for the user to find the desired content is the final product of the information architecture.

Third, it is a community of practicing educators whose goal is to ensure that good information architecture comes to the forefront in UX.

Analogy with architecture

You can find out which IA strategies are needed for a specific project by looking at the example of architectural drawings used in construction.

The average house on the same street in an average city can be built very well according to a standard plan. There are dozens, hundreds of other houses built from the same set of plans across the country. They perform their functions. They are economical.

Of course, each of these houses is different: they have different finishes, they stand on different sites, different people live in them, who use them differently.

From a template solution you can create a website that will meet the needs of a wide range of customers. Minor cosmetic changes are all that will be needed for the final adaptation of such projects. A front-end developer can easily make all these changes, and no IA will be needed.

Another scenario is when the house needs major renovations. Often houses are built “with reserve” so that changes can be made without damaging the building. Residents can add and remove rooms, move the kitchen, and tear down partitions. An architect is involved: after all, renovations involve major structural changes.

These types of solutions apply to the IA world as well. A general information architecture template may be close to what is needed. But perhaps a major overhaul is required? Perhaps a module needs to be added to ensure that users' needs are fully covered. Or maybe the project needs to be simplified. The information architect determines the changes that need to be made on the project and develops a plan to implement these changes.

At the other end of the spectrum is a completely custom project. By analogy with architecture, this will be a set of drawings developed from scratch. The architect will assess the future occupant's needs and then speak with the engineer and builder to ensure those wishes are achievable. This is the most expensive solution, but in some cases it is the only one that can satisfy the client's needs.

The same thing happens with large web projects. For example, startups simply cannot make do with out-of-the-box solutions, even those tailored to their needs. They need a solution that fully fits their business model and is scalable (after all, the startup will grow). This is the case when an information architect (or a team of such) can show his best.

Of course, there are also unique cases. So a small project may need IA, but a large one can easily fit into a boxed solution. This is why an IA strategy should be developed from the very beginning, rather than trying to squeeze in good content into the existing site layout.

What does an information architect do all day?

Although most often an information architect performs several roles in a company at once, there are cases when this is a separate specialist. So what is he doing?

First of all, the architect acts as a link between the site designer and developers. They must ensure that the designer has created proper organization content, and the developers interpreted everything correctly. And, of course, he is responsible for how the information on the site will be organized and presented so that the best way meet the user's needs. This is a very important mission, because if it fails, the user will be disappointed.

The last thing many information architects do is develop website prototypes. Using a prototype, you can demonstrate how users behave on the site, as well as how certain elements should function.

The site map created at this stage can become part of the finished site. Or remain an internal technical document.

Information Architecture Principles

Dan Brown has been practicing information architecture for over 20 years. He developed 8 principles of IA () that can serve as a good basis for any project.

1. The principle of objects. The principle prescribes viewing content as an evolving entity that has its own life cycle. Miscellaneous Content will have different attributes and behavior and this needs to be taken into account when designing.
2. The principle of choice. The principle means that you should offer meaningful choices to your users. However, you should make sure that the selection is focused on something specific: too many options can confuse the user. Information should also be presented in the form of a hierarchy, categories and sub-categories, instead of simply presenting it in a long list.
3. The principle of disclosure. It is important to give the user the information he needs. However, you should make sure that this is really what he needs, and not what you wanted to give. The principle also says that it is necessary to immediately give the user the information necessary to understand: what he can find on other pages of the site and what he cannot. Information should be presented gradually, from page to page, and not try to dump everything at once.
4. The principle of examples. Using the principle significantly improves the user experience. For example, when you go to a certain product category on Amazon, the site displays examples of products that fall into that category. This helps the user navigate faster, especially if he does not fully understand what the category name means.
5. The principle of the front entrance. Half of visitors don't get to your site through home page. This means that any page must contain minimum required text information- so that users understand where they are. This also once again confirms point 3, there is no need to try to fit all the information on home page site.
6. The principle of multiple classification. This principle suggests that different users use your site in different ways, they may have different different methods to find the same information. For example, some will use search, others will prefer to wander around the site. Content needs to be adapted to different user behavior scenarios.
7. The principle of targeted navigation. It doesn't matter where the menu is, it's what's written on it that matters. Try to make your menu and navigation bar show where the user is now and where they can go from the current page.
8. The principle of growth. On the vast majority of websites, content is a fluid, changeable entity. The amount of content you have on your site today may be a fraction of what might be there tomorrow. Organize your content in a way that allows it to grow in the future. And not only in terms of expanding a block of text: content can be added of completely different types.

All of these principles will be applicable to a given project to a greater or lesser extent. How to start working on information architecture?

Where to start

Where to start is by clarifying the purpose and mission of the project. Moreover, you need to understand what its mission is today, and what it may be in the future. Try to ask the client how they see the project in six months or a couple of years.

Finally, you have to think like the end users. For technically savvy users and beginners - absolutely different style using the site.

Having clarified these two points, you can plan your content strategy in detail.

How users find content

There are four different ways how users search for information on a website. The classification provides a good starting point for information architecture design.

Known target

In this case, the user knows exactly what he is looking for, knows how to describe it, and may even know where to start looking for it. This is an IA professional's dream.

Such users do not need to be led by the hand; they will most likely use the search or dive into the menu. If your search returns informative results, then there will be no problem.

Study

When the user knows what to look for, but has no idea how. The solution is the search module, which itself suggests terms that allow you to narrow your search. Such a search will provide the user with an invaluable service.

Unknown

The user has a vague idea, he thinks that he knows what he needs. Particularly relevant for complex industries: financial, legal. There is no universal solution, but we definitely need to figure out how to push the user to the right result.

Re-search

The user has already seen the content he needs, but does not know how to find it again. There are two options: make a “have you recently viewed these pages” section and a bookmarking function. The first works passively, the second requires user participation, but is not limited in terms of “memory” volume.

Models for organizing content

There are six main models for organizing and structuring content on a website. Sometimes they can be combined, usually in different sections of the project. But they can also be used independently of each other.

1. One page. Suitable for sites with very limited content, narrow purpose. Suitable for product websites, sub-sites of large companies or personal pages.
2. Flat structure. A flat structure is most often used on sites of less than 10 pages. The navigation chain is end-to-end and has no branches. This structure can often be seen in agency portfolios, on simple business websites or small e-commerce sites.
3. Index. Flat-like structure. However, the main page has a list of all pages. The examples are similar to the previous structure.
4. Chamomile. This structure is most often found in web applications and educational sites. After completing targeted actions on a specific page, the user is prompted to go to the main page. For example, in a to-do list app, after creating, editing, or completing a task, the user returns to the list.
5. Strict hierarchy. In a strict hierarchy, the transition to the next page can only be done from the parent page. This is a great structure for sites where authors don't want users to skip pages. For example, if a sequential training course is posted on the site.
6. Multidimensional hierarchies. One of the most common structures, largely due to the ease of implementation in terms of IA. In such a structure greatest number navigation elements, each page is accessible from everywhere.

"Labelling Convention"

It is very important to write the titles of some pages in a certain way. For example, when a user is looking for contact information, they will first look for links to a “contact us” section, “contact us”, or something similar. But if you name the page “reach out” or “ Feedback", then the user will have to work extra hard. Or even go to a competitor’s site.

Likewise, the “about company” or “team” page is better perceived when it is named something like this.

Big site vs small site

Good content organization is important for any site, large or small, but the more content you have on your site, the more important the role of structure is.

Imagine if Wikipedia articles had no links to other articles. I would have to use the search every time.

UX vs IA

Many designers and developers think that IA is just part of a UX designer's job. Yes, these areas are inextricably linked, but they are not the same thing.

Good information architecture is the key to a positive user experience.

Of course, your UX designer can serve as an IA, but on large and complex projects it is still better to have a dedicated specialist.

IA vs. your CMS

No matter how good your information architecture is, if you don’t select an adequate CMS for the project, you won’t be able to do it. simple process creating content for its authors, everything will go to waste.

Ask yourself: who will interact with the CMS, what level do these people have? technical knowledge and experience. A technical and complex CMS, although it will allow you to perform more tasks, but may be overwhelming for content managers.

Tools

Many IA tools are analog, despite the digital origins of the science itself.

Boards, card sorting are very popular IA methods, especially helpful in the initial stages.

Digital instruments

These tools are gaining popularity as more teams work remotely.

Whiteboard apps are great for brainstorming with a remote team or clients. The best of these services function like real boards, but can be easily linked to.

Most ordinary people, customers, and even some novice web developers are sure that any website begins with web design. Actually this is not true. Just as the basis of any building, from a shack to a skyscraper, is architecture (even if the builder did not develop it), the basis of any website, from the simplest - 3-4 pages - to impressive web sites, lies information architecture. No serious building is built without a design, so it is correct to assume that a well-thought-out information architecture for a site should be modeled from the very beginning.

A simplified representation of the site architecture is often the so-called. “block diagram” of the site, appearing in almost every statement of work ( technical task to create a website) in the form bulleted list. However, here I would like to talk about the information architecture of the site, represented through diagrams that more demonstratively show not only the hierarchy of the site’s pages, but also the interaction with the user/visitor of the site. The article provides the main graphic symbols for constructing site diagrams (so-called site drawings) and their designation. The article is provided with an example of a website drawing from personal practice.

The article will be useful beginner web developers for visual modeling of site architecture using special graphic symbols. The article may be interesting web service customers for an improved presentation of the site’s information architecture and its modeling.

Information architecture of the site. Meaning and Use

Information architecture(often abbreviated to “IA”) is a combination of organization, subjectization and navigation schemes implemented in an information system.

Quite often, the information architecture of a website is associated with Usability, a system of knowledge about the ease of use of a website. Thus, in the definition of The Information Architecture Institute we see:

Information architecture is the art and science of organizing and presenting websites, intranets, online communities and software, with the goal of ensuring ease of use (usability).

At the same time, equating website architecture solely with usability is not entirely correct. There is an opinion (and I tend to adhere to it) that “usability specialists do not always have a good understanding of how often user requirements for the same information change, and how these different requirements affect search speed” (Louis Rosenfeld, ( Louis Rosenfeld, co-author of the highly acclaimed Information Architecture for the World Wide Web; quote taken from interview). Here it should be clarified that under the search for information and the speed of this search, Louis Rosenfeld (according to at least, as I understand it) implies not so much a “site search” using the site service of the same name, but rather the names of menu items, pages, etc., which must meet the expectations and requirements of the visitor. Along with the principles of usability, information architecture should include marketing goals, highlighting more significant and “profitable” areas of the site. The role of information architecture is inextricably linked to the formulation of business objectives.

In my mind, Information architecture of the site- the art and science of organizing, subjecting and systematizing websites, serving for the marketing effectiveness of the site and including usability as its goals.

Information architecture. We create site drawings

It is most convenient to represent the information architecture and ways of user interaction with the site by creating diagrams. What do site drawings (diagrams) provide? Undoubtedly, the main advantage of site drawings is the visibility of the site structure and interaction with the user/site visitor. Practical significance site drawings are purchased in the liquidation field language barrier(terminological), and, as a consequence, in increasing the efficiency of working with the site (in conjunction with business tasks) and generating solutions to improve user interactions.

Information architecture diagrams typically use a number of graphical symbols. Below is a list of such symbols(graphic symbols) with the help of which site diagrams are created. You can read more about their meaning and usage on websam.com, article Graphic Notation for Documenting Information Architecture and User Interactions with a Website. Web designers/web developers - For further study, I also recommend reading the book Information Architecture: Blueprints for a Site by Christina Wodtke, one of the world's leading information architects (creating diagrams at the end of the book).

Basic graphic symbols for modeling information systems:

Below is a fragment of the information architecture of the website of the Capital Shipping Company (CCK=SHIP.RU):

We build our building, and then our building builds us.

Winston Churchill

What features of buildings excite us most? Regardless of who we are - experts in architecture or ordinary people, our emotional state is closely related to the physical structures that we encounter throughout our lives.

Each of the buildings has its own purpose. The bustling café, with its wooden floors and large windows overlooking the main street, is the perfect place for a quick breakfast meeting. The steel and glass high-rise building, with its mix of cubes1 and offices, creates an energetic and collaborative atmosphere for its occupants. A dark, smoky bar with paneled metal ceilings and bare brick walls turns out to be a refuge from the maelstrom of modern life. And the medieval Gothic cathedral, decorated with granite sculptures, stained glass windows and turrets reaching towards the sky, evokes both a feeling of humility and inspiration.

Each building serves its own unique purpose. Architecture, design, construction, decoration and location play an important role in shaping general impression. All items must

1 Cubicle (cube, cubicle) is a workspace separated by low partitions for each employee. It is an inexpensive alternative to individual offices, because it can be easily created in large rooms using screens and partitions, which simplifies redevelopment on your own and does not require the participation of a construction team. –Note scientific ed.

to work together. In successful buildings, the whole is greater than the sum of its parts.

Why did we start a book about websites by talking about buildings? Because the analogy with architecture is a powerful tool for getting to know the complex multidimensional nature of information spaces. Like buildings, websites have an architecture that defines how we interact with them.

Some websites have a logical structure that allows us to find the answer and complete the task. Other sites lack any logical organization and attempt to navigate them is futile. Can't find required product, we can’t find the report we found last week, or we get lost in the shopping cart of an online store. Such websites are reminiscent of failed buildings: houses with leaking flat roofs, kitchens with no room for a counter, office buildings with windows that won't open, and labyrinthine airports with signs leading in the wrong direction.

Bad buildings, like bad websites, are caused by similar architectural mistakes. Firstly, often architects do not live in the buildings they design. They have little understanding of their customers' needs and will not have to suffer the long-term consequences of poor decisions. Secondly, creating buildings that will stand the test of time is really difficult. Needs change, and surprises arise all the time. The desire for stability must be combined with flexibility and scalability. Architects are often faced with complex technical requirements, conflicting objectives and high level uncertainty. Transforming this chaos into order is extremely difficult and requires special insight and foresight.

However, web site developers should not confine themselves to the metaphor of building architecture. In this book we will also talk about information ecology, information economics, digital libraries, and virtual communities. From each analogy we will take everything important and discard the unimportant.

Definition

Those new to the field are probably still wondering: what exactly is information architecture? This section is addressed to them.

in·form·ma·ci·on·nyaya ar·hi·tek·tu·ra n.

1. A combination of organization schemes, objectization and navigation implemented in an information system.

2. Structural design information space, facilitating task completion and intuitive access to content.

3. The art and science of structuring and classifying websites and intranets to make it easier for users to find and manage information.

4. An emerging discipline and community of practice dedicated to disseminating the principles of design and architecture in digital spaces.

Did you expect there to be one definition? Something short and innocent? A few words that briefly capture the essence and boundaries of the field of information architecture? Let's daydream!

The reason we can't formulate a single, all-powerful, universal definition is the key to understanding why designing good websites is so difficult. It's about about problems inherent in language and representation. No document can fully and accurately represent the intent of its author. No title or definition can fully capture the meaning of a document. And no two people perceive and understand the same document, definition or designation in the same way. The connection between words and meaning is tenuous at best.1

Let's leave our philosophical platform and turn to the basics of things. Let's expand our definitions and explore some basic concepts information architecture.

Information

We use the term “information” to distinguish between information structure and data and knowledge management. Data are facts and figures. Relational databases data are highly organized and generate specific answers to specific questions. Knowledge is what is found

V people's heads. Knowledge management professionals develop tools, procedures, and incentives for sharing this knowledge. Information occupies some intermediate place. Information Systems Often they cannot give a single “correct” answer to a question asked. We will be interested in information presented in any form and volume: websites, documents, software applications, graphics, etc. We are also interested in Metadata: Terms that describe and represent content objects such as documents, people, procedures, and organizations.

1 A humorous look at deceit in English can be found

V Bill Bryson's book The Mother Tongue: English & How It Got That Way.

Structuring, organizing and labeling

This is what information architects do best. Structuring involves choosing the level of granularity1 for the “information atoms” of the site, and establishing the relationships between them. Organization consists of combining these components into separate semantic categories and themes. Subjectification involves determining the names of these categories and the navigation links leading to them.

Search and management

The ability to find information is a decisive factor for the usability of the site as a whole. If users are unable to find the information they need by browsing the web, searching the site, and asking questions, the site should be considered a failure. But it is not enough to focus on the end user when designing. The objectives of organizations and those who manage information must be taken into account. Information architecture must balance user needs and business objectives. Great importance have effective content management, clearly defined procedures and information policy site.

Art and Science

Disciplines such as ergonomics and ethnography bring scientific rigor to the analysis of user needs and information-seeking behavior. Our ability to study user behavior patterns and improve our websites is growing steadily. However, practical work in the field of information architecture will never be reduced solely to mechanical actions - the ambiguity and complexity are too great. Information architects must rely on their experience, intuition, and creativity. They must be willing to take risks and trust their intuition. This is the “art” of information architecture.

Clay tablets, scrolls, books and libraries

People have been structuring, organizing and subjecting information for centuries. Back in 660 BC. e. The clay tablets of the Syrian king were arranged by topic. In 330 BC. e. The bibliography of the Library of Alexandria was placed on 120 scrolls.

1 Level of detail (granularity) means the degree of generalization when dividing information into fragments or their relative size. Different levels of detail can be like this: private room magazine, article, paragraph, sentence.

IN In 1873, Melvil Dewey came up with the “Dewey Decimal System” to organize and simplify access to the ever-growing number of books.

IN Nowadays, most people are familiar with the basics of organizing information from experience working with books and libraries. In table Figure 1.1 shows the application of information architecture (IA) concepts to the world of the printed word and the World Wide Web.

Table 1.1. Differences between books and websites

Concept of IA			Web sites
Elements	Cover, title,		Home page, navigation panel
	chapters, sections, pages,
	page numbers, table of contents,		press, site map, subject
	subject index.		index, site search.
Measurements	2D pages, pre		Multidimensional	informational
	placed in succession		space	from hypertext
	nom linear order.		navigation.
	Tangible and finite, even		Weakly tangible, unclear, what
	what beginning and ending.		rez which information “about
			leaks" to other sites.

If we move from individual books to book collections, the comparison becomes even more interesting. Let's imagine a bookstore that has no organizational structure. Thousands of books are simply piled up on tables. Such stores do exist, such as Gould's Book Arcade in Newton, Australia. It is shown in Fig. 1.1.

Rice. 1.1. Gould's Book Arcade (Photo courtesy of Seth Gordon)

From a philosophical point of view, one can assume that such a random accumulation of books provides an opportunity to break away from the strict order of everyday life with relief. And in this bookstore you can really rummage through books with enthusiasm, making unexpected finds. But if you came looking for a specific book or are interested in a specific author or topic, then you are guaranteed a long and painful search for a needle in a haystack.

Compare the chaos of this store with the order that reigns in the library (Fig. 1.2). Even at first glance, the contrast is striking. If you take a closer look, you will find that a library is not just a warehouse for books, magazines and music recordings. It has complex systems and well-trained professionals who operate behind the scenes and select, evaluate, tag, describe, structure and organize collections so that library patrons can find what they need. Despite the fact that the information environment of the library is strictly organized, oriented approach, characteristic of the Dewey Decimal System and the Library of Congress classification scheme, also allows for exploratory browsing and serendipitous discovery.

Rice. 1.2. Browsing books in the library (Photo courtesy of http://intergate.sdmesa.sdccd.cc.ca.us/lrc/stacks.jpg)

In short, the main way for libraries and librarians to add value to printed materials is to organize these materials in a structured manner that follows the rules of information architecture and makes them easier for readers to access. Information architects perform a similar task, but it is usually done in the context of websites and digital content. Of course, there are significant differences between libraries and websites. Some of them are given in table. 1.2.

There are many challenges to overcome in developing a library's information architecture, but the library is a relatively well-defined environment and provides access to a wealth of accumulated experience. On the contrary, websites present a whole new set of problems. Virtual spaces have greater flexibility