Arbortext Editor Redesign
Summary:
- Led redesign of internal help documentation system
- Improved information flow and added consistency to the interface
- Simplified interface allowing users to reduce time on task
Challenge:
Oracle's Information Developers use Arbortext XML editor to enter information into the help system database on the back end. The editor's interface is clunky, not intuitive and lacks up to date common text editor conventions.
Process:
The first step in the process was to perform a heuristic evaluation. Then I interviewed 12 Information Developers to get a better understanding of their pain points and main issues. Once these interviews were complete I analyzed all of the data that was available to me and met with the engineers responsible for tweaking the interface to see what changes were possible.
Recommendations:
I then generated a set of recommendations for changes to the interface. These recommendations were both about the processes to complete tasks as well as visual changes. I created a PowerPoint prototype to ensure that the engineers knew exactly what changes needed to be made to the interface. This powerpoint also includes the design recommendations I made. Any sensitive information has been removed (mostly people's names)
When:
Winter 2010
Where:
Oracle
Timeline:
2 months
What:
Winter 2010
Where:
Oracle
Timeline:
2 months
What:

