Portfoilio for film & visual art
Identity Portfolio
website
website
and multimedia artist.
Key deliverables: audience-driven IA, responsive exploration patterns and a reusable content system for adding projects safely.
Role: UX architecture, web design
Scope: IA, interaction design, usability testing, design system.
Context
My role & approach
Users
Problem
Insights
Solution
Validation
Results
Vladimir works as both a filmmaker and a visual artist.
The portfolio had to serve two very different audiences without splitting into two websites.
The design goal was clarity in the first seconds: who he is, which path or where to start.
The portfolio had to serve two very different audiences without splitting into two websites.
The design goal was clarity in the first seconds: who he is, which path or where to start.
Film industry viewers needed fast access to films, showreel, roles, and behind-the-scenes breakdowns. Art-world viewers needed curated artworks, categories, and context.
The portfolio should not only be a gallery, but also a means to attract employers, clients and the art environment.
The portfolio should not only be a gallery, but also a means to attract employers, clients and the art environment.
Starting point
Navigation followed internal file categories, so visitors had to decode the structure before exploring.
So I validated the structure and entry points first, before iterating on visuals.
Before: navigation mixed content formats
and forced visitors to interpret where to start.
and forced visitors to interpret where to start.
The biggest UX challenge was making the dual identity legible in seconds and the archive feel curated.
How I worked
Goals and success criteria
Without analytics, I used think-aloud usability tasks to validate:
• Can people choose Film vs Art without hints?
• Can they find a specific project fast?
• Do they stay oriented after scrolling and spot contact links?
With audiences defined, discovery focused on testing whether the existing structure helped each group reach proof quickly.
Target audience
I mapped three core evaluation intents (hire, collect, curate) and used four role models to make structure decisions testable: routing, navigation density, and how much context belongs above the fold.
Next are the findings that shaped the final interaction model and page templates.
Research
I mapped audience intents and ran quick, iterative checks to see where people hesitated, what they clicked first, and what made them leave.
Reference moodboard (inspiration only; not part of final deliverables).
• Moodboards to align visual tone
• Lo-fi wireframes to test structure before polish
• Quick usability checks to see what users scan, click or ignore
First structural hypothesis: a folder-style “file system” structure (projects as categories), mirroring how Vladimir organizes his work.
It aligned with the client’s mental model and created a strong identity — but in real evaluation tasks, visitors worked too hard to find the right path and the strongest proof.
Visitors had to guess where to start (Film vs Art) and sift through the wrong categories.
Decision fatigue
Long lists felt like a spreadsheet — exploration dropped after a few items.
Everything looked equal, so the strongest work didn’t stand out.
Weak story on the homepage
Text-heavy hero didn’t establish what to click first or why.
Reframing the problem
Visitors were trying to answer a specific question fast, so the portfolio needed to route by intent first, then reveal depth progressively — with stable orientation and curated choices.
What I decided
to build
stakeholder interview · audience mapping · think-aloud checks · quick structure tests
Hypotheses
Clear Film/Art entry reduces hesitation and increases correct-path selection.
H2 Navigation stability:
Fixed navigation while content scrolls increases depth of exploration without losing orientation.
Short visible lists increase clicks vs long equal-weight lists.
H4 Visual pacingLarge anchors and controlled rhythm reduce overwhelm in dense grids.
How I worked — Phase 2Design the interaction model (TO-BE)
After that, each track uses the same interaction rule - stable navigation and structured story, so visitors always know where they are and what to do next.
Template hierarchy
The structure is intentionally simple: one page template, one navigation model, repeatable content sections — adding new projects shouldn’t require redesigning layouts.
Lo-Fi Wireframes
validating mechanics before visual polish
After the first full prototype pass, I tightened the rules: curation thresholds, text pacing, template constraints — so the system stays stable as new projects are added.
How I worked — Phase 3
Without analytics, I used lightweight think‑aloud tasks and tracked observable signals: first‑click confidence, time to find the showreel, backtracking, and whether people could switch tracks without getting lost.
What broke
and how I fixed it
and how I fixed it
Sidebar list still felt heavycapped the visible set and grouped the rest as “Everything else”
Copy was too dense
kept scannable intros and moved depth below
kept scannable intros and moved depth below
Spacing drifted across pageslocked rhythm tokens and enforced components
Media grids competed for attentionreduced simultaneous thumbnails and used stronger anchors
NEW design
Turns the portfolio into an evaluation tool: clear Film/Art entry, stable navigation and a predictable story template for every project.
Baseline layout: navigation stays fixed on the left, while the story scrolls in a consistent sequence on the right.
I validated it through short repeated checks:
first‑click accuracy, list‑length tolerance and whether project switching stayed effortless without losing context.
The Human Side of Scale
The hardest part for me
Was earning enough trust to change the structure under a strong existing aesthetic.
Clarity didn’t dilute personality - it made the work easier to judge fairly.
What I loved most
Was the collaboration also: turning subjective creative material into testable decisions.
Once those were aligned, the rest became craft — pacing, templates, and small rules that keep the system stable as it grows.