A Practitioner's Guide to the Methods and Theory of Synthesis
By: Jon Kolko
Jon Kolko's article about concept maps really opened my eyes on how we can have an effect on a project. We can start at the initial proposal of the project, rather than the tail end of the timeline where visual design is the only task left to complete.
He first explains different experiences we can create for the user. First was a story they could create that illustrates an environment and feeling that the artist wants to convey. The overall goal is to create an experience for the audience rather than focusing on the technology or engineering behind the scenes of the project.
The next was taking different viewpoints of a project into consideration. By looking at the bigger picture, the designer can study the context in which the product would be used, whether it be a somewhere in a house, a city, or a geographical region. Then, looking at the details opens the idea of abstract thinking. Where do the components come from? How are some things seemingly the same, different? The final viewpoint is to backtrack and look back at the timeline created. Revisiting old ideas and concepts and comparing them to the current state may raise new ideas, making the current project more solid.
The last way of thinking is by "shifting the placements", which I had a hard time understanding at first. What does Kolko mean by complex systems related to thoughts? Is this what comes from shifting the placements or is there more to the process? After reading through the example of the Coffee maker, it made a little more sense to me. But as a designer for interactive/print design, how does shifting the placement relate to interactive and print design? It was hard to relate this way of thinking to our methods of design.
After reading Kolko's experience with Java and concept maps, it really put it in perspective of how beneficial mapping out ideas can be in a team environment. By creating a concept map, we are creating a language that everyone, even people that don't normally work in the design field, can understand. The example of teeth-brushing cleared up Monday's lesson on concept maps, and gave me a perspective of what my concept map will be like for our project in class. Although the Java example was very in-depth and informative, I don't think we have a year and a half to spend pre-planning our project…
I'm really excited about this new way of thinking. It's initial rough sketching of ideas is very beneficial because everyone can jot down ideas without anything being concrete. Ideas can be flushed out or developed, depending on importance. Once everything is agreed upon, then developing is stopped and the map is refined to be handed out to everyone else working on the project. This ensures that everyone is on the same page, and the project will be a success according to the concept map.
