SELECTED WORK · 02
PMI Silesia
I helped redesign the PMI Silesia branch website — so it says clearly what the branch does, how to join it and what’s coming up next.
CLIENT
PMI Poland Chapter, Silesia Branch
TEAM
PM · developer · graphic designer · 4 UX/UI designers
MY ROLE
UX: content models, information architecture, site map and user flow agreed with the team, then I built the content models · UI of the event page, agenda and archive
TIMELINE
2025–2026
TOOLS
Figma · FigJam
At a glance
Problem
The old site hid what people came for and never said clearly what the branch does: events sat several clicks deep, and membership, volunteering and education were mixed together.
Solution
Together we agreed everything — the content models, the information architecture, the site map and the user flow — and gathered benchmarks and inspiration, all on the PMI brand, the branch’s requirements and its brief. Once it was agreed, I built the content models and designed the event page, the full agenda and the archive — while my colleagues designed the other parts of the branch’s site.
Result
The new site is live. It says what the branch does and how to join it, every topic has its own section, and four designers delivered one consistent site.
Listen, compare, then decide.
We didn’t run user research, so every decision had to rest on evidence we could check: an audit of the old site against Nielsen’s 10 heuristics and UX best practices, pointing out errors and ways to improve; benchmarks of conference and association sites; and the branch’s answers to what they wanted to improve. Three findings shaped everything after: content needs clear thematic sections, the agenda is the heart of an event page, and pages must be easy to scan.
• my audit of the old site → what it led to
Found
Led to
A long description in small print, with no focus on what matters.
→
Content models and thematic sections — every page leads with its key information.
Workshops and seminars hidden inside a paragraph of text.
→
Events got their own section, one click from the home page.
No clear message when no events were coming up.
→
The event page became a template ready for the next edition, with past editions kept in an archive.
Low contrast in body text, in the Partners and Contact headings and in the footer.
→
Every colour pair in the design system checked against WCAG.
A search field with no label and image buttons with no text — invisible to screen readers.
→
Listed as WCAG issues for the team and the developer.
• where we started
Audit of the old site — errors and ways to improve
Page by page: where people get lost and what the site fails to tell them.
Benchmarks & inspiration
Event pages of conferences and associations, and inspiration each designer brought to the table.
Brief & requirements
We asked the branch what they wanted to improve and built on their answers — and on the questions members repeat.
PMI brand
The brand book as the base for colours, type and tone.
• what we took from it
01
Events one click from the home page.
02
One structure for all content.
03
Every page ends with a next step.
04
The agenda is the heart of an event page.
From content models to a site map.
Problem: membership, volunteering and education were mixed together, and events sat several clicks deep.
Decision: from the client’s answers and the audit we agreed the content models, the information architecture and the site map as a team; I then built the content models for the home page, the event list and a single event.
Effect: every designer worked from one agreed structure, and membership, volunteering, education and events each got their own clear section.
• content models, information architecture & site map
One system, many hands.
Problem: four designers working in parallel could easily deliver four different sites.
Decision: a shared atomic design system on the PMI brand book — colours, type and core components, every colour pair checked against WCAG — and low-fi wireframes of the main flows with real content before any visual layer. We met every week with our PM, who coordinated the team; we helped choose elements in each other’s work, reviewed each other’s designs and voted on proposals.
Effect: one consistent site, with subpage colours that follow the PMI brand.
• design system
01
Tokens
Colours, type and spacing from the brand book, contrast-checked.
02
Components
Buttons, cards, tags and forms with all their states.
03
Sections
Reusable blocks shared by every designer.
04
Low-fi → hi-fi
Structure first in grey, then the visual layer on top — with the colours of every subpage following the PMI brand.
05
Decided together
Weekly calls with our PM, who coordinated the team. Parallel design, comments, proposals and team votes; we took part in choosing elements in each other’s work and reviewed each other’s designs — then calls with the client to show the design and get it approved.
• how we worked
01
Brainstorm
Something always changed. Every round started with one question: what can we improve?
02
Analyse every change
No change went in on taste alone — every idea from the brainstorm was analysed before it reached the design.
03
Click through as a user
We clicked through each other’s screens, thinking like a visitor who isn’t only looking for an event but also wants to know what the site is about, which branch runs it and how to join it — not like the designer who drew the screens.
04
Design apart, choose together
For the visual style each of us designed her own version; then we voted on what to take from each — and why — and discussed it at the weekly meeting with our PM.
Effect: decisions came from arguments, not from who drew the screen — and the site combines the best of every version.
The event page & agenda.
The agenda took longer than any other screen: we had many versions, which we tested and rejected.
The hard problem: many sessions run at the same time, and every attendee chooses which one to go to.
Approach: we designed on the agenda of the previous edition, so on real data, and looked at how other event organisers present theirs, knowing most people would open it on the phone.
GOAL
An agenda that’s easy to read, accessible and usable on any device.
• how the agenda changed
01 · on the event page
Agenda preview
Only on the event page: a short list with “see the full agenda”, which leads to the full version.
02 · rejected
The full agenda in a pop-up
Everything in one column: four workshops at the same hour read one after another — a wall of text.
03 · final
Cards in time blocks
Talks and workshops side by side, breaks across both tracks — chosen after reviews, click-throughs and team votes.
• event page decisions
01
Cards in time blocks
Problem: the agenda was a wall of text — to compare two sessions you had to read everything.
Decision: I grouped the day into time blocks, with every session as its own card.
Effect: sessions running at the same time sit side by side, so choosing between them takes a glance, not a read.
02
Time first
Problem: the first thing people want from an agenda is “when?”.
Decision: time is the most prominent element, then session type, then title and speaker; extra details stay hidden until needed.
Effect: each card answers questions in the order people ask them, without clutter.
03
Colour as a map
Problem: in a full day of sessions it’s hard to see where the talks, workshops and breaks are.
Decision: each session type got its own contrasting colour, and the type is also written in text.
Effect: the shape of the whole day reads at a glance — and colour is never the only signal, so it works for everyone.
04
Built for the hallway
Problem: the agenda is checked mostly on the phone — on the go, between sessions.
Decision: we studied how other event organisers solve their agendas on mobile, and after several rounds of attempts, click-throughs and meetings we settled on: sessions stacked in one column, thumb-sized targets, parallel workshops in a carousel you swipe sideways, and a heart to save sessions to favourites.
Effect: the same agenda works in the hallway and at a desk.
05
Built to be refilled
Problem: the branch has no designer or developer on call, and a new conference comes every year.
Decision: I designed the event page as a template — dates, agenda, speakers and partners fill one fixed structure.
Effect: the branch publishes every new event on its own, and each edition looks consistent.
• information hierarchy — my agenda, annotated
1
Time first
People scan an agenda by the clock, so every card opens with the time.
2
Two tracks side by side
Talks on the left, workshops on the right: parallel sessions are compared across the page, not hunted for.
3
Breaks span both tracks
Breaks and lunch run full width in their own colour, so the rhythm of the day shows before you read a word.
4
Add to calendar on every card
The decision to attend becomes an action in one tap, right where it’s made.
5
Parallel workshops in a carousel
Parallel workshops that don’t fit side by side sit in a carousel (1 of 6) instead of breaking the layout — with the room on every card.
• event page — desktop & phone
• event page in action
The event page in action: the agenda, clicking through the speakers of the current edition, and the timeline of previous editions — every past conference stays online as a living archive. I put my versions of this section to a team vote; we chose the timeline split into years and months because it draws attention and echoes the dotted stepper used elsewhere on the site.
From Figma to a live site.
A developer coded the site from our Figma designs. The branch updates its events on an ongoing basis — sometimes there’s an upcoming one, sometimes there isn’t — so the films show the design with the 2025 edition.
Results
What changed.
Every topic got its own place
Membership, volunteering, education and events each have their own section instead of being mixed together.
One system, four designers
A shared design system kept parallel work consistent across the whole site.
Live, ready for the next event
The site is live. The event page waits as a template: when the branch announces its next conference, it fills it in and publishes, and past editions move to the archive.
NEXT PROJECT →
UX Audit