Goals

To develop a document management system from scratch to replace the legacy platform

- Enhance scalability from both a technical and UX perspective,
- Cut maintenance expenses by favoring in-house solutions,
- Implement the corporate visual language and design system,
- Improve user experience and ensure alignment with other enterprise systems.

My role

- UX/UI/Product design
- User research
- Wireframes / Prototypes
- Stakeholder management
- Design hand-off
- Reviews and docs
- Presentations
- Facilitating workshops
- Feature proposals
- Design system development
- Team consultancy

Team

- 3 key stakeholders
- Product Owner
- 3 Analysts
- UX/Product Designer
- 6-8 Developers
- 2 QA

Duration

>3,5 years

Result

Fully designed document system for ~2000 employees, speeding up contract management by 30% compare to the previous system.

Users

We had 2 user groups within the company interested in speeding up the processes:

~ 2000 contract managers handling deal processing,
~ 1000 specialists verifying contract legality.

Challenges

- Users were entrenched in the old system, despite its inconsistent UX and business flow. To streamline contract signing, we untangled existing processes, revamped business logic, and introduced human-centered design,
- Transitioning systems wasn't a simple switch. We navigated through multiple launch stages - MVP, alpha, beta - while integrating two systems running simultaneously.

Tools

Figma, Miro, Jira, Confluence, ChatGPT, Illustrator, Kendo UI

Show design process

Task

It can come from:

Client
Big conceptual undefined requests.

Product Owner
User stories that need analysis, targeted on business needs.

Myself
Features and tunings to improve UX of final users.

Tasks can be:

Simple
You just do it. All the other team knows exactly how to do it.

Complex
Nobody knows what the result will be, me included. These 30% of tasks - fuel for number of ideation workshops, analysis, iteration, user research and hours of discussions.

Draft & users

If task is "simple", I have two checks of wireframes:

With Product Owner
If design answered business requirements.

With developers
If we can simplify design (without losing in UX) to speed up time to market.

If task is "complex", plus to those two I also have:

Brainstorm session with client
Sometimes it about them reinventing the whole business process. Sometimes it me to guide them into the right direction.

User interviews
30-minutes calls with users where they perform some tasks on clickable prototype. Depends on my hypothesis proven or rejected, the Draft stage can have another iteration.

UI & hand-off

90% of time
I work with predefined design systems. So I build the entire UI from its components.

10% of time -
some unique solutions where discussion with developers is needed.

After we discussed the final design with the team, I prepare mockups (flows, comments, documentation if needed).

When someone starts to work on this task in sprint they invite me on the tasks kick-off, where we check everything we need to do.

After the task is ready, I have a design review during the task demo or myself on the dev stage.

Release

As I work in-house, I have control on what happens after the release.

If feedback is negative and prioritized, I analys it it and go on the next iteration of design.

If feedback is positive, I can propose that new feature/pattern/flow for another product in our ecosystem. Yes, I test design innovations on selected products before the whole-ecosystem implementation.

Task

It can come from:

Client
Big conceptual undefined requests.

Product Owner
User stories that need analysis, targeted on business needs.

Myself
Features and tunings to improve UX of final users.

Tasks can be:

Simple
You just do it. All the other team knows exactly how to do it.

Complex
Nobody knows what the result will be, me included. These 30% of tasks - fuel for number of ideation workshops, analysis, iteration, user research and hours of discussions.

Draft & users

If task is "simple", I have two checks of wireframes:

With Product Owner
If design answered business requirements.

With developers
If we can simplify design (without losing in UX) to speed up time to market.

If task is "complex", plus to those two I also have:

Brainstorm session with client
Sometimes it about them reinventing the whole business process. Sometimes it me to guide them into the right direction.

User interviews
30-minutes calls with users where they perform some tasks on clickable prototype. Depends on my hypothesis proven or rejected, the Draft stage can have another iteration.

UI & hand-off

90% of time
I work with predefined design systems. So I build the entire UI from its components.

10% of time -
some unique solutions where discussion with developers is needed.

After we discussed the final design with the team, I prepare mockups (flows, comments, documentation if needed).

When someone starts to work on this task in sprint they invite me on the tasks kick-off, where we check everything we need to do.

After the task is ready, I have a design review during the task demo or myself on the dev stage.

Release

As I work in-house, I have control on what happens after the release.

If feedback is negative and prioritized, I analys it it and go on the next iteration of design.

If feedback is positive, I can propose that new feature/pattern/flow for another product in our ecosystem. Yes, I test design innovations on selected products before the whole-ecosystem implementation.

Show design process

New EDMS (Electronic Document Management System) to boost contract workflow. Actually, there was the previous one - it worked well enough, but more was needed.

So our team had to recreate all the similarities and spice it up with better UX, more features, and cut out the super-2010's legacy stuff.

<...> Vlad worked closely with developers and stakeholders, understood business needs, and turned them into clear, practical solutions. He actively responded to feedback and always considered technical constraints without sacrificing design quality. Vlad is a designer you can trust with a complex product. He thinks systemically, works consistently, and helps build scalable, thoughtful solutions.<...>

Senior Frontend Developer

We worked on this product together for 3 years

<...> Vlad worked closely with developers and stakeholders, understood business needs, and turned them into clear, practical solutions. He actively responded to feedback and always considered technical constraints without sacrificing design quality. Vlad is a designer you can trust with a complex product. He thinks systemically, works consistently, and helps build scalable, thoughtful solutions.<...>

Senior Frontend Developer

We worked on this product together for 3 years

<...> Vlad worked closely with developers and stakeholders, understood business needs, and turned them into clear, practical solutions. He actively responded to feedback and always considered technical constraints without sacrificing design quality. Vlad is a designer you can trust with a complex product. He thinks systemically, works consistently, and helps build scalable, thoughtful solutions.<...>

Senior Frontend Developer

We worked on this product together for 3 years

Vlad is a reliable, self-confident and efficient profi in UX/UI design and meanwhile a team-player that is very important. I can discuss with him all concerns regarding feature realization or criticise sometimes and he do not hesitate to dive deeper if needed, to offer different solutions that is really important in agile team. He showed himself as both easy-going person and professional with his own opinion.

Lead System Analyst / Product Owner

Working on this system together since 2023

Vlad is a reliable, self-confident and efficient profi in UX/UI design and meanwhile a team-player that is very important. I can discuss with him all concerns regarding feature realization or criticise sometimes and he do not hesitate to dive deeper if needed, to offer different solutions that is really important in agile team. He showed himself as both easy-going person and professional with his own opinion.

Lead System Analyst / Product Owner

Working on this system together since 2023

Vlad is a reliable, self-confident and efficient profi in UX/UI design and meanwhile a team-player that is very important. I can discuss with him all concerns regarding feature realization or criticise sometimes and he do not hesitate to dive deeper if needed, to offer different solutions that is really important in agile team. He showed himself as both easy-going person and professional with his own opinion.

Lead System Analyst / Product Owner

Working on this system together since 2023

<...> Beyond his technical expertise, Vlad's commitment to fostering a supportive and collaborative team environment truly sets him apart. He readily shares his knowledge, provides valuable feedback and consistently inspires those around him to do their best. His commitment to excellence and his role as a trusted Design Partner have been essential to our collective success. <...>

Senior UX/Product Designer

Design team fellow, 3+ years of reviewing each other

<...> Beyond his technical expertise, Vlad's commitment to fostering a supportive and collaborative team environment truly sets him apart. He readily shares his knowledge, provides valuable feedback and consistently inspires those around him to do their best. His commitment to excellence and his role as a trusted Design Partner have been essential to our collective success. <...>

Senior UX/Product Designer

Design team fellow, 3+ years of reviewing each other

<...> Beyond his technical expertise, Vlad's commitment to fostering a supportive and collaborative team environment truly sets him apart. He readily shares his knowledge, provides valuable feedback and consistently inspires those around him to do their best. His commitment to excellence and his role as a trusted Design Partner have been essential to our collective success. <...>

Senior UX/Product Designer

Design team fellow, 3+ years of reviewing each other

To comply with GDPR, this website does not collect or store any personal data. Сlick on LinkedIn icon to see the person in real

To comply with GDPR, this website does not collect or store any personal data. Сlick on LinkedIn icon to see the person in real

To comply with GDPR, this website does not collect or store any personal data. Сlick on LinkedIn icon to see the person in real

10%

increase in sales per feature-requested release

1.2x

increase of frontend developmet speed after implementing designed UI kit

10%

increase in sales per feature-requested release

1.2x

increase of frontend developmet speed after implementing designed UI kit

10%

increase in sales per feature-requested release

1.2x

increase of frontend developmet speed after implementing designed UI kit

Because document workflow is one of the most important processes in business, we used the MVP approach: "First it has to work, then it has to work well".

That's interesting for me: I have to create a roadmap for each feature to divide its development and integration into 2 or even 3 phases. Between each phase - a few months or even half a year. In this paradigm, it's obvious that the 2nd and 3rd phases can change every time another cross-feature is implemented.

That's interesting for me: I have to create a roadmap for each feature to divide its development and integration into 2 or even 3

NDA disclaimer: The images shown on this page are drafts, concepts or high-fidelity wireframes and do not reflect the final product. All names, numbers, titles, charts, and other data are fictitious.

NDA disclaimer: The images shown on this page are drafts, concepts or high-fidelity wireframes and do not reflect the final product. All names, numbers, titles, charts, and other data are fictitious.

NDA disclaimer: The images shown on this page are drafts, concepts or high-fidelity wireframes and do not reflect the final product. All names, numbers, titles, charts, and other data are fictitious.