Let's Talk About Sitemaps

This week's assignment, we were to read about specific theories and their many components when it comes to seeing a project through. I chose sitemaps for the flowchart-like appeal when assigning tasks, and its straightforward approach in being proactive when it comes to laying out the expectations for other team members. Since I'm not generally a person who like hidden agendas, this is one of the theories I could relate to. 

Creating a sitemap is the first and most important step in the information design process. Without it, there isn’t a way to make order out of the chaos that always ensues when working on an interdepartmental project. Although there’s always a common goal, not everyone’s job is the same when it comes to seeing a fully fleshed out idea grow into a new reality. In order to do that, a sitemap should be in place before any work- individually or collectively- is assigned. 

But what exactly is a sitemap and why is it so important? 

A sitemap is a tool used to help the team figure out the entire website, with all its main sections, pages, and sublevel pages¹. Having this type of flowchart allows all the people involved in the project the ability to plan accordingly by knowing what their goal is, the timeframe in which it needs to be accomplished and the expected outcome. In short, it is a way to keep order in a situation that could become extremely chaotic without a guideline being implemented from the beginning. 

In digging further into this topic, I decided that I can't say I would change anything about it. Nor would I remove any steps, since each project's guidelines require different needs to be met and results to be achieved. For example, if the team is creating software for the special needs population- to include those with visual impairments- it would require a different set of guidelines to be met not only with the State Board of Education but in keeping with the Federal IDEA law as well, especially if being used in an academic setting. Conversely, designing educational programs for general education students is less strident, in one area, but no less important across the board.

 However, when looked at together, it is apparent that both groups of students have the need to be educated, but it must be done differently in order to achieve the goals listed on the student with an individualized educational plan (IEP) in place. Again, one goal is not more important than the other; just different in how they have to be handled. I would think the same reasoning would be used in any other field of commerce as well, especially if the same information design team is being used for competing companies. 

In conclusion, I am a firm believer that a person can’t rise to the occasion if they aren’t fully aware of what the goal is. Therefore, having a sitemap (or flowchart) would be valuable because it sets the expectations from the beginning, gives an idea of what the timeline would be, and gives signposts in case a contingency plan or extension is needed in order to complete the project. By giving the team the entire picture and scope of the situation, it also allows them to take ownership of their part in the development process. It’s said that an architect is only as good as his contractor, and the contractor is only as good as their interior designer, etc. This way of thinking also holds true when it comes to information design. Each person on the team holds the key to making the project as good as it can be before its release date. 

So in my opinion, having a blueprint before the project even starts is a way to not only get the project done mostly on schedule, but to avoid the ‘I didn’t know that’ implications later on if there are issues. 

1. Baer, Kim, and Jill Vacarra. Information Design Workbook : Graphic approaches, solutions, and inspiration + 30 case studies, Quarto Publishing Group USA, 2008. ProQuest Ebook Central, http://ebookcentral.proquest.com/lib/empire-ebooks/detail.action?docID=3399804.
   Created from empire-ebooks on 2023-02-23 19:07:09.