Saturday, September 14, 2013

Tips for beautifying wireframes

- Gray the borders
- Master grayscale presentation
- Use correct fonts and sizes (understand what font is used in the application)
- Make it look as realistic as possible
- Use right mild colors
- Layout, reducing the white space
- Alignments
- Adding graphics that fit color scheme and correct size
- Filling up the spaces well, but keep design simple as far as possible
- Use transparent arrows and annotation border boxes
- Use light bg color (cream, brownish, bluish etc.)
- Show focus elements of the wireframe clearly
(make it prominent by contrast of colors, blur out the background/irrelevant etc.)
- Make modular wherever possible, chunking of elements/grouping etc.

Friday, September 6, 2013

Content Strategy Review points

- Links to be clear - where it would take you
- Provide good informational sources links
- Show Examples at each step
- Subtle References to subscribe in many places but not overt
- Language used based on intended/majority audience
- Add visual cues (icons) wherever possible
- Maintain conceptual separation
- Have headlines for each section
- How to enable features (screenshots)
- Emotional lead-in line
- Add stuff the company markets the most
- Refer to brand/product in key areas - e.g.: in subject line etc.
- Curiosity inducement in each subject line/maintaining theme

Thursday, September 5, 2013

Principles - Part 2

1. 80/20 rule - make the 20% good, highest use cases, use case pyramid in frequency. Set default options everywhere
2. Lean methodology: Build - test - learn - improvise
would the user know the terms?
3. Is the categorization/chunking/grouping of functions, actions and terms correct? Does each block show consistent behavior?
4. Minimize choices, have a phased approach, more important first then additional options/advanced
5. The problem is most of the time, do I have all the info to build the wireframe? what is missing? what are the alternatives? how many? justification of recommendation?
6. Is it developmentally possible? Front-end? Can the back-end/kernel handle it?
7. Consider everyone's opinions and put it in your UX framework:
Optimize UX (specialization) + background of other disciplines: proj mgmt, opinions and directions of people in power (requires convincing effort if not tallying), business goals
8. Involve all stakeholders and get their opinions from the start
9. Before any meeting - always have expectations of what to get from it, direct the meeting towards the desired framework, summarize and recheck at the end.