A presentation I gave back in mid-2012 on the UX process currently being employed at the time. A process that needed a significant overhaul. Everything is a work in progress.
9. Content creation
•
•
“Sizzle” and “Steak” pages are de!ned
•
•
Content is edited by the copywriter
Content is written by stakeholders in
conjunction with the copywriter
UX takes a back seat, but shouldn’t
10.
11. Build wireframes
•
•
•
•
De!ne patterns used on Ubuntu.com
•
Explore multiple options for each page of
content
•
Get feedback verbally or via Onotate
Design a ‘typical’ sizzle page
Design a ‘typical’ steak page
Build a base wireframe with Ubuntu.com
furniture
16. •
Little or no generative research beyond
talking to internal stakeholders
•
Little or no evaluative research with
external users or customers
•
Time and resources
18. •
Work with other web-based teams to
de!ne and inform design process
•
•
•
•
Launchpad
Landscape
MAAS
Ubuntu One
19. •
•
A UI pattern library for Ubuntu.com
•
Mobile and tablet user testing using test
rigs
•
Analytics (goals, funnels, events,
heatmaps)
•
•
Multivariate and A/B testing
Responsive web design and responsive
wireframes
Accessibility auditing
21. •
OmniGra"e for wireframes, Pixelmator
and GIMP for simple graphics
•
OmniOutliner and/or Google Spreadsheets
for information architecture
•
•
•
Google Docs for collaborative working
Silverback for formal usability testing
Cisco Flip, Canon 60D and ScreenFlow for
video capture and editing
22. •
Sansom CO3U USB condenser microphone,
Zoom H4n mobile recorder and Audacity
for sound recording and editing
•
•
•
•
Skype for remote interviews/testing
•
Pen and paper
OptimalSort for card sorting
SurveyMonkey for questionnaires
Good old HTML, CSS and JavaScript
(jQuery) for clickable prototypes