Visualizing Data
I would love to think the most important part of my job is making things look cool, but the truth of the matter is it’s more about relaying information.
The corporate sector has a dire need to visualize data in unique, compelling, and effective ways. Not many people like to read statistics, not many people like pouring over annual reports but it needs to be done. Information needs to be passed on.
Timing is crucial, the talent to effectively and effeciently design the relay of information is depenendent on how quickly or slowly it is presented. Imagine if all the copy in commercials was onscreen for exactly 4 seconds/line. Where is the emotion? Where is the engagement?
We know that static information is extremely maliable. I can make a very shocking point seem irrelevant if I time it correctly, and I don’t mean how quickly it passes forth along the screen. There is a window of engagement that I am slowly but surely learning forms the foundation for information architecture and display. How quickly does something move in and out? How long does it stay still? Does it stay still? Can you still read it on it’s way in and out? Do you want the data to soak in? How much of the data needs to soak in? What is less important about the data that you can sacrafice for the exemplification of other points?
These are things that I’m learning right now, in addition to building my business. I’m consistantly striving to improve upon what I know, not just show it off.
As these things come to me I will post about them. I’m sick of seeing tutorials that just scratch the service with bits and pieces of superficial design. Sure, it’s important to know how to apply keyframes and animations but it is much more important to know why you are animating something, what you are animating, and what you are trying to convey.
