Calendar and planner
My first project in the bank — issue planner for account managers. It includes the task tracker and the calendar. Service made both for web and mobile devices.
Planner guide fragment
Goals and problems
Main goal is a system controlling tasks of an account manager, which provides a calendar and task queue. It must be universal tool, customized and reusable for different employees roles.
Challenge is different requirements for different roles. For example, an account manager in retail department works with hundreds of individuals, making one task for everyone. On the contrary, a corporate account manager in a large business has few clients and knows every of them personally. The manager makes a lot of tasks for one client. Product managers, lawyers and others are required for a deal.
Challenge is different requirements for different roles. For example, an account manager in retail department works with hundreds of individuals, making one task for everyone. On the contrary, a corporate account manager in a large business has few clients and knows every of them personally. The manager makes a lot of tasks for one client. Product managers, lawyers and others are required for a deal.
Beginning of the work
Firstly the planner was made for one role: an account manager in large and medium business. A manager has calling, meeting and having deals. Me and my team have visited bank branches and interviewed managers for to know from their own words the needs and work features. More details for the work process we have received from business analytics.
I developed the main workflows for users, then made interactive wireframes. Me and the product owner discussed and corrected business-processes. Sometimes I asked for consultation from the art-director for solving complex issues.
To check the usability of our decision we had several qualitative research. UX analytics made scenarios and hypotheses, and I prepared the prototype. Current bank employees were invited for the testing. I participated as an observer. Testing was mostly successful, details described in UX research reports.
We also had a big session of Design Thinking. We interviewed an employees in different cities, found a lot of hypotheses, made a prototype and checked it with more UX tests.
I developed the main workflows for users, then made interactive wireframes. Me and the product owner discussed and corrected business-processes. Sometimes I asked for consultation from the art-director for solving complex issues.
To check the usability of our decision we had several qualitative research. UX analytics made scenarios and hypotheses, and I prepared the prototype. Current bank employees were invited for the testing. I participated as an observer. Testing was mostly successful, details described in UX research reports.
We also had a big session of Design Thinking. We interviewed an employees in different cities, found a lot of hypotheses, made a prototype and checked it with more UX tests.
The planner as unified basic system
We had the special team for working with the planner. Our goal was to do a unified system, which can be reusable in different internal projects. I created the common guideline for interface, which was not specific for any single role. The team developed a mobile iOS version of the planner.
Every task in the planner has not only a time slot and description, but full information for making the task. For example: contacts, calls and meets history, actual bank products. It also includes the deal information: figures, expiry dates, special conditions.
For to make the service flexible and customized we developed 2 work principles:
— Task cards are made up of typical blocks (modules). Their amount depends on a kind of a task and a user’s role. We can add or remove a block to configure a card.
— If we need specific information in a card, we can add a custom code block in it. We can start any bank inner process or third party applications (for example, routes with Yandex-map.
Every task in the planner has not only a time slot and description, but full information for making the task. For example: contacts, calls and meets history, actual bank products. It also includes the deal information: figures, expiry dates, special conditions.
For to make the service flexible and customized we developed 2 work principles:
— Task cards are made up of typical blocks (modules). Their amount depends on a kind of a task and a user’s role. We can add or remove a block to configure a card.
— If we need specific information in a card, we can add a custom code block in it. We can start any bank inner process or third party applications (for example, routes with Yandex-map.
