Amal Ayyash's profile

Berry - organizational correspondence system

An internal system for a governmental organization that dealt with incoming paper-based applications (most of the time), and required a lot of coordination between different parties in order to see the applications executed was required by our team.
 
The main issue with the legacy system was the overly noisy interface where too many details, and the wide distribution of actions, where a user needed to jump between multiple screens to get the job done. The solution was to voice down the details to only the main required per action, and sort applications not according to technicality, but according to what the user needed to do with them.

Applying actions on every application was handled in a single screen, and digging deeper for detailed information was allowed for those who needed that information (which was for record keeping, and not a daily task).
 
The brand identity in the following screens were modified to conceal the original brand.
 
Whenever possible, small items that could be added or edited, were placed inline, to maximize efficiency and remove confusion. 
In the old application a lot of tools and activities were showing to user all the time, now we tuck everything inside hidden menus to keep the user focused on a single action, allowing them to do extra stuff whenever needed, which was not on daily basis
Sometimes, the interface to edit is not as complicated to have a lightbox of its own, nor is it as simple as having it in place, so we mixed, a lightbox in place.
Amongst the problems we needed to fix was invalid information, and too much interference. In the old system, because of the complexity and many steps and screens, some old data went in without validation, and some was almost impossible to validate. To fix the problem of "to interfere or not to interfere", we provided validation on data entry when the entry was in a single point, like above, and refrained from interferring when the entry point was in multiple places, and made sure the system is flexible enough to allow for human errors. Like in below screen.
Berry - organizational correspondence system
Published:

Owner

Berry - organizational correspondence system

Internal governmental correspondence system

Published:

Creative Fields