Let’s talk about how Digital integration can work for your business

Fill in the form below, a local specialist will contact you soon

By clicking the button, you confirm your consent to the processing of personal data and are familiar with the privacy policy

TVC

CREATING A CORPORATE SOCIAL NETWORK OF THE TV CHANNEL

TV Centre is a state-run Russia TV station, airing since 1999.

Our solution integrated 5 systems and 14 services. To connect 3,000 employees, we designed a portal based on User Stories, which took us 5 design sprints

We proposed to make a "single entry point" for all systems, which would be linked to them through APIs. Each employee can view his/her tasks, changes, assignments, and interact with them. Thus, we solved several issues at once: poor user interface, fragmented information, too many windows that you have to switch between.

Before diving into development, we had to analyze the functions of the 5 systems which client was using, who and how was using them, etc. This information not only helped to design the logic of the system, but also to determine the lacking services which would allow the system to provide comprehensive and correct data.

You can't just write a user manual for a virtual workspace as you do for a fridge. Systems, services evolve as the business grows and gain a lot of new features that are obvious to company employees, but are an unknown land to an agency. In order to identify needs and demands which customer tries to cover by using many isolated applications, we usually use User Stories.

User Stories utilize interviews to list tasks of each key user. Based on this data, we determine features of the single workspace we want to create.

Notamedia analysts have done a tremendous job putting together demands and working out user scenarios

The approach to structuring tasks in design sprints was as follows: first, we created modules that do not require a lot of integration. For example, My Account was done in the first design sprint, since its development requires almost no simultaneous work on other modules. Task module, on the other hand, is better not to do in the first design sprints, since it profoundly relates to other modules, simpler ones.

It sounds complicated, but the workload was distributed quite evenly, although some of the initial stages were finalized towards project completion. User scenarios, the User Stories mentioned earlier, have been written for each module.

THE DEVELOPMENT WAS DIVIDED INTO 5 STAGES = 5 DESIGN SPRINTS

  1. 01
    • Event Feed
    • My Account
    • Company Employees
  2. 02
    • Services
    • Inquiries
    • Contracts
  3. 03
    • Catalog
    • Budgeting
    • Counterparties
  4. 04
    • Projects and programs
    • Tasks
    • Knowledge management system
  5. 05
    • Discussions
  6. We have created
    73 scenarios

We held briefings with the client's department heads, who would later use a module, and together we defined the key roles and responsibilities of users. The analyst at our end had to obtain a very detailed description from the client in order to create a scenario.

After briefings, the logic of key user roles was captured on paper and we started working on prototypes and design. There is never a single true logic, the analyst specifies to the designer a way a module is supposed to work. Designer may suggest a better solution, however, he doesn't have to

My Account prototypes

  • Projects section
    Projects section
  • Contacts section
    Contacts section
  • Absences section
    Absences section
  • Projects / No Projects section
    Projects / No Projects section
  • Services & Contracts section
    Services & Contracts section
  • Thumbnail selection
    Thumbnail selection
  • Logout pop-up dialog
    Logout pop-up dialog
  • Update a photo
    Update a photo
  • Photo deletion pop-up dialog
    Photo deletion pop-up dialog

The challenge was also the large number of employees who participated in meetings where the module features were discussed

If employees wanted contradictory features, we wrote down all demands and then sorted them out directly with the customer, identifying what was really needed. And so, a concept was formed. We wrote specifications for developers, as detailed as possible, taking into account the state of the system at all stages of interaction.

A brief extract from the prototype list of the task module

  • By customer service
    By customer service
  • By service
    By service
  • By task stage
    By task stage
  • By projects
    By projects
  • By team leader
    By team leader
  • Task page
    Task page
  • Kanban
    Kanban
  • By implementer service
    By implementer service

Bringing all the workspaces together was a challenge. The engineering team of the client was also engaged and wrote APIs

Using API, we took data from services and consolidated them in a new window. As we were drafting User Stories, we recognized that we needed a totally new functionality that wasn't previously covered by the client's services. In addition to API, the TV Center team also wrote code to our specifications.

Project UI-KIT

This was an exciting project for Notamedia. Integration was quite challenging, , but we gained a lot of experience

In addition, we really enjoyed working with the customer: any difficulties were addressed with a view to finding optimal solution, and our expert recommendations were respected and heeded. Such portals require a lot of work and commitment not only from agency, but also from the customer, customer’s insider knowledge and willingness to share it were absolutely essential to the success of the project.

  • 3000+ users
  • 100+ prototypes
  • 2000+ hours of work
  • 73+ scenarios

System specifications

Front

  • React framework
  • TypeScript
  • self-written State Manager

Back

  • Laravel
  • PostgreSQL
  • Cache and task queues by Redis
tvc-subtract