Collaborative Human Centered UX & UI Design

With 10+ years in UX and UI design, my approach emphasizes working closely with users and cross-functional teams to understand both user and business goals, and provide contextual clarity for prioritization and decision-making as well as for effective focus and impactful effort.

Get in touch LinkedIn Legacy-folio Résumé

Modernizing a Legacy Conference Management Platform

2018 – 2025 CTI Meeting Technology UX Design & Research, UI Design, Product Team & Dev. Support

A decades-old scientific conference management platform serving worldwide associations needed modernization. Working within the product team, with developers, and customer support teams, we transformed the user experience while establishing scalable design patterns, and iterating on a UX process for improvements and new bussiness opportunities.

Initial context

Users faced inconsistent navigation patterns, outdated visual design, and a steep learning curve. The legacy system had accumulated 20+ years of technical debt, with each module using different UI patterns and interaction models. Interviews and user feedback in NPS and SUS surveys reflected frustration with the interface complexity, inconsistency, and outdated UI.

Effort
  • Understood the business via interviews and iterative artifacts like information hierarchy, high-level taxonomy, and user flows;
  • Reviewed existing UX artifacts like personas and feedback surveys;
  • Discovery and envisioning workshops with stakeholders, development team, and users representatives (CS) to identify pains, opportunities, and expectations as well as prioritizing and considering holistic solutions;
  • Rebuilt the legacy UI with its style-guide (Sketch + Zeplin) containing cross-module considerations — would now build the design system in Figma;
  • Defined the process and deliverables with templates across teams (Miro);
  • Identified key users → workshops or interviews input → validated scope statement and context → iterated user journeys and flows → iterated low to mid level drafts → provided support for development → post-development follow-ups;
  • UpVote, Maze, surveys like NPS and SUS, and other input means were used for keeping track and adding ways of identifying or handling next focus points;
Outcome
  • Modernized and consistent UI with facilitation of frequent navigation and tasks – dahsboards with overviews and clearer statuses, adding ways to search and filter, mutli-select and perform bulk actions, as well as optimizing and evolving import and export features along with ways to consistently manage the different modules and set up 3rd party components;
  • Quick adaptation to Covid context, creating an improved solutin for virtual/online meetings managed from the same control area;
  • Considering Pareto, identified the 20% of things that were causing 80% of time spent on tasks and customer support interventions. Tickets and time spend on them were reduced as well as customer support interventions.
  • As NPS and SUS opened feedback surveys were set per component, the impact was reflected per each module and component as we progressed.
Extended details

Understanding the business
– Discovery interviews with stakeholders and team members;
– Attending congresses;
– High level taxonomy of components, services, user types, and main user tasks;
– Reviewing existing UX artifacts like personas and feedback surveys.

Workshops with stakeholders, Dev team, and user representatives (CS)
– Design sprint format to explore and validate product direction;
– Mapped pain points, expectations, and opportunities
– Clustered insights using sticky notes, then grouped and prioritized them collaboratively
– Used dot voting to determine top priorities;
– Split teams for dedicated session of brainstorm for the top 3 most voted items/high level scopes found;
– Held cross-team presentations and debates to refine ideas

Structuring the resulted information and delivering it to stakeholders/product team

– A personas library existed but we narrowed it down to a structure of user groups and defined 3 categories of personas per task complexity and expectations of proficiency:
a. low complexity for attendees and the contribution portal,
b. mid complexity for the contribution portal and administration system;
c. high complexity for the administration system
(eg. attendee sites should have the low complexity as the main persona; while admin system being a complex context to allow high complexity but have focus on the mid complexity persona while also allowing some compromises for the low complexity persona).

Rebuilding the legacy UI
Identified most important components and initial sequence from workshop + follow-up interviews with stakeholders, dev-team, and users representatives (centralizing in Miro).

Drafted UI components, navigation patterns, and page types/templates like:
– overview landing page;
– dashboards for the main item types with charts, simple search toggle to advanced search and filtering abilities;
– control over what columns can be seen with order and sort;
– actions on all, a selection or individual items;
– detail pages of items from the dashboards, or from an app level search tool, or from settings pages;
– defined pattern of facilitating help tips and content throughout the application;
– used WP for creating and managing help content that can be called holistically from the top of the app or contextually in dedicated areas in pages.

Iterated drafts with the product team, dev-team and users.
– made initial HTML/CSS static prototype;
– created a style-guide and shared it with the dev. team, Sketch to Zeplin (2018 – 2019, would have done it with Figma if later);
– Aligned with UI dev. lead for using BEM as naming convention for the design system;
– ensured an always visible feedback tool for users;
– kept legacy UI with announcement and link to the new one – for a period both in parallel;
– After release, periodic check with in-house user-base to identify remaining pains or incompletion.

Setting a Requirements + UX/UI team process for further effort and new features
– dedicated Miro template to cover the scope of the feature, stakeholders expectation and user-base connections for validation and insights;
– also to cover specifics like need of reporting, or consideration of API updates, as well as need for trainings or help content.

Methods & tasks: Interviews, Surveys, Analytics, UI reviews, User tests, Workshops, User Journeys, Taxonomies, Information hierarchy, Role mapping, Mockups & Prototypes, Style Guide with components, HTML & CSS assistance, Agile environment & methodologies, and more.
Tools: Sketch + Zeplin (would use Figma now), InVision + Craft (for some early prototypes), Miro, Survey Monkey, Maze, Up Vote, Google Analytics, Xmind, Adobe CC, Jira, Microsoft 365, and others.

Building UX Maturity in a Development-Focused Organization

2011 – 2018 ISDC → Endava UI Design, UX Processes & Design, Dev. Support

Software development company that outsourced particularly to Netherlands and Germany (occasionally elsewhere like Switzerland or UK) for businesses in banking, insurance, education, health, and others.

Initial context

The company had no UX designers, no design processes, and development teams implementing UI based solely on requirements or improvisation. This led to inconsistent quality, rework cycles, and missed competitive opportunities.

The effort
  • Created in-house awareness of GUI & usability standards/best practices in the technically oriented – development outsourcing environment;
  • Aligned with clients on a user-centric vision and values towards using ISDC’s UI design services;
  • Determined and shaped the company’s UX maturity and UX community, culture and processes;
  • Workshopped and applied UX methods for discovery/research and envisioning for more holistic projects;
Extended details

Initial context
In 2012, a B2B software company outsourcing mainly to Netherlands, Germany and occasionally UK or other EU countries to businesses in education, medical, finance, and others – hired me initially on a front-end developer position, but really for my web design portfolio and interest for GUI & usability.

The company was very technical initially, without any in-house designers, focusing on development services and leaving UI/UX oriented aspects to the clients, which had own/in-house, or used 3rd party, or improvised.

The opportunity and start
If ISDC had UI/UX as a service, it would’ve been easier for everyone, improving the quality of deliveries (UI/UX wise), and adding UI/UX as a capability and service. The scope of my hire was kickstarting design services and awareness of heuristics in the company. 

Initially I was assigned to a project as front-end, having HTML & CSS knowledge. In parallel I started preparing a presentation aimed at bringing awareness about usability, best practices, samples of dos and don’ts and other tips and patterns from GUI manuals from Apple and Google as well as important ideas I felt relevant and impactful then (still do) – like Simon Sinek’s Golden circle, and Elen Lupton’s advice if you have to break the rules – brake them from a perspective of knowledge and not ignorance (Thinking with type). I created a survey, oriented around the UX maturity in the company, looking at the perception, expectations, and importance given to UX from different roles and teams (and presented the outputs).

Getting inertia
Started having UI design responsibilities in the initial project I was assigned to (education). With a few adjustments, used the presentation to align awareness on UI standards & usability with the project’s team on the client side, and was also assigned to assist with UI design on their partner project (facilitation of exam rooms).
After the initial presentation, other projects started to gradually use the UI design services to ensure good consistency, good standards and better quality of experience, but the UX research was not yet a specific service, having to work directly with provided requirements.

Keeping momentum
Eventually ISDC was bought by Endava (another bigger IT company).
So to align the teams I did a survey again, in both sides, and included the results in a presentation about Personas for a yearly internal event. The event was meant to raise awareness on UX in the now greater company – we called it “UX day” and it had at least 2 editions (last I know being before I left the company and Romania).
Projects and workshops continued with more focus on UX research and iterative envisioning tasks.

Methods & tasks: Interviews, Surveys, Analytics, UI reviews, Workshops, Design Sprint, Mockups & Prototypes, Taxonomies, Information hierarchy, Personas, User Journeys, Flow diagrams, Mood boards, Templates & Style Guide, HTML & CSS assistance, Print & Layout design, Agile environment & methodologies, and more.
Tools: Sketch + Zeplin, InVision + Craft, Miro, Survey Monkey, Xmind, Omnigraffle, Adobe CC, Jira, Microsoft 365, iWork, and others.

On the way: other media (graphics & animations)

I found the folder with animated intros and logos, print layouts and others, beyond what’s in the Legacy-folio. Will make a video of briefly glancing through them.

Design system sample in Figma
Demo: Prototype + User test + OBS video

I’ve been playing with OBS. Here, I experimentally show basic abilities with Figma and Maze. 720p instead of 1080p would have been even smoother, but this was fun :D

Let’s Work Together

I’m actively seeking opportunities in Vienna or other English-friendly EU locations.
Open to discussing how I can contribute to your product and team.

Get in touch LinkedIn Legacy-folio Résumé