Igor Pilicic | Senior UX/Product Designer

Senior UX/Product Designer who makes complex work understandable

I turn specialist knowledge, unclear requirements, and technical constraints into digital products that users understand, teams can build, and organizations can adopt.

Three entry points. One way of thinking.

Choose what matters most to you. The map will show how it connects to concrete work.

When knowing the methodology is not enough to design a useful digital tool

Client engagement · UX Design Lead and business analysis · RCA platform

The specialists knew manufacturing and investigation methods. My task was to understand how they actually applied them and turn that work into a connected digital process.

Fishbone, Is/Is Not, and 5 Whys needed to connect with the investigation: what the user was trying to establish, what information was already available, and what the next decision required.

Where my judgment mattered

Through research with specialists, process mapping, and collaboration with Product Owners and engineers, I connected user needs with the system's capabilities. I supported project planning, feasibility assessment, and shaping the direction before detailed design.

The Figma example shows how that approach carries into the product: guidance is available within the task, methods have clear entry points, and users retain an overview of the rest of the investigation.

My contribution to the team

I helped specialists, project leadership, and engineers build a shared understanding of the problem and translate it into workflows, prototypes, and implementation guidance.

Explore the workflow and design decisions

Show design decisions

How the methodology became a workflow

Four decisions visible in this development-stage Figma design.

Development-stage Figma design of an RCA workflow with fictional content

Key Contributions

Modular Interface (Atomic Design) - Implemented Atomic Design principles for a scalable, reusable UI component framework
Fishbone Methodology UI - Designed an interface integrating the Ishikawa diagram approach for identifying root causes of manufacturing problems
Is/Is Not Analysis UI - Built a tool distinguishing specific problem conditions by comparing scenarios where the problem does and does not occur
5 Whys Interface - Created an intuitive tool guiding investigators through iterative "why" questions to drill down to underlying causes
Investigation Modal - Designed the UI for gathering additional information from investigators during the investigation process
Comprehensive Process Mapping - Systematically identified and addressed inefficiencies in existing RCA processes
Stakeholder Analysis & Advocacy - Conducted in-depth research to inform and advocate for system improvements
Change Management - Applied change management theories to guide project evolution across the organisation

Investigation Methodologies

Fishbone (Ishikawa)

Visual cause-and-effect diagram interface for categorising potential causes of manufacturing problems into systematic groupings.

Is / Is Not

Comparative analysis tool distinguishing specific problem characteristics by examining where, when, and how the issue does and doesn't occur.

5 Whys

Sequential questioning interface that guides investigators through iterative layers of causation to reach the true root cause.

Selected development-stage interface designs

Created in Figma during product development. All displayed names, avatars, IDs, and scenario content are fictionalized. Click an image to enlarge.

Development-stage Figma design for a pharmaceutical root cause analysis workflow, showing a cause review with fictionalized content

Cause review - fictionalized scenario

Development-stage Figma design of a Fishbone analysis workspace with fictionalized pharmaceutical scenario content

Fishbone workspace - fictionalized scenario

Development-stage Figma design showing an overview of a pharmaceutical root cause analysis workflow with fictionalized content

RCA workflow overview

Outcome

A few months after my engagement ended, colleagues at Roche told me the platform was being used by more than 10,000 users. My contribution included turning investigation methods into understandable workflows and reusable interface patterns, working with subject-matter experts and engineers.

Overview

Designed workflows and interface patterns for pharmaceutical documentation management, including dashboards, metadata inheritance, role-based permissions, document relationships, versioning, validation states, and reporting views.

The role extended beyond interface design into workflow analysis, feasibility discussions, stakeholder alignment, implementation-ready work items, and enablement material for engineering teams.

Key Contributions

Ergonomic Dashboard - Applied HCI principles for a user-friendly project summary view, featuring settings, favorites, and links to DAMAS/MDMS hubs
Role-Based Workflows - Designed interfaces and interaction rules for permissions, controlled collaboration, and traceable actions
Metadata Selection - Designed interfaces for selecting from diverse project metadata reflecting specific characteristics and nature of each project
Process Validation Reports - Created specialised UIs including Chromatography reporting components
Information Retrieval - Designed filtering and retrieval interactions for complex project and document information
Responsive Design - Ensured seamless experience across various platforms and devices
Promotional Materials - Produced video and marketing content to boost project traction (per SMART Process Design requirements)

Process & Collaboration

Worked closely with Product Owners, Subject Matter Experts, and engineers using draw.io for system architecture mapping, organisational hierarchy documentation, data parsing process design, and wireframe development. Successful partnership with Product Owners facilitated task creation that was subsequently managed in Jira for both engineers and design.

Selected development-stage interface designs

Created in Figma during product development. All displayed names, avatars, IDs, and scenario content are fictionalized. Click an image to enlarge.

Development-stage Figma design of an enterprise authoring dashboard with fictionalized projects and identifiers

Project dashboard - fictionalized content

Development-stage Figma design of a pharmaceutical metadata configuration workflow with fictionalized project and product data

Metadata configuration - fictionalized content

Report configuration workflow

Outcome

Produced approximately 120 UI designs and a broader reusable design system, supported approximately 50 engineers across three teams, and contributed with the wider product team to a reduction of more than 30% in manual reporting effort.

Client engagement · Pharmaceutical projects · Vendor evaluation, RFP/RFI, and executive communication

Evaluating AI solutions required understanding what the technology could offer, how it fitted existing processes, and what introducing it would require.

I worked with project leadership, teams, and AI engineers on vendor research, structuring requirements, and preparing decision materials.

Where my judgment mattered

I connected business needs, user workflows, and technical constraints. I contributed to assessments of whether an existing system needed substantial reworking or whether the required functionality could be connected through APIs.

I translated findings into RFP/RFI materials, evaluation frameworks, and leadership presentations. A key part of the work was selecting what mattered to the decision, making open questions visible, and explaining trade-offs.

My contribution to the team

I worked closely with the project lead and teams to support decision preparation. My experience in UX, analysis, and visual communication helped connect technical details with the business questions leadership needed to resolve.

Engagement scope and responsibilities

Tiny Humans Engine

Working prototype · In development

A personal 2D game engine and editor for building small worlds with autonomous characters. The simulation below is a working extract, not a playable game.

I define how the systems fit together, develop and check them through structured AI collaboration, and document the decisions. The project brings together my design experience, systems thinking and hands-on prototyping.

Design is the center. Everything else helps me see the whole system.

The work, then the résumé.

Products and workflows

Visual design

Technical experiments

Root Cause Analysis Investigation Platform - Manufacturing QA

When knowing the methodology is not enough to design a useful digital tool

Where my judgment mattered

My contribution to the team

How the methodology became a workflow

Regulatory Reporting Tool

AI Procurement & Vendor Governance

Where my judgment mattered

My contribution to the team

iPhone 7 Pre-order Landing Page

Graphic Design Library

3D Neurological Visualisation

17+ years. From visual design to complex systems.

Independent projects and product development

Independent UX/Product Designer and Technology Consultant

UI/UX Consultant | RFP/RFI & OSINT Vendor Due Diligence

Lead UX Designer - Root Cause Analysis Investigation Platform

Lead UI/UX Designer - Intelligent Authoring / Regulatory Reporting

Marketing Graphic Designer & Web Designer

Web & Graphics Designer

E-commerce Manager

Part-time Designer & Developer

From the first question to a product that can grow.

Understand the problem

Agree on a direction

Design and test

Support delivery

Learn from use

Enable growth

Broad experience, one clear professional centre

Product and UX Design

Workflow, Evaluation, and Decision Support

Visual and Digital Design

The toolkit behind the work

Tiny Humans Engine

Scope of the prototype

Working Method: Structured AI-Assisted Development

A proof of concept from the engine

Let's discuss a role