Beesknees UX » Projects

RMS application [RuleManagement]

acvessen — Thu, 15 Mar 2012 15:45:45 +0000

The rule management suite (RMS) is being used by a small number of specialized analysts for the translation of legal text (government legislation, policies, terms & conditions) into unambiguous rules used for the development of software for their implementation. RuleManagement wished to extend the use of this tool to more organizations and “roles” within an organization.
However, training new analysts to use the tool was taking a lot of effort.

Screens were divided into 6 panels, each with horizontal and vertical scroll bars. As a result content that was relevant to the task was obscured while irrelevant content was constantly in view. Much of the interaction between user and application that could be observed involved adjusting the screen layout by closing, opening and/or resizing the panels.
The relationship between the panels was not sufficiently clear due to inconsistent labeling.
Available functionality was hidden / actions could only be completed with a context menu.

My job was to improve the tools efficiency and learnability in order to expand its user base. After doing contextual inquiries and studying examples of screen layouts that had been adjusted by users in the course of completing their tasks I was able to discover which combination of screen content was needed when.

Click to enlarge image

The resulting new interface design consisted of three different combinations of just two panels per screen to be used when respectively viewing / editing text, forming elements from text, or forming diagrams from elements.

A user can move through the screens from left to right while translating the text into logical elements, or from right to left to view the text fragments to which the elements were traced.

To determine which user interaction to create elements from text had the best efficiency and user experience 3 alternatives were tested with expert and new users.

Responsibilities: user research, requirement development, information architecture, prototyping (iRise).

NUtrecht [NUCultuur]

acvessen — Fri, 25 Feb 2011 23:26:47 +0000

2010 • Freelance
The objective of the NUtrecht project is to create a stimulating environment for young creatives who want to start their own business.
My job was to design and develop a web site that would interest the targeted group of Millennials and sponsors for the project. This was achieved by featuring photographs, video’s and tweets from young creatives already participating in the project.

Responsibilities: coordination, formulation of goals & functional requirements, design (CSS, illustrations, photo’s) & implementation.

Information architecture [OV&W]

admin — Sat, 15 May 2010 17:26:59 +0000

2010 • Logica

This project involved the development of a CRM application and a website for the Department of Traffic and Water affairs. An important objective of the web site was to consult and inform representatives of civil society about relevant government policy issues.

categorization of dossiers

Representatives were to be linked to relevant categories of “Dossiers” and / or “Programs” in a CRM application to determine which information they would be presented on the web site. This would determine which topics they would be consulted on and to which meetings they would be invited. Because these categories were ambiguous and most likely not clear-cut enough to the representatives whom had to pick from them, I developed a new way of categorizing them that also would allow for the inclusion of new programs and dossiers in the future.
Ultimately there were 10 factors that were key in determining useful categories:

Traffic or Safety/Environment (2)
Land, Air or Water (internal waters or sea) (4)
Persons or Goods (2)
Domestic or International (2)

Responsibilities:

Development of the “user stories” together with the product owner (=client) in “scrum team” for the representatives web site.
Preparation of workshop with product owner and end users of the web site to test user stories and categories.

TAX-i application [Logica, HWH]

admin — Sun, 10 Jan 2010 18:12:34 +0000

2009 – 2010 • Logica
The TAX-i project consists of 2 applications; ODB which leverages municipal data across silos, and UBS that calculates water levies based on this data. It is being co-developed by Logica and a couple of Water Boards. Representatives of the Water boards and users of the system are part of the acceptance procedure.

Taskflow file management

Taskflow service desk employee

I was responsible for the Interaction design of ODB (Java) which would often be used in unison with UBS that had already been developed in Oracle. The challenge was to adopt enough of the interaction patterns / behavior of the existing application for consistency of use while still trying to improve the user experience of the new application.

Responsibilities:

Leading workshops to collect user requirements,
analysis of the interaction patterns used in UBS,
making interactive prototypes,
writing the interaction design document (describing a.o. usability guidelines, user mental models, navigation, interaction patterns and errors, alerts and confirmation).

Digimeente application [GovUnited]

acvessen — Fri, 10 Jul 2009 17:56:01 +0000

2008 – 2009 • Logica
GovUnited commissioned Logica to develop their Midoffice Suite “Digimeente” (case management) for 70+ municipalities. My job was to design a user friendly GUI for it bases on the “proof of concept” (POC).

The case management system

Case management

A case file can originate from Post intake (3) but it can also originate from an e-form sent from a municipal website. These cases end up in the “work list” of a case manager (4) who, if the case file is accepted (5), will start processing the case (6).

Post intake

Post intake

When post (hard copy or email) is received, it must be determined whether this document belongs to an existing case. This is done by searching the data base (3) for a matching case file or client file. If a matching case is found (4) the document is added to the case (6). If a matching client file is found (8) it must be determined if this document belongs to an existing case (9) or constitutes a new case (and if so which type of case) (10).
If no matching case or client file is found (11) a new client file is formed, but only after the system matches the new data with municipal data as a check. A new case file is made for the new client and the document is added.

Case management

Case management vs managing case related information

The relationship of a case file to a client file

Responsibilities:

Analysis of the POC (Digimeente 1.3)
A presentation to GovUnited and the pilot communities on the importance of a good “user experience” for the acceptance and success of the application
The design of a user friendly structure and user interface
Production of interactive prototypes based on use cases and user research
Writing of the interaction design document / style guide used for the development of Digimeente 2.0