Application for coordinating participants and guests of numerous corporate events. It was made for Gazprom Intranet.
Gazprom is a global energy company focused on geological exploration, production, transportation and sales of gas, gas condensate and oil, as well as generation and marketing of heat and electric power.
Project overview
2018
The problem:
Organizing and holding corporate events requires a lot of routine work. Coordination of guests takes a lot of time.
The goal:
Automation of routine actions,
Improving the quality of employee information,
Improving control over employee transfers at field events.
Improving the quality of employee information,
Improving control over employee transfers at field events.
My role:
UX/UI designer
Responsibilities:
User research, digital wireframing, iterating on designs.
- The problem:Organizing and holding corporate events requires a lot of routine work. Coordination of guests takes a lot of time.
- The goal:Automation of routine actions,
Improving the quality of employee information,
Improving control over employee transfers at field events. -
My role:UX/UI designer -
Responsibilities:User research, digital wireframing, iterating on designs.
Brandbook compliance
The company has a strong recognizable brand and corporate identity, the rules of which we had to observe.
Company has a design system Consta, which helps to make all brand products in the same style. We used that system.
Mockups
The company needed a single application for holding different events for different groups of employees, so it was also necessary to organize the differentiation of access to events and functions within the application.
Difficulties
We quickly found a common language with the client. However, there appeared a challenge at some point. Access to the application must be closed, and there are restrictions on access to information about each event inside the application. A personal access checked by a moderator is required for all employees.
First, to fulfill this requirement, we developed manual moderation: when entering the event, the moderator checked people with the list and gave them access permissions. But at the first event it became clear that these actions take a lot of time, so a queue formed at the entrance.
First, to fulfill this requirement, we developed manual moderation: when entering the event, the moderator checked people with the list and gave them access permissions. But at the first event it became clear that these actions take a lot of time, so a queue formed at the entrance.
We quickly found a common language with the client. However, there appeared a challenge at some point. Access to the application must be closed, and there are restrictions on access to information about each event inside the application. A personal access checked by a moderator is required for all employees.
First, to fulfill this requirement, we developed manual moderation: when entering the event, the moderator checked people with the list and gave them access permissions. But at the first event it became clear that these actions take a lot of time, so a queue formed at the entrance.
First, to fulfill this requirement, we developed manual moderation: when entering the event, the moderator checked people with the list and gave them access permissions. But at the first event it became clear that these actions take a lot of time, so a queue formed at the entrance.
We analyzed the problem, promptly finalized the application, and already at the next event, identity confirmation and registration took place instantly, using an individual QR-code for each participant.
Accessibility considerations
✅ Provided graphical cues to guide non-literate users and people with cognitive disabilities. Text is combined with images in menu.
✅ Visuals and icons are paired with text, especially on navigation.
✅ Visuals and icons are paired with text, especially on navigation.
Conclusion
This version of application includes our first and second iterations of the product in 2018. Later, however, further iterations were applied using a constructor solution called CampuZ. It is the main platform for creating applications and I took a huge part in designing this platform as well. So now this product for intranet usage looks like the latest version of constructor CampuZ (in App Store and Google Play). That's why the present day version of the application looks a bit different. I decided to show you the first version because in my opinion it reflects the corporate identity better. That was a great experience because our team had a hard task to balance between the client's design system and our platform solution.
More projects