FIRST STEPS TO IMPROVE
COMPLEX SYSTEM LOOK

Case study

DOIT
DOIT software

--

Let’s face it. Everyone knows how to build ideally right design-development process in theory. But the real cases often appear very distant from ones you’ve learned with your mentors. So being able to do your best even in case of limited time and resources is crucial for a development team. Thus, we are going to share our experience of dealing with such kind of tasks.

Project background

Nowadays a lot of business owners and accountants use Excel spreadsheets for solving their tasks. And very often they face the inefficiency of spreadsheets for summarizing all data related to project. It can be scattered in dozens of files which can be edited by different people at the same time. Google Docs can partially solve this issue, but still it does not deliver users from wasting tons of time on formatting tables and charts and make them fit specific needs.

Projectric appeared as a solution to these issues. It is a cloud-based project portfolio management software that provides powerful and handy tools to analyse project metrics in order to transform them into business decisions. It helps to visualise data and give the wide landscape view of business state.

Input requirements

Projectric system was built several years ago basing on the technologies that were in use at that time. So the system seems quite like a naked engine. It works reliably and infallible, but it does not look nice and modern. Hence, we have got a request to make the first steps to improve system look without influencing on its structure. We clearly understand that it is not enough to make the system meet all the modern standards of CRM usability, though the key reason for that is impossibility to change both styles and user flow at the same time. We plan to make changes step by step. Bearing in mind that the Projectric system is currently in use by a lot of customers (who are mostly not very familiar with the latest IT-technologies) we decided to change it gradually in order to give users time to accustom the changes.

So the question is: how much can we achieve only with styles change?

Solving the task

As we can see, the old interface has plenty of visual issues that make the content quite difficult to perceive. Among them are cumbersome main navigation, absence of visual hierarchy and accents, lack of free space, too tiny font size and too dark colors. Also it is not obvious that some UI elements are clickable. Thus, fixing these issues could be a quite good start towards clear and easy perceptible look.

Main screen of old Projectric system UI
Main screen of new Projectric system UI

Actually, using only css changes we can make a lot. Everyone knows that if styles are disabled even the coolest web applications look like basic text and tables. So putting styles in order due to the main visual design principles could be a really great start.

Before — After

Here are some shots of old and new UI.

Charts/Health section — Before
Charts/Health section — After
Administration/Time section — Before
Administration/Time section — After
Project details/Documents — Before
Project details/Documents — After

Design system

If we need to change all the styles in the huge system it is smart to develop a guidelines which include measures and rules for each element. It allows to simplify the implementation and development new pages in future even without designer assistance. Also design system is crucial for components uniformity and consistency.

Projectric design system — General look

Actually, using only css changes we can make a lot. Everyone knows that if styles are disabled even the coolest web applications look like basic text and tables. So putting styles in order due to the main visual design principles could be a really great start.

Projectric design system — Details

To provide the client a full understanding of the new layout we provided an interactive prototype filled with real data. So it was easier to imagine how the refreshed system will behave in real life. We tried to create as detailed prototype as possible for time-quality prospective.

Prototype connections — Details
Prototype connections — General look

Conclusions

Working on this project we proved to the client that he can get a sufficient result even after very basic but right changes. As for the further steps, we plan to investigate how users will interact with this new refreshed look and due to that we will suggest changes that will make UX more convenient.

Thank you for reading!

We are open for communication. Feel free to write us: contact@doitua.com
Check our website: https://doit.software/

--

--