Overview Process
Discussing with the client the problems the intranet needs to solve. Writing a detailed statement of work. Working on the basic usage scenarios, making a site map and planning page templates.
Making a first attempt at developing a design concept. Showing brief overviews of the contents on the main page with links to relevant sections of the portal. Trying to use widgets.
Too much noise in the images, trying to add more graphicness.
Simplifying down. To make sure adding new information is easy, including the ability to upload new documents right from the main page.
Finalizing the design concept and presenting to the client. The client asks to work more on the visual aspect of the solution.
The second approach: trying to add shape and color. We get the idea to use the skeletal formula for hydrocarbon.
Too much text. Trying to create a visual hierarchy of the materials on the page, dividing the contents into blocks and distributing them among sections. The client likes the result.
Drawing a page with styles and starting to create templates.
The company has a complex internal organization and complicated relationships between the structures, which means there are a lot of diagrams. We need to create a universal way to present them which will not distract from the contents. Trying different solutions.
So far nothing. Asking another designer to give it a try.
Too complex. Yet another designer makes an effort.
The client chooses the most suitable design.
Understanding all the organizational interconnections.
Drawing complex schemes and “untangling” them.
Starting to develop the organizational structure interface. Trying different options: drop-down lists, vertically arranged job titles. Trying to use different layout systems.
But it’s important for the company to maintain horizontal hierarchy. Keeping the overall direction and sending the template for typesetting.
Working with maps.
Drawing the contour and adding relief.
Moving on to icons and illustrations.