I plan, design and build digital products end to end, from research and flows to high-fidelity UI and working no-code builds in Bubble, FlutterFlow, Webflow and Figma.
A concept vaccination tracker imagining what childcare in Poland could look like after a digital reform, designed end to end from market research through 42 high-fidelity screens.
A UX redesign of the lidl.pl webshop, grounded in a benchmark of 12 competing e-commerce sites: reworking the product page, guest checkout, homepage personalisation and more.
A live, shipped feature inside an internal freight-brokerage platform, giving brokers a real-time view of earnings, disputes and payouts.
A leadership-facing dashboard for the same platform: margin, revenue, exposure and cash flow against target, built from a working session with the CEO.
A founder-led digital health platform helping women track and understand endometriosis symptoms, built end to end from market research to a live app in FlutterFlow and Firebase.
I'm a biology graduate turned UX/UI & no-code designer, based in Poznań. For over a year I owned a full digital product end to end at Egala/Brocarga, from problem analysis, through detailed specs, to implementation and results tracking, reporting directly to leadership. I'm organised, detail-oriented, and quick to pick up new tools, with a foundation in high-pressure admin work from McKinsey & Company. I'm looking to keep growing at the intersection of product, UX and public health, in step with my biology degree.
Right now I'm between roles, fresh off about a year and a half as a No-Code & UX/UI Specialist at Egala / Brocarga, basically owning a product from idea to shipped, no hand-holding. Before that I did a UX design internship at Lidl Polska, and before that I spent almost two years as an Executive Assistant at McKinsey & Company, so staying organised and calm under pressure is pretty much second nature at this point. These days I mostly design and build things myself, in Figma and no-code tools like Bubble and FlutterFlow.
Open to junior UX/UI, product and no-code roles. Reach out and let's talk about what you're building.
A vaccination tracker imagining what childcare could look like in Poland if the system went through a digital reform, designed for parents who are done chasing paper records and phone-only bookings.
Health is the number one priority to me. I want more people to be aware of the good things science offers us, and to take advantage of it for their wellness.
Initial research pointed to the same gap over and over: there is a real need for digitalising and developing medical apps that let parents schedule and track vaccinations, and get access to decent medical information, so they aren't left piecing it together from unreliable sources.
Estimated share of children still expected to be vaccinated by 2021, down from close to 100% just a few years earlier, and predicted to keep dropping.
The claim
The rate of vaccinated children has been decreasing over the last years, and it's estimated to keep dropping in the years that follow.
The problem
The number of people avoiding vaccinations is increasing, largely because parents are picking up medical "knowledge" from unreliable sources and the activities of anti-vaccine movements.
I looked closely at the 3 most popular apps available to Polish parents: their booking and tracking experience, missing features, and what real users were saying about them in app store reviews.
All three apps let parents search for a vaccination schedule.
None of them show a correct vaccination schedule alongside a child's health history (Pediatric on call), and none surface obligatory vaccines (Szczepienia).
I surveyed 24 parents with children between 0–18 years old who were interested in a vaccination schedule tool.
What are the challenges you encounter while scheduling a vaccine appointment for your children?
23 participants"I would like to have an overview of all available appointments near my home."
"I wish there was a simple app to track my kids' vaccination schedules and appointments."
"Misinformation is everywhere. I want access to reliable articles and doctors."
I built two personas around the two types of users this app serves: a working mom of four kids, and a busy dad who wants to stay on the same page as his wife.
"I want to stay updated with my wife regarding kids' health. I am also a parent."
"If we can schedule a hairdresser online, why don't we schedule doctor appointments as well?"
To outline all the necessary functionality, I mapped the main tasks a parent can complete. Fail-state flows were designed too, but are left out here for space.
A look at the core flows: signing up, managing profiles for every child, keeping every appointment in one calendar, booking a new one in a few taps, and getting help fast when it's needed.
The style leans on a calming blue to convey trust and safety, reflecting the app's focus on health and wellbeing. 42 high-fidelity screens were created in total, including two different navigation patterns (a tab bar and a hamburger menu), tested against each other for further design stages.
I picked an 8-point grid for the project, with 8 and 16 px margins within groups, and 24, 32 and 48 px margins between groups, keeping tap targets and spacing predictable across all 42 screens.
Immune 8 started as a "what if": what could vaccination tracking look like in Poland with a bit of digital reform? Grounding it in real survey answers and a proper competitive audit kept the design honest, and gave me a system I could carry into the next case study.
← Back to workA UX redesign of the lidl.pl webshop, grounded in a benchmark of 12 competing e-commerce sites, closing the gaps that were sending shoppers to guest checkouts, size guides and locker delivery elsewhere.
During my UX design internship at Lidl Polska, I was asked to look at where lidl.pl was losing shoppers compared to the rest of the market. That meant a full competitive benchmark of 12 competing e-commerce sites, reviewed feature by feature, paired with Google Analytics data on how people were actually behaving on lidl.pl itself.
I presented the findings and recommendations directly to leadership, then turned the highest-impact gaps into a set of concrete redesign proposals for the six areas below.
Competing e-commerce sites benchmarked feature-by-feature to find where lidl.pl was falling behind the market.
What was pushing shoppers off lidl.pl before the redesign?
From the Google Analytics funnel data and the competitive benchmark"I don't want to create an account just to buy something once. Half the time I abandon the order right there."
"The size never matches what the chart says, so I end up ordering two sizes just to be safe."
"I have to know my own street by heart to find the right locker. Just show me a map."
Six areas came out of the benchmark as the clearest gaps, from the product page itself through to how a parcel actually reaches someone's door.
Competitors let shoppers switch colour and size without losing their place. On lidl.pl, colour was buried in a dropdown and material info was easy to miss. I redesigned the product page around colour swatches you can see and tap directly, a size selector with a fit-confidence hint ("Pasuje idealnie, 71%"), and the material and delivery info surfaced right next to the add-to-cart button instead of scrolled below the fold.
Every competitor benchmarked let people check out without creating an account first; lidl.pl didn't. I designed a checkout entry screen with an equally weighted "Order as guest" path alongside login and account creation, so account creation becomes a choice instead of a checkout gate.
The redesigned homepage greets a logged-in shopper by name ("Witaj Zuzannah!") and gives saved lists their own, visually distinct spot instead of folding them into a generic menu, so returning shoppers land somewhere that already feels like theirs.
Personal details, delivery address, order history and Lidl Plus status were scattered across the old account area. The redesigned profile groups them under one "Moje Dane" view with clear edit access, so shoppers aren't hunting across pages to update a phone number or check a past order.
On the original site, checking or changing a size once an item was in the cart meant going back to the product page. The redesign surfaces size and quantity directly on each cart line, with inline controls to adjust either, one less round trip before checkout.
Locker delivery was one of the top asks from the competitive benchmark. I designed a delivery-method step with an interactive map of nearby InPost lockers, complete with opening hours, so choosing a pickup point is as easy as picking a pin closest to home.
This project taught me that a redesign is only as good as the benchmark behind it: every one of these six changes traces back to something the market had already proven shoppers expect. Presenting that case to leadership, backed by 12 competitors and real analytics, was as much a part of the job as the screens themselves.
← Back to workA real, shipped feature inside an internal freight-brokerage platform I owned end to end, giving brokers a live view of what they've earned, what's still pending, and why money is sometimes on hold.
As the No-Code & UX/UI Specialist on this internal platform, I owned this feature from concept through to a live release, writing the requirements, defining acceptance criteria, and working directly with leadership to ship it.
Before Broker's Wallet, brokers had no self-serve way to check their own numbers. Every question about earnings, invoicing status, or blocked funds turned into a message to finance, and finance had to stop and answer it manually, every single time.
Every earnings or payout question a broker had meant one direct message to finance, with no way to check it themselves.
What was slowing brokers down before Wallet existed?
Gathered from working sessions with brokers and finance during discovery"I don't need the money early. I just want to know what's happening with it before I have to ask someone."
"Raising a self-bill by hand means copying numbers from three different places and hoping they still match by the time I'm done."
"If a deal's on hold, just tell me why. I can usually fix it faster than finance can once I know what's wrong."
The problem
Brokers had no visibility into their own money. Earnings, pending invoices, and blocked funds all lived in finance's systems, so brokers chased answers by message and finance answered the same handful of questions on repeat.
The solution
One screen a broker can check any time. Wallet shows a live balance, a Pre-Wallet view of everything still in motion, and a payout flow that takes one tap, so finance stops fielding routine questions and brokers stop waiting on a reply.
Wallet is built around a broker's actual working mode: check the balance first thing, glance at what's still moving through the pipeline, resolve a dispute the moment it comes up, and withdraw in one tap once money is confirmed. No separate app, no waiting on finance, no manual request form.
The primary balance is money a broker can withdraw right now. Pre-Wallet is everything still working its way there: deals grouped by where they stand in the pipeline (collecting payment, invoiced, in transport), so a broker always knows what's confirmed versus what's still in motion.
A simple leaderboard of a broker's highest-margin deals, with the combined gross margin called out up top: a quick way to see what's actually driving earnings that month, without digging through a spreadsheet.
Before this, raising a self-bill meant pulling the sales amount and VAT rate from the deal record, checking that against what the carrier had actually delivered, and chasing an approval before anything could be issued. One mistyped figure meant a mismatched invoice, and a mismatched invoice meant another round of back-and-forth with finance. Self-billing invoices now show the VAT breakdown alongside the sales amount, a clear Paid / Pending status, and a one-tap PDF download, so brokers stop asking finance to resend documents they already have a right to see.
When a Proof of Delivery (POD) is missing or doesn't match the order, the deal's money is blocked automatically, and the broker sees exactly why, with the reason and the blocked amount stated on the card itself, not buried in a support ticket. Uploading the correct POD directly from that card is the entire resolution flow: once it's accepted, the dispute simply drops off the list and the funds clear.
This was the core of the ask: get money out with as little friction as possible. Withdrawing is a single screen: the full balance is pre-filled, the minimum payout is stated up front, and one tap confirms it. There's no separate request form and no waiting on finance to process it manually, so once a balance is confirmed, moving it to the broker's account takes exactly one click.
Broker's Wallet is the project I'm proudest of on my CV precisely because it isn't a concept: it's in production, brokers use it every day, and I carried it from a requirements doc to a released Bubble.io feature myself. It taught me that the best UX work in an internal tool is often just making a hidden number visible, and letting people act on it in one tap.
← Back to workA leadership-facing dashboard for an internal freight-brokerage platform: one screen that turns margin, revenue, exposure and cash flow into numbers a CFO can act on the same morning.
Before drawing a single card, I sat down with the CEO to walk through what actually mattered day to day: not every number the system could produce, but the handful that decide whether this week is on track. That conversation shaped the whole brief: which figures earn a spot at the top of the screen, which ones only matter when they slip, and which ones are for a details page, not the homepage.
I came back with a rough priority order: margin first, revenue and exposure right behind it, and cash flow watched closely because it's the number that turns a good month into a cash-flow problem if no one's looking.
Separate reports (margin, revenue, exposure, cash flow) that used to live in different places, now on one screen a CFO checks every morning.
What made the old way of tracking these numbers hard?
From the working session with the CEO and finance"I don't want fifteen numbers on a screen. I want the five that tell me if this week is actually on track."
"If margin starts sliding, I need to see it while it's still a trend, not after it's already a problem in the bank balance."
"Don't bury the spend in a separate report. Put it right next to the results it's supposed to be driving."
Every KPI on this dashboard carries a target, not just a value, because a raw number rarely tells a CFO whether to worry. €446K of gross margin means nothing on its own; €446K against a €1.15M annual goal, trending green, does. So each card pairs the actual figure with its target, a percent-to-target, and a small up/down delta versus the last period, the same shape repeated across margin, revenue, exposure and order volume so the eye learns it once and reads all four the same way.
A second row of cards goes one level deeper for the metrics that move the most within a period: gross margin, revenue, order volume and new customers each get a progress bar against their period target, colour-coded so a glance tells you whether something needs attention before you've read a single number. Amber and red bars carry a small warning icon, a deliberate nudge for the ones actually falling short.
The chart underneath is the same four metrics again, but plotted against time instead of a single period: goal and actual as two lines a CFO can flip between by metric and by Day / Week / Period. It exists because a single snapshot can hide a trend: a number can be on-target this week and still have been sliding for a month. Letting the same chart answer both questions kept the dashboard from needing a second page just for history.
Not everything belongs in a KPI card. An alert banner sits above the fold for whatever needs a human decision that day. Here, a rate change showing up across ten customers' order counts, with a direct call to action instead of a number to interpret. A status table below covers the operational trail: expenses, invoices and self-billing entries waiting on approval, colour-coded by status so the ones stuck in review stand out from the ones already moving.
Underneath the performance numbers sit the budgets that fund them: marketing, platform development, relay and overhead, each with its own trend and a quick upload for the underlying documentation. Small, but it was one of the more requested pieces from the interview: leadership wanted spend sitting right next to the results it produces, not buried in a separate report.
This one taught me that dashboard design starts before the UI, in a conversation about what a person actually checks first thing in the morning. Every card on this screen traces back to something the CEO said mattered, not to what the database happened to make easy to show.
← Back to workA digital health platform for women with endometriosis: a mobile app for tracking symptoms, cycles and pain patterns, paired with a marketing site, built end to end as the founder.
Endometriosis is common, and by most accounts still poorly understood even by the healthcare system meant to catch it. Diagnosis is frequently reported to take years, in large part because symptoms are inconsistent, easy to dismiss, and hard to describe precisely in a ten-minute appointment.
I'm building endoBestie as the founder, not just the designer: the product, the business case, and the grant applications that fund it are all mine to carry. The app gives women a private place to log symptoms and cycles over time, so a pattern that's invisible day to day becomes something concrete to bring to a doctor.
Founder-developer, building the app, the website, the pitch materials and the grant application myself.
What makes managing endometriosis harder than it needs to be?
From early conversations with women living with it, and outreach to specialists"By the time I'm in the appointment, I've forgotten how bad last week actually was. I need something that remembers for me."
"The apps I've tried are built for people trying to get pregnant, not for tracking pain. None of the fields fit what I'm actually going through."
"I don't just want to log the pain. I want to know if it's connected to what I ate or how I slept."
The home screen leads with streaks instead of a blank log: consecutive days of diet, physiotherapy and mindfulness, plus a one-tap mood check-in, so the small, unglamorous habits that actually help with symptom management stay visible instead of getting forgotten.
Diet and physiotherapy sit in the same daily plan instead of living in separate tools a person has to remember to open. Each physiotherapy exercise carries its own duration and can be favourited, so a short pelvic-floor routine or a five-minute breathing exercise is one tap away on a day when that's all someone has energy for.
Recipes are filterable by the restrictions that actually matter here, fish, vegetarian, dairy-free, gluten-free, rather than generic diet categories, so a meal suggestion doesn't need to be manually checked against a flare trigger before it's safe to cook.
Threads are tagged by what they're actually about, diagnosis, symptoms, treatment, diet, so someone looking for what to bring to a first gynaecologist visit isn't scrolling through unrelated posts to find it.
I've been reaching out directly to specialists, including urogynecological physiotherapists and dietitians, about contributing content and being listed here. Each profile shows a rating, years of experience and the specific areas they cover, so finding the right specialist doesn't mean hours in Facebook groups hoping someone else already did the legwork.
Outside the app itself, I'm sizing the market using GUS data, weighing company structures for the business, and preparing a HOT3 incubation application, on top of the investor pitch deck and design system. It's the part of the job no one sees in the screens, but it's what decides whether the product I'm designing ever reaches the women it's for.
endoBestie is different from every other project on this site because there's no client or employer setting the brief. I have to be the researcher, the designer, the developer and the person defending the business case, often in the same afternoon. It's taught me that founder-led product work is mostly about sequencing: knowing which of those hats to wear first so the next one has something real to work from.
← Back to work