Three central tasks
Standardise communication, create one place for activity data, and unify the preparation and checking of reports.
Selected project · 2023–2024
YID: one digital platform for the Young Traffic Inspector Movement
From an initial idea to the launch of a portal connecting the working processes of five levels of a large distributed community.
Digital platform2023–202489 regions
Project scale
Key reference points
- regions
- 89
- YID units
- 35,000+
- participants
- 500,000+
Context and challenge
Why one shared platform was needed
Structures ranging from an individual unit to national headquarters needed different responsibilities, interfaces and access rights.
Activity, event and reporting data needed to be stored and transferred according to shared rules.
The task was broader than an information website: it required a role-based product in which data could move, be checked and accumulate over time.
My role
Project lead from concept to implementation
The project required product thinking, contractor management, implementation control and user adoption.
- product concept
- five user groups and scenarios
- requirements and access levels
- development control
- user training
- public presentation
Public scope
The platform was designed for 89 regions, more than 35,000 units and over 500,000 participants.
It included five profile types, digital portfolios, event calendars, individual IDs and reporting workflows.
After launch, I trained users and presented the project at the YID Forum and during Road Safety Week broadcasts.
Approach
Five groups, five working scenarios
The design followed what each group creates, receives, approves and passes to the next level.
01
YID Headquarters
Consolidated information and overall reporting.
02
Regional representatives
Regional coordination and data checking.
03
Municipal representatives
Support for local units, events and reports.
04
Unit leaders
Unit data, participants, events and reporting.
05
Young inspectors
Personal profiles, portfolios and achievements.
What the work included
- developing the portal concept and user scenarios
- forming requirements for structure and functionality
- designing roles and access rights
- selecting contractors and supervising development
- testing the platform and training users
- presenting the project publicly
Working logic
For every level of the Movement, the product logic defined:
- which data the user creates and receives
- which actions the user performs
- who they interact with and in what sequence
- which access rights they require
- how information moves between levels
The main challenge was not separate pages, but an interconnected system of roles, data flows and approvals.
Related expertise
Start with the context, not a preselected format
- digital product management
- user journey design
- distributed audiences
- user training