UX Enterprise™ Solves These Problems

How do I:

• Effectively define a request for a project?
• Quickly communicate the definition?
• Know if the company has done this or a similar project before?
• Know which scenarios, personas, questionnaires to use?
• Find the existing UX IP to do the project?
• Efficiently document the project?
• Drastically reduce the time to create a project presentation?

The pain and opportunity of industrial strength UX

If you are part of a serious UX operation you know that your "file-sharingwiki- repository" is broken. If you are just starting a serious group, imagine what happens when you have 100s of reports and terabytes of images and video. You can't find anything! You hope you remember the personas that you created three years ago and you have little hope of running across the pricey work from the European team that spent a year on the Estonian farming ecosystem that is your target population this week. It's almost easier to just redo the study.

But just try to make a fully indexed repository by hand! You will need an army of librarians. If you are going to change a design template and you want to see just which applications use the current Wizard template, you need to put a team on that research. So instead of using the power of the full UX team in your organization, we ask friends, read endless reports, and hope we can remember.

UX work can be fun. But the drudgery is in the endless documentation and communication. Normally, a research plan takes days to write and fills at least a dozen pages. A typical expert review has at least 15 pages specifying the user profiles, environments, scenarios, and artifacts being studied. Instead of creative contributions we get stuck in documentation hell.

Why can't it be FUN to work from a foundation of our organization's collective insights?

It CAN be FUN.