Well it’s been long since any of us had any chat on this ground. We have been silent. Lot of things are going around in everybody’s life. And I think it’s time now we break our silence and put down some worthy thoughts. I would like all to come back on track. We’ll be posting on my recent experiment on multitouch application, the game and the experience.

You might already have come across this, but in case not this is a very interesting concept.

VIDEO LINK

DESIGN

Design to most of us is the beautification of objects/elements in the system around us.

Though this forms only a small part of whole definition the perception about design needs to change. It’s become so much a lingo in our everyday life that we unknowingly use this word.

“Arey ye chair ka design sahi hai !!!”

“Is web page ke design me color thik nahi”

“Is rangoli ka design (?) maine kiya hai”

Above are some of the common phrases you might have overhear/heard sometime in your life. Now read my comments on them.

“Chair ka design sahi hai but are you able to sit on it properly or is it poking your butt ???”

“Web page ka design ? are you able to find the required information even with that color ???”

“Rangoli is an art not design”

Well you must have inferred something from my comments. If not let me first put before you the definition of Design in my own language.

“Design is a process in which you try to make/modify something to which is aesthetically good, functions to ease the life of it’s users/non users and helps them to get their work done in effective/productive way.” You may find different definitions on web. It’s because there is no unanimous definition of it. You may find all of them relevant in their context, though different. Well this may sound similar to the software development life-cycle or product life-cycle, it varies majorly on the medium and effectiveness. Designers mostly follow a visual medium so that it’s easier for human brain to understand the intricacies better and produce effective solutions.

When I say design is a process, it follows a proper step by step methodology to arrive at the final solution, which we many a times consider as one shot result.

Research

Design starts with research and understanding the system and context of the solution/problem. It may also be called “data collection” stage. Many a times it happens that you don’t have a problem at hand, but you are given a system/domain which you need to study and figure out the location of breakdown. You need to study about that system first and then draw mind maps and bubble diagrams (peculiar to a designer, though engineers also like it they seldom use it). Several such mindmaps of the system are created and put side by side. Visual representation of the system helps human brain to understand it in a better way and it’s possible to make interconnections between different parts of it. These interconnections may not be visible otherwise. An example of mindmap is show below. The mind map is a result of brainstorming on activities and objects surrounding TV.

Apart from studying system you also study parallel products/market/business of it. Well this part may be quite optional it assumes an important role when working on large projects. You study how things happen in current scenario and may depict major breakdowns by a brief story board by scribbles. Keeping this aside for later reference helps a lot to align final design with goals.

Analysis

Once you have cracked down the system comes phase of ananlysis. With whatever data you have collected you try to see where the problem lies or if you already have problem at hand you see what parameters are causing the problem and analyze the reason for it. As a designer this is mostly done using sketches and doodles and whiteboard scraps (though this is not their legacy). All the analysis is presented in form of “Visual Representation“. Infographics/Information aesthetics is one of the commonly used term with us wherein we present data in a way that is simple and quick to understand and looks good too. Information aesthetics is a site that has huge collection of wonderful representations of data. Some quick examples can also be found at Smashing Magazine.

See how beautifully is the data represented. Had this been in figures it would have taken years to analyze and you would be scratching your head, unless you have a Beautiful Mind .

Design Intent

After analysis it may happen that you want to rephrase your focus/problem statement/domain. This is the time when you do so. And with this you also set some goals for your final product. The goals may be in terms of usability, aesthetics, market value, consumer base capture etc. At the end of any project (small/big) you crosscheck whether your final product meets these goals or not.

Concept Generation

The designer phase. With all those stages toured our minds would be filled with all the data of the system. Now comes the time when you feel free and jot down ideas pertaining the problem. Withough hindering the imagination with technology, economic feasibility and constraints you sketch down the concepts. However the problem and its system and relevance of the concept should always be kept in mind. The end result of this stage may be doodles and story board of how the concept is going to handle the situation at hand.

Design Evaluation

Rough paper prototypes of the concepts are prepared and taken to the actual users.  Paper prototype help reduce the cost and time that might go in wrong concept. This is an easy method in which you draw low fidelity screens (with minimal details) of your product, number them as if you have drawn each box in the flow diagram of you concept system on a big paper. If it’s a physical product say something like cellphone/keyboard you make a physical model of the concept with some details to it and again paper prototype to show the response of the system at different point of use.

You closely watch users using these protoypes and make notes of where they are finding it difficult. You may use your goals (set in Design Intent) to monitor their actions. This phase is not about asking users whether they like the product or not. The answer would be yes in most of the case. As a designer we should be able to tell what suits them best by examining their actions and expressions while using the product/system. At the end of this stage you may create a matrix listing all the parameters that you have judged your concept for and differnt concepts. The resulting figure will give you an idea as to which concept should be taken further and detailed. Some of the parameters that I use are User liking, Personal favorite, Ease of User, Speed of learning, technology feasibility, amount change in current system etc.

Detailing

Once the concept is finalized the concept is detailed. Now this stage itself comprises of several sub stages like information organization (s/w engg. call it object modelling), navigation model (state diagram/flow chart), interface detail (button placement etc.). Hmmm this seems to be pretty close to what we have learnt in Software Engineering. Remember UML? Yeah, it’s almost the same except that all this is done keeping user in mind and not the system. Hence there is clear distinction between software engineer who cares about the software/product and a designer who cares for user first and then the software. This is an iterative process wherein at each stage of proto completion you go to the users take feedback, evaluate and come back. The duration actually depends on you and project timeline.

Though there doesn’t seem to be any end stage of the product except it’s final delivery for a designer it still continues wherein he/she studies the behavioural pattern of the usage of system and suggest necessary changes. This may also result in writing guidelines for such projects.

So here I finish looooooooong first informative post about Design. I have tried to keep is as short and simple and in the course may have missed many parts of it. The details will be taken care in posts later.

Till then happy designing.

I was always wondering if I could ever get chance to write programs for a specific board/platform Something that I can use which has all kind of interface to sense physical world ….. And I found arduino This little board is fun to play with , check it out!

Silent ideas should be expressed for they will make a difference.

Everybody has dreams and ideas. They could be small or big, but each of them have their values in life. Silent ideas is an effort to bring all these small ideas and dreams together to create a dream and a common goal that we can pursue together.

We are a group of friends sharing a passion to make a difference in the world. The journey that started during our college days has brought us to a place where we feel the desire to do something as a team. Our minds are filled with ideas that need a platform to express themselves and hence this website.

- Henry Ford

Silent ideas should be expressed for they will bring us together.