➡️ ◻️ ⛸️ Performance management through assessments - from idea to beta testing 🙃 🚋 🧗

One spring morning, my colleague and I thought about how to improve the quality of our teams in the company. To create such conditions for the guys to want to do their job even better, so that the creator strives to invent a product or part of it as gracefully as possible. Where it would be clear which skills need to be improved, and which are aerobatics. Where there would be no questions about the quality of work, and the bonuses were as transparent as possible. Where the leader could see the productivity of his team and what skills of its members need to be improved.

This is how the idea of a new product was born, the minimal functions of which we immediately tried to describe.

The MVP version of the product started as an Open Source solution and its development had to take place in free time from the main tasks

We decided to adapt the minimum viable product to the development department, but in subsequent releases we planned to refine the functionality for other departments, for example, such as support, marketing and others.

The first thing that we recorded is the subjects. To begin with, the system must have four key roles

We decided not to include the quality department in the minimum viable product, leaving this functionality for a later date.

We wanted the system to be like a constructor, so that roles in the system were not static, but could be configured by the administrator. This is how the admin panel for managing roles appeared.

Using the admin panel and the configured role, the user can activate or block registered members, form roles from system permissions and assign them to any users