Information Design Process

Taking this blog assignment very literal, it may be a bit long because it is my way of learning all of this as well. The process for information design can vary from the projects you do and the tasks that need to be taken on. Before you can even get started on the project, you have to learn who is on board. “Politics, Diplomacy, and Consensus” as Baer says page 32. What does your client want? What is behind this organization, the company, the reason for this project? You have to understand the insides of company, and everything in order to know what you need for the project to be successful. Perhaps the “business structures”, the “client’s history”, and so on with the general idea of the background of who or what you are working for. It will also help to get a team together who already knows a bit about what needs to be brought into the project, from the client’s team itself. It helps to have who is in charge, the “ultimate decision maker” (pg 33) with you a large step of the way. Meaning almost all meetings and other events. If they don’t like what’s there, your in trouble.

Once everything is in place, and you know about the company and all there is to know period, you can start with the roles to get the project on its feet. “Diagram the process” (pg 34). Explain what needs to be done so everyone understands what will be going on throughout the project. Make a list of who is on your team, get the roles and responsibilities of those people out of the way. Basically get your people in order so you can begin. Together, make a timeline so it’s known what is to be expected when to move faster. Planning and thinking a head of time always goes a long way, and paves the road for less mess ups.

Now you must figure out what this project is targeted towards. “Know Thy Audience.” (pg 36) Self explanatory really. Understand what needs to be in the project to get your point across. The emotional values, the physical values and everything in between. Make sure the content in your project has a significant amount of data for people to understand what you are building. Data upon data will give you more leeway for more information to better understand the finish project. While in development, make sure to “review your content while in development” (pg 46).

“The Creative Brief” (pg 50) is a document that will help the process move along nice and smoothly so everyone knows what is going on. Also understanding that people come and go, things will stop and start during a project. They’re will be some problems along the way, but the before process of planning should help you ease those moments. “Client approvals and feedback” (pg 50) will also help with the process running smoothly.

There are also sitemaps that can be included for bigger projects that have websites, exhibitions and more complex publications (pg 64). Creating blueprints is a critical step to projects. You need to know what it looks like and what is going were. Wireframes are essential as well, they can be used for websites and other documents. It’s a basic outline of what needs to be said and what needs to be understood on a visual perspective in my explanation. Research, research, research. The more you know about everything, the easier the execution of the project will be done and seen the way it is meant to be seen.

I cant say I would take away any steps, but it all depends on the project. I am all for forward planning before I even start anything. I like thinking ahead. I took this assignment very literal like I said before because I am learning more about the process so I wanted to write down what I thought was necessary in order to understand it.