Best Information Architecture Courses

Find the best online Information Architecture Courses for you. The courses are sorted based on popularity and user ratings. We do not allow paid placements in any of our rankings. We also have a separate page listing only the Free Information Architecture Courses.

Information Architecture (IA) Fundamentals

Everything you need to know — from what content should be presented to what it’s called to how it’s organized!

Created by Joe Natoli - 30-year UX + Design Veteran; Consultant, Author & Speaker

"]

Students: 12451, Price: $44.99

Students: 12451, Price:  Paid

Without good, relevant content, there’s no compelling reason for anyone to visit or use the site or app; without clear, understandable structure, no one can find anything! How pages or screens are divided and categorized is a direct result of Information Architecture (IA). What shows up in your navigation menus and interactive controls is a result of IA. The information on a single screen and how people move through it — and what’s connected to it — is the result of IA.

Your physical body can’t perform any task without the bones under your muscles and skin, which are designed to support those actions. In the same way, a site, app or system can’t deliver anything to anyone unless its bone structure — it’s Information Architecture — is specifically designed to support those tasks

Information Architecture Fundamentals walks you through everything you need to know — from determining what content should be presented to what it’s called to how it’s organized and what format it’s delivered in. Taken from Joe Natoli's popular UX & Web Design Master Course taken by more than 7,000 students, these laser-focused lessons will show you how to:

  • Develop an IA that clearly illustrates the depth of content, its organization and priority.
  • Label and organize content in a way that makes sense to users.
  • Rules and methods for organizing the content and flow of a website, app or system.
  • Identify and diagram the content workflows critical to your product’s success.
  • Work with clients or stakeholders to find out how content should be edited, approved and published.
  • Extend an IA to the logical structures and naming conventions of the code files that make the product reality.
  • Make sure your content — and its organization — is relevant, appropriate and useful.
  • The five core types of IA models, and when to use each type.
  • Five ways to organize and categorize content types that always apply, no matter what you’re creating.
  • The best way to test and validate your IA with clients, stakeholders and users.
  • How to use IA work to develop primary, secondary, global and local navigation.
  • How to determine key navigation paths and test their appropriateness
  • My tips for rock-solid IA, based on nearly three decades working with some of the biggest brands in the world.

How to become the perfect Web and Information Architect

In this course the students will learn Web Information and Solution Architecture and define software requirements

Created by Daniele Protti - Project Manager and Software Architect

"]

Students: 650, Price: $89.99

Students: 650, Price:  Paid

This course has been created to support information and solution architects to improve their skills for the design and development of website, web applications and mobile apps.

It is an over-comprehensive course with the scope of covering all the aspects of the software development process where an information and/or solution architect should be involved to.

The main topics covered in this course are:

  • What is solution and information architecture: what really solution and information architecture is. How to setup your mindset to understand your customers and the design and development teams and solve conflicts and misunderstandings.
  • Different roles in the design process: get to know the main roles involved in the design and development phases of a web product, e.g. User Experience designers, User Interface designers, Product designers, etc.
  • Requirement Gathering: how to collect and define the requirement as your customer wants and understands.
  • Product Conception: how to do high and low level design, design the process workflows, define the business logic and algorithm to implement the functionalities, define the use cases, prepare wireframes, prototypes, sketches and mokups for the front end parts/pages of the final web solutions.
  • Database Architecture: specify database tables, define primary and foreign keys, link/reference tables, specify the user privileges.
  • Technical Requirements: how to translate business requirements into detailed technical requirements, how to specify layout and functionality requirements; write the technical requirements in form of user stories (following AGILE methodologies e.g. SCRUM); specify the acceptance criteria of the technical specifications in form of "definition of done".
  • Project Management: what a solution architect needs to know with regards to project management; how to layout a project plan; how to define a release plan based on sprints (following AGILE methodologies e.g. SCRUM); how to evaluation the time and effort needed for each design and development task. Although an information architect is not a project manager at the end in many cases in the real life of a business it is quite often required that an architect also take care of project management activities (at least as a technical project manager within a project or program management organization).
  • Quality Assurance: as for the project management past, an information architect may be likely involved in the definition of the acceptance criteria of each technical specifications. In this section students learn how to define test scenarios, test cases and test procedures (which at the end will be executed by other teams). With that I mean that the students will learn how to specify the way to test the technical specifications and to which criteria the acceptance procedures should refer to.
  • Documentation management: an information architect delivers a lot of documentation in the definition phase and needs also to update it when reviews are needed (e.g. during the project execution phase or when the customers decides to proposed new changes or when the developers inform that corrections are needed). In this session the students learn how to manage their documentation and how to deal with documentation packages, implement the revision process and specify the documentation data structure (including the management of the history and of the documentation package versions).
  • Code and component modularity: the critical key to success in software architecture is the specifications of single modules and templates to use as parts of the front end solutions and as pieces of software code to be reused at need and reduce redundancy, development cycle times and maintenance issues, efforts and times. In this session the students learn how to do modular web design and modular web applications as developers.
  • Front End Design: this is where an architect define the layout, the fonts, colors, user interfaces and interactions of a website or web application.
  • Responsive Web Design: this does not mean design and develop a responsive website or web application but how to specify a website or web application that must be responsive, i.e. must have the best look & feel on all devices (desktop computers, tables, smartphones, etc.). This is an extension of the previous session (Front End Design) but focused on making everything work on all the possible combinations of browsers/devices.
  • Back End Design: what is the difference between back end and admin panel and between back end programming and back end administration. Students learn here how to specify the architecture of an admin panel and back end admin for content management systems.

At the end I have included some special bonuses which include some case studies and an overview of some of the trends and technologies in web design up to date.

All the topics are supported by clarifications from 3 case studies:

  • a B2B product management application
  • a raffle campaign website
  • an eLearning web platform

The students learn how to use Microsoft PowerPoint and LucidChart to create their workflows, processes, wireframes and database architectures and will get to know the most popular tools for web architect to create prototypes and mokups. They also learn how to use Microsoft word to compile technical briefing and Microsoft Excel to list the technical specifications, generate the test cases and test scenarios, specify the project and release plans and track the documentation versions.

UX and Information Architecture Basics for Technical Writers

Learn 3 taxonomy development and 2 card sorting techniques for designing info architecture and user experience research

Created by JPDocu School of Technical Writing - WE TEACH SOFTWARE DOCUMENTATION AND DITA! 22K+ Students!

"]

Students: 145, Price: $99.99

Students: 145, Price:  Paid

Are you a technical writer, looking to learn the basics of information architecture? Are you looking for ways to properly target your audience, to enhance their user experience?

If you want your readers to easily find and retrieve your content, you need to invest in information architecture design and development. This will help you transform your content from simple "boring product documentation" into "intelligent information"?

To enable the efficient consumption of your documentation, the customers need to find it in an intuitive way.

The art and science of organizing your information deliverables are called information architecture.

One of the most important first steps towards organizing the information architecture is to define the terminology and organize it into a taxonomy you will use to structure and organize this content.

You need a taxonomy to define:

- define metadata, needed for machine learning, search, and retrieval;

- define the categories and values used to organize the information on the web page;

- achieve a common understanding and define terminology to be used consistently in the software documentation, the software, and the customer's front end - on your web pages

- the correct definition of the subjects to be used in a DITA XML subject scheme map;

Having high-quality metadata for your content often is the key differentiator between success and failure!

To build high-quality content that is ready to be used in an intelligent way, a technical writer must prepare and provide some form of pre-classified content.

The best way to collect and organize such metadata is by developing a taxonomy.

In this course you will learn:

- Which are the benefits you will get from applying the strategies for building taxonomies to your content;

- Understand important terms and their explanations with IT examples;

- 3 specific strategies that will save you a ton of time in creating a taxonomy: using a standard, a description, or by comparison;

But we do not stop here. How will you know if your taxonomy is a valid one? What your customers think about it and is it helpful or not? 

In the course you will also learn:

- What is the card sorting technique and

- How to set up open and closed card sorting workshops to validate the user experience with the information architecture you have defined;

- Which tools to use to design and develop information architecture and taxonomies.

This course DOES NOT COVER:

- How to write in DITA. (This is covered in other courses of JPDocu School of Technical Writing)

- How to create DITA subject scheme maps. (This is covered in other courses of JPDocu School of Technical Writing)

- Deep details on ontologies.

- Advanced tools, metadata repositories, classification engines, or servers for storing and handling of metadata, taxonomies, or ontologies - this is a getting started course, so such tools and details are not included.

- Ontologies and building them - we consider that a student needs to get a good hold on taxonomies, get practical experience before we can start talking about ontological relations between taxonomies and taxonomy terms.

- Chatbots - although taxonomy is a prerequisite for building decent chatbots, we do not go into details about chatbots in this course.

The instructor of this course, Jordan Stanchev, has over 20 years of experience in the technical communications world.

He is leading the information architecture experts group for the DITA CMS infrastructure at a Fortune 100 company.

Here is what participants say:

"Jordan's excellent course on taxonomies has helped me to consolidate my understanding of what it takes to build intelligent content. I will certainly apply this knowledge to the new documentation project that I'm about to start!"

— Anne Tarnoruder, Senior Technical Writer at Synopsys Inc, API documentation expert, author of the "Standards and Guidelines for API Documentation"

Enroll now and learn how to build taxonomies and design the information architecture of your documentation - take the first step to build your career from a technical writer into an information architect and user experience expert!

P.S. Do not forget that this course comes with a 30-day full refund policy - no questions asked!