It is seen that for good results, the designer needs to use his gut feeling and change his approach based on the business condition.These principles are only good for basic analysis, for better results you have to rely on the designer.
Visibility of system status
The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
Match between system and the real world
The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
User control and freedom
Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
Consistency and standards
Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
Recognition rather than recall
Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
Flexibility and efficiency of use
Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
Aesthetic and minimalist design
Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
Help users recognize, diagnose, and recover from errors
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
Help and documentation
Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
The stills so far was.
- Visiting a college and helping them to use technology at its best. Create branding plan for the school.
- A business came for a branding online, guided them with technology
- Online sales for an e-commerce company, gave consulting tips and new design for their portal
- A new online resume/portal was made
- An Australian university needs revamping of their portal, analysis for competitive values with its market captures was done and delivered
- A dating site was launched
- Service industry in UAE asked for a branding work, it was done with pleasure and satisfactions
- An online social media search engine was created http://27expo.com
You can have a different view of the blogs by clicking on the links
You can see the same blog in multiple views, the views can be changed by selecting the navigation menus on the right.
I checked Picasa and was so happy by it, there is a drop pane where we just need to drag the images that need to be uploaded, rest is taken care.
The solution works well here as here we have multiple images that needs to be published on the internet.
Hats of to Google for this feature. I like it and it solves the problem so well.
These pics i had collected long back and they are so touching i thought to share with the world. It is true we cannot actually create the real WW2 in movies. I appreciate the film makers to educate us on these topics, and personally i have seen many movies on war. Well the fact is I love them, i drew a conclusion form them that i have already made bold in the above paragraph.
Now how to overcome such a situation, the best part is to make the expectations clear. Before staring the work prepares a present explain what they will get in from the association.
See the presentation that I had created for Universal Music group (Vevo.com) stakeholders to make their expectations clear.
Tips for sketching
1. Use less lines
The less lines you use the better it becomes to explain the concept. More lines create clutter and confusion.
2. Use thick lines outside the main boxes and points of stress. Using thicker lines make the design clean and visually pleasing
3. Render the borders to give the computer sleek looks
4. Avoid too much detailing of elements – such as minimize, maximize buttons
5. Scan the sketches and send via e-mail. Most stakeholders would love to see something in e-mail. They can easily share it with their teams and seek their views on it.
6. Sketch in batches – don’t ever sketch the complete software in one go. First sketch the home page of the software. If you get a green flag go ahead and sketch more. Otherwise you need to again sketch from scratch if your home page design got rejected.
7. Focus on the element on hand – do not sketch the outside section again and again.
These are the 7 golden rules that will make your sketch stand out and get a good name.
When the user enter the text in the form fields you can not read the text that you are typing.
Hope these guys can change it.