# Slava+Design: Senior Product Designer who builds in code > I design apps that anyone can use. Fintech, payments and web3: wallets, payment apps, a POS terminal and a festival app, from research to launch. - Website: https://slavadesign.xyz/ - Email: hello@slavadesign.xyz - cv: assets/cv/Viacheslav-Ksendziuk-CV.pdf?v=2615212 - linkedIn: https://www.linkedin.com/in/viacheslav-ksendziuk-6364a9143/ - dribbble: https://dribbble.com/valimar - x.com: https://x.com/slavaksendziuk - medium: https://medium.com/@sls.dsgn - Skills: product design, mobile app, web3, UX design, UI design, design system, fintech, wayfinding, POS, web app, ticketing, UX research, event management, Figma plugin, design tools, design systems, AI, web design, visual identity, illustration, motion design, banking, hotel booking, typography, type design, posters, visual design, B2B, SaaS, medtech, LMS, redesign, white label, EV charging, edtech, healthcare ## Experience - Parity Technologies (2022-27) - Heartbeat (2021-22) - Lendflow (2021) - Glow (2020-21) - Halo Lab (2019-20) ## Work ### Polkadot App (2022-26) Ecosystem app that helps beginners plunge into the crypto world - Case: https://slavadesign.xyz/work.html?p=polkadot - Tags: product design, mobile app, web3, UX design, UI design, design system - Under NDA: the case opens with a PIN on request - Versions: 2026, 2024, 2023 ### Pocket Funding (2026) Flows to top up and send money by card, bank transfer or crypto, private and calm - Case: https://slavadesign.xyz/work.html?p=pocket - Tags: product design, mobile app, web3, fintech, UX design, UI design - Under NDA: the case opens with a PIN on request ### Web3 Summit App (2026) The festival app inside the Polkadot App: a program by time, a map of the venue, badges and your own sessions - Case: https://slavadesign.xyz/work.html?p=festival - Tags: product design, mobile app, web3, wayfinding, UX design, UI design - Under NDA: the case opens with a PIN on request ### Web3 Terminal (2025-26) A point of sale app for merchants that takes private dotUSD payments by QR or NFC and prints receipts - Case: https://slavadesign.xyz/work.html?p=terminal - Tags: product design, POS, web3, fintech, UX design, UI design - Under NDA: the case opens with a PIN on request ### Web3 Ticket App (2026) Event tickets you buy with a wallet, with no email or phone number - Case: https://slavadesign.xyz/work.html?p=tickets - Tags: product design, web app, web3, ticketing, UX research, event management - Under NDA: the case opens with a PIN on request ### Icon Rescissor (2026) A free Figma plugin that resizes icons, keeps the right stroke at every size and exports tokens - Case: https://slavadesign.xyz/work.html?p=icon-rescissor - Tags: product design, Figma plugin, design tools, design systems, AI - Screens: How the plugin grew: from resizing one icon to exporting tokens, feature by feature; Resize: a 48 px copy next to the original, then a card icon that grows in place and keeps its proportions; Scale Set: one icon becomes every size. Preset strokes, then Scale with a thinner base, then Lock on three sizes; Component Set and Finalize: variants Size=12 to Size=56, then a plain set turned into components and renamed by the pattern; Export: select icons on the canvas and paste their size and stroke as JSON and CSS tokens; Marketing materials for the Figma Community page: Resize; Marketing materials: Scale Set, every size with the right stroke; Marketing materials: Export, from canvas to code A designer routine is a product problem too. Eight or nine manual steps for every icon became one click, and the answers of the team became the roadmap. Icon Rescissor is a free Figma plugin that turns one raw icon into a full set of sizes, ready for a library. It resizes the icon, keeps the right stroke at every size, builds a Component Set, renames the layers and exports tokens for developers. I designed it and made every product decision. I did not write the code myself: Claude wrote it while I described what I needed. At Parity our team kept moving and resizing Lucide icons by hand. Preparing one icon for the library meant the same steps for every size: change the size, pick the stroke, rename the layer, collect the variants. Then repeat it for 8 or 9 sizes, and then for every icon in the library. I had this pain every day, so I decided to fix it for myself and the team. It started small: a resize for one icon and a way to generate a set of sizes from it. Then I kept asking the design team what they missed when they worked with icons, and added features from their answers. Step by step it grew into the whole pipeline, and in the end it even exports tokens for developers. My goal was a plugin that is simple and easy to use: select an icon, click generate, and that's it. People who need full control still get it, but it stays out of the way. I built it in my own time and published it in Figma Community in 2026. The code is open on GitHub (ayvendil/icon-resizer). Whole pipeline resize, stroke, size sets, Component Set, rename and token export in one plugin; 6 designers at Parity and Novasama used it for our icon system; 2 clicks instead of 3 to 4 minutes of manual work for 6 sizes of one icon, plus checking, components and renaming. Our library had 50 to 100 icons; 4 icon libraries ready stroke presets for Lucide, Phosphor, Tabler and Heroicons, all editable Core users: The plugin is for anyone who keeps an icon library in Figma, and for the people who build with it. - Designers: prepare icons for a library or a design system and want every size with the right stroke and clean names, without repeating the same steps. - Design system owners: need the same rules for all icons: one table of sizes and strokes, one naming pattern, and Component Sets the team can use. - Developers: need the size and stroke of each icon as data, not as numbers read off the canvas. Research: The main source was the design team. I asked the designers what they missed when they prepared icons, and their answers shaped the next features. That is how a simple resize grew into sets, presets, renaming and, in the end, an export for developers. I didn't study other plugins before I started. I looked at them later, when I was already adding the next features. Many of them were broken, and others had a UX so confusing that it was hard to understand where to click. Most only resize, some are paid. It confirmed what I thought: other people had the same problem, and nothing solved it well, so I kept going. A few details came from that look too: the sets moved from a Section to an Auto Layout frame, and stroke got three modes. Problem: Every icon in a library needs the same manual cycle for every size, and the stroke has to change with the size or small icons look heavy and big ones look thin. It takes a lot of time, the names drift, and developers get sizes and strokes by reading the canvas. Solution: Two tabs for the two ways people work with an icon. Resize changes the selected icons to a preset size, in place or as a copy next to the original, and keeps the proportions of icons that are not square. Scale Set builds every size from one icon in one click. (Solves: sometimes you change icons in place, and sometimes you build a whole set of sizes from one icon.) Three stroke modes, right in the header of the size table: Preset takes the stroke from the table, Scale calculates it from a base size and stroke with a live calculator, Lock leaves it as it is. Color shows the mode before you generate: orange for presets, mint for calculated values, gray for untouched. It works with icons that keep their strokes, not ones outlined into shapes, so the line stays editable at every size. (Solves: with one stroke for every size, small icons look heavy and big ones look thin.) Presets make it fit any design system. Sizes, labels and strokes live in a table you can edit, add to, cut down and reorder. Ready sets for Lucide, Phosphor, Tabler and Heroicons can be changed too. Names follow a pattern with a live preview, because every product names its icons differently. Export copies the size and stroke of the selected icons as JSON or CSS tokens for the design system and developers, and the same data now works as context for Claude. (Solves: every design system has its own sizes and strokes.) How we got there: - One use case at a time: The features grew one after another. First the work with one icon, then a set of sizes at once, then renaming by size and Component Sets, and at the end the export. Each step covered one group of people: someone who needs several sizes at once, someone who needs only one size, and someone who hands icons to developers. A few use cases, all about icons, that complete each other. - Free export: In other plugins, even ones that had nothing to do with icons, export was paid. I wanted a person who works with icons to export them for development without any extra tools. - Staying small: I decided not to grow the plugin any further and to keep it as it is. Some tools turn into Frankensteins: companies keep extending them to cover every case, and the product loses its main idea of being simple and easy. Think of a moka pot: its structure and function stay the same, only the shape and the color change, and that is decoration. I wanted the same for this tool: simple, and only for icons. - Describe, see, fix: Claude could not see the plugin, so I tested every version in Figma and sent screenshots and console errors. Over dozens of iterations, and a few full rewrites when fixes piled up into structural bugs, the main skill was to describe the problem exactly. That is how I caught bugs like Rename replacing an icon's name with its size, or a Component Set failing on an icon that was an instance. - Auto Layout, not a Section: The first sets landed in a Section. I switched the output to a horizontal Auto Layout frame that grows with its content and keeps the same gap, so a generated set is ready to use and easy to change. - Saying no: Most of my decisions were simplifications. Export became an overlay, not a third tab, because tabs are ways to work with an icon and export is a separate action. I dropped a canvas or presets source switch, because selecting icons and clicking a button is enough. I did not add tokens for variant properties like Filled or Weight: they differ between libraries, and that is already a different product. - Names and details: The size labels went from Caption, Body and Title to Micro through Max, because Title reads like typography, not an icon size. The column became Label, so it matches the {label} token. Reset defaults got a dark button with a red border, so it does not look like the orange main action. I also tried an uppercase redesign with square toggles, did not like it and rolled it back. Key contributions: - Problem to job: I turned a manual routine, 8 or 9 sizes per icon with a new stroke, a new name and variants each time, into one job for the plugin: one icon in, a ready set of sizes out. - Roadmap from the team: I asked the designers what they missed with icons and added features in that order: Component Sets, library presets, renaming and, at the end, export for developers. - Presets for any design system: sizes, labels and strokes in a table you can edit, add to, cut down and reorder, plus ready sets for Lucide, Phosphor, Tabler and Heroicons that can be changed too. The plugin adapts to a design system and to the stroke of a given icon set, instead of forcing one. - Stroke system: three modes, Preset, Scale and Lock, right in the size table, with a live calculator and a color for each mode, so you see the result before you generate. It works on icons that keep their strokes, so the line stays editable at every size. - Naming: a rename pattern with name, size and label tokens and a live preview of the result. I added it because every product names its icons differently. - Design to code: Export copies the size and stroke of the selected icons as JSON or CSS tokens for the design system and developers. Developers stop reading numbers off the canvas. - Scope and simplicity: I kept the plugin to one job and said no to what would turn it into another product, like tokens for variant properties. Two tabs named by the action and sizes from Micro to Max make it work without explanation. - Building with AI: I owned the product, UX and QA. Claude wrote the code, I tested every build in Figma and turned bugs into precise descriptions that could be fixed. - Launch and result: the name, the plugin icon, three promo screens, the README and the Community page. The plugin is free in Figma Community, the code is open on GitHub, and the whole design team at Parity and Novasama used it for our icon system. What I'd do differently: I would make my own visual design for the plugin. When I built it with Claude, there was no way to bring my design in, like there is now, when Claude connects to Figma through an MCP server. I even had my own design for the widget, but I built it from the components Claude could give me and focused on the UX first: it does not matter what components a tool is built from, what matters is how it works. "With AI as the developer, the gap between an idea and a working tool is how precisely you can describe the problem." ### Polkadot Website (2026) Five pages and a mobile version for the Polkadot App, with an identity built on frosted glass, chromatic light and dots - Case: https://slavadesign.xyz/work.html?p=polkadot-website - Tags: web design, visual identity, illustration, motion design, web3 - Under NDA: the case opens with a PIN on request ### Open (2021-22) Business banking for small companies in India, on mobile and web - Case: https://slavadesign.xyz/work.html?p=open - Tags: fintech, banking, mobile app, web app, design system - Under NDA: the case opens with a PIN on request ### Aire (2023) Hotel booking app, a UX course project from research to prototype - Case: https://slavadesign.xyz/work.html?p=aire - Tags: mobile app, UX research, UX design, hotel booking - Screens: Survey with 15 answers: what matters when people choose a hotel, how they use reviews and where they book; Journey map: how the interview participant felt at every step of booking. Tap a step to see why; Key insights from the affinity diagram and what they changed in the app; Search: from the home screen to results on the map; Compare: several places in one search; Hotel page: photos, details and reviews, the price is always at hand; Booking: room, checkout, card details and a QR code for check-in; Filters: price, breakfast, payment type and property type, the number of places updates with every step; AI travel assistant: long press on the search bar Aire is a hotel booking app that I designed as a study project for the Professional Diploma in UX Design at UX Design Institute in 2023. I did every step on my own: competitor analysis, a survey, user interviews and usability tests, then the journey map, structure, flows, wireframes, a clickable prototype and the UI. The course was built as a chain of small projects, from the first research to annotations for developers. I took hotel booking as my topic and went through all of them with it. In my survey almost everyone used Booking.com, but in interviews people called it cluttered and preferred the clean feel of Airbnb. My goal was a booking app that is as calm and clear as Airbnb, but made for hotels. Research A benchmark of 3 apps, a survey with 15 answers, user interviews and usability tests; Structure Affinity diagram, journey map, information architecture and user flow; Prototype Wireframes, a clickable prototype and annotations for developers Core users: The main users are people who book a stay online when they travel. - Travelers: In my survey 14 of 15 people looked at price first, and then at location and reviews. - People who compare: most use two or more booking services and compare prices, often in browser tabs on a laptop. - Map-first users: like the participant from my interview: they search by area on the map and check what is nearby before they book. Research: I started with a benchmark of Booking.com, Expedia and Airbnb: the main screen, search, date and guest pickers, results and the hotel page, with good points and things to improve for each. Then I made a survey with 12 questions and got 15 answers. Price and location mattered to 14 of 15 people, reviews to 12, and 13 relied on reviews always or most of the time. The big surprise was that 13 of 15 booked on a laptop, not a phone. A friend explained it: it is easier to compare prices in browser tabs. Then I ran user interviews and usability tests myself, and for the journey map I put them together into one participant: a project manager who travels for leisure. He booked a trip in Booking.com and in Airbnb while I watched and took notes. It showed the same picture: he got lost in cluttered results and similar room options, but felt comfortable with clean screens, a map and reviews from verified people. For him the photo was the main reason to choose a place, and the map was his main search tool. Problem: Booking.com was the app people used most, 13 of 15 in my survey. But it is full of ads, has too many filters and puts too much text on every card. Rooms look the same and differ only by price, and many people do not trust the reviews. Solution: A calm home screen with one search. You choose the place, then dates, then guests, step by step, with flexible dates and an option for pets. Results on a map and in clean cards with photos, price, location and rating. A hotel page with a real photo gallery, a map of what is nearby, verified reviews and a sticky bar with the price and Reserve button. Room selection in a popup instead of a long scroll, and a short checkout with a clear total and an installment plan. An AI travel assistant: a long press on the search bar opens a chat that suggests ideas for a trip, popular directions and cheap hotels, or answers a question. It came from the research: a simple answer from a host could take an hour or two. How we got there: - Benchmark: For every step of booking I marked what is good, what is okay and what needs to improve in each app. Airbnb showed how much a clean interface helps, Booking.com showed what happens with too much information. - Affinity diagram: I wrote one finding per sticky note from all my research and grouped them by the steps of the journey: home, search, pickers, results, filters, map, hotel page, room selection and checkout. Then I grouped them again to remove repeats. - Journey map: I mapped the journey of the participant from my interview. His mood dropped on the results page and in room selection, where there was too much information, so these became my main focus. - Structure and flow: From these notes I built the information architecture and a user flow from the home screen to payment, with every decision point. - Prototype: I shared the clickable prototype with friends and watched them go through it. It showed me small gaps I had missed and how people really use the screens. - AI from the start: In 2023 the teachers told us not to use AI. I used ChatGPT in my research anyway and started thinking about how AI could work inside a hotel app. Later UX Design Institute added a course on AI for UX, with prompting, for all diploma students. Key contributions: - Research: a benchmark of 3 apps, a survey with 15 answers, user interviews and usability tests that I ran myself. - Synthesis: an affinity diagram and a journey map to find the main problems. - Structure: information architecture and the full user flow from home to payment. - Prototype: wireframes and a clickable prototype that I tested with people. - UI: the visual design of the app. - Handoff: annotations for developers with a flow, descriptions and a legend. - AI assistant: the idea and design of a travel assistant inside the app, based on what people told me. "Most of a good screen is decided before the first pixel: in the research, the journey and the structure." ### Posters (2025-26) Poster series built on typefaces I drew while studying type - Case: https://slavadesign.xyz/work.html?p=posters - Tags: typography, type design, posters, visual design - Screens: May 68; May 68; May 68; Blues Profundo; Blues Profundo; de larch; de larch; Grafisch; Grafisch; Robotik Corp; Robotik Corp; Funky Blue in G Minor; Funky Blue in G Minor; Digging with Nyam-Huan Gan! Khi!; Digging with Nyam-Huan Gan! Khi!; Printing; Everything is a mirror; Brave New World, Skee Mask; East West Posters I made while studying type. Each task started with two or three letters. I drew a typeface from them to train my hand, then took the theme from its name and built a series of posters around it. It was a study of forms, series and styles. ### Lendflow (2021) Product that helps entrepreneurs grow and improve their business - Case: https://slavadesign.xyz/work.html?p=lendflow - Tags: B2B, SaaS, UX design, fintech - Under NDA: the case opens with a PIN on request ### EthosCE (2020-21) Redesign of a learning platform for doctors and nurses who grow their careers - Case: https://slavadesign.xyz/work.html?p=ethos - Tags: medtech, LMS, redesign, white label, design system - Archive project - Screens: Before and after; White label: each institution gets its own colors, but stays consistent with EthosCE; Course search: tags, filters and search to find a course for your specialty; Course page: files, credits and everything you need before you sign up; Course test: a calm interface for every stage of the course; Learning groups: find people with the same interests or ask a question EthosCE is a learning management system for healthcare professionals who want to take the next step in their careers. We rebuilt the outdated platform from zero, and I was responsible for its structure, key features and the design system. I worked on EthosCE in 2020 and 2021 through an agency. The client came with an old platform. They wanted more than a new look: new user experience patterns that bring in new people and serve current ones better. So we decided to rebuild everything and create a new platform. The client put all their trust in us and gave us full freedom, so the decisions about structure and features were ours. Structure A benchmark of competitors and a new information architecture for the whole platform; Courses Quizzes and course tests rethought for the new platform; Design system Ready for future expansion and for white label pages Core users: EthosCE works for three sides of medical education. - Healthcare professionals: take courses and exams and get credits to move forward in their careers. - Universities and hospitals: get branded pages to promote their courses and institutions. - Professors: grade students and give them feedback. Research: The old site was confusing: no clear structure and no logic in how people moved through it. So I started with the architecture, not with the screens. I made a benchmark of direct competitors and of adjacent ones, the platforms where people actually study. Quizlet was a big example for me because of its game system. I also read forums to find what people missed in competitors. Then I rebuilt the information architecture and the way from finding a course to finishing it. Problem: The platform was outdated in every sense: the visual design, the user flows and the structure. It was hard to engage new people and to keep the quality of service for current ones. Solution: A new structure for the whole platform, with course search built on tags, filters and search, so people spend less time finding the right course. A course page with files, credits and all the details before signing up, and a reworked flow of course progress and tests. White label pages for partners, and learning groups where people find others with the same interests. How we got there: - Before and after: The old platform looked like a website from another decade. The goal was a new look and new patterns, so the comparison shows more than colors. - Course test: By reworking the main flow of course progress, I made an interface that stays comfortable at every stage of the course. - Learning like a game: From Quizlet I took learning cards. Before the exam a student goes through self-check tests built on question and answer, and sees a mistake right away. Then I designed the exam on the same logic, with the result shown at the end. Instant feedback was the idea of the whole system. - White label: The platform was built so that different clinics and institutions can create their own courses in their fields. That is why it needed a white label: each one gets its own colors and page, but stays consistent with EthosCE. Partners can also publish content, a newsfeed and discussions in learning groups. - Social discovery: On distance learning platforms people miss each other, so group search became one of the main features. Key contributions: - Research: a benchmark of direct and adjacent competitors like Quizlet, and forums to find what people missed. - Structure: information architecture and user flows of the new platform. - Courses: search with tags and filters, the course page, and the test flow: self-check cards with instant feedback, then the exam with a result at the end. - White label: branded pages for universities and hospitals. - Learning groups: social discovery inside the platform. - Design system: ready for future expansion. "The old platform needed a structure people could find their way in long before it needed new colors." ### JUCR (2020) App that helps electric car owners find a charger and pay in one place - Case: https://slavadesign.xyz/work.html?p=jucr - Tags: mobile app, UX research, UI design, EV charging - Archive project - Screens: Wireframes for the clickable prototype; Profile: charging stats, cars, coupons and payment; Smart notification center; Charging: live status and coupons while you wait; Arriving at a free station and at a busy one JUCR is an app for electric car owners in Europe. It brings charging stations from different networks into one app, so you can find a free charger, start charging and pay without switching between apps. I led the design of the whole app, from research and UX to the layout, interactions, animations and the design system. I worked on JUCR through Glow agency in 2020, in a small team of three: a project manager, a lead designer and me. The agency gave me full freedom, so I led the project myself, and the lead designer brought feedback from the client and sometimes gave useful advice. The app did not exist yet, and I did all of it: research, UX and structure, the layout and interface, how interactions and animations work, some of the illustrations and the design system. We went through every stage and handed the finished project over to the JUCR team. EV drivers had a phone full of apps: one for each charging network, one for maps, one for payment. My goal was one app that does all of it, and does it simply. JUCR started in Berlin in 2020. A few days after the release the app was 26th in the German App Store. By 2022 the company had raised about €33M, and one subscription covered about 333,000 charging points across Europe. 333,000 charging points in one subscription by 2022, in the app I designed from zero; 26th in the App Store in Germany, a few days after the release; Smart notifications My idea: the app tells you when a busy charger is free or your car is charged Core users: The main users are electric car owners. Many of them charge at home, but on the road they depend on public chargers from many different companies. - Drivers on the road: want to find a working, free charger nearby and start charging in a few taps. - Regular drivers: want one subscription and one way to pay in every network, without a card for each company. - The business: wanted a strong app that saves drivers time and keeps them in one place. Research: I made a survey for EV owners in communities on Reddit and Facebook, collected the answers, sorted them and used them to prioritize features. I also talked with the JUCR team about their goals, looked at competitors and read their reviews in app stores with appfollow.io. To find the real pain points I used Jobs to be done. People said the same things again and again: they check several apps to see if a charger works, every app is missing something, and they want one app with all chargers and one way to pay. From this we got four needs: find any charging station in one app, pay with one subscription, see the charging status, and pay contactless. Problem: The EV market was young and had no standard. Every charging network had its own app, so drivers kept many apps on their phone and still could not always pay or see if a charger was free. Solution: One app for all chargers: a map with stations from different networks, the right connector for your car, and payment with NFC or a QR code. A subscription for charging, a live charging screen with time and kWh, and coupons from places nearby, like cafes, so the wait is not wasted. Smart notifications: the app tells you when a busy charger becomes free or when your car is charged. How we got there: - User flow: Before the screens I drew the full flow, from the welcome screen to the start of charging. It was big, but it helped to see every step and every edge case. - Wireframes and prototype: I started with wireframes and a clickable prototype and showed the client how the app would work before any visual design. It saved a lot of time and money: we changed things while it was still cheap. - Smart notifications: In research I saw that people wait next to the charger for hours. So I suggested notifications: go for a walk, use a coupon, and the app tells you when the car is ready or when a busy station is free. The client called it the killer feature, and many people used it actively. - Ideas beyond the brief: During the project I kept suggesting improvements that were not in the original plan, like the smart notifications. The JUCR team liked these ideas a lot, and many of them went into the app. - Free and busy stations: I designed two cases of arriving at a station. When it is free, you connect and start. When it is busy, you turn on a notification and the app tells you when it is free. Key contributions: - Research: a survey in EV communities, sorting the answers and prioritizing features, plus Jobs to be done to find the real problems of EV drivers. - Structure: information architecture and the full user flow of the app. - Prototype: wireframes and a clickable prototype to check the idea with the client early. - Interface: the layout and full mobile UI: map, station page, charging, profile, coupons, payment and notifications. - Motion and illustrations: how interactions and animations work in the app, and some of the illustrations. - Design system: built from scratch, so every screen of the app looks and works the same way. - Smart notifications: the feature that tells drivers when a charger is free or the car is charged. "The feature the client called the killer one came from people who told me they wait next to a charger for hours." ### Tilt (2020) Platform that connects students with colleges and financial aid - Case: https://slavadesign.xyz/work.html?p=tilt - Tags: edtech, web app, UX research, UI design, design system - Archive project - Screens: Information architecture, reworked when new flows were added; Dashboard: a to-do wizard shows what to do next; College search: personal results by location, majors and budget, or on a map; College page: overview, a cost calculator and campus life in tabs; Mobile: the dashboard works like an app, on the go Tilt helps students find colleges and financial aid. I redesigned its website and the platform for students, from research to the design system. I worked on Tilt in 2020 through an agency and led the design on my own, from scratch. Tilt's strength is a personal approach: a person at Tilt processes every application. My goal was to keep that feeling and make the way to college simple for students from 16 to 24 and their parents. Students fill out a short form, see colleges that fit them, and then manage their colleges and look for financial aid in one place. The project won a grant, and after that Tilt came back to us with a new task: a notification for the moment a student gets accepted to a college. Research Competitors and the real emotions of students who get into college; Structure Information architecture, reworked for new flows; Design system Built and handed over with the product Core users: Students from 16 to 24 who want to go to college but need help to pay for it, and their parents. Each of them comes to Tilt at a different time, from high school to their early twenties. - Students: want one place to see colleges that fit them and the status of each application. - Parents: want to understand the costs and help with the decision. - The Tilt team: processes every application and keeps a personal touch. Research: I looked at direct competitors, CollegeVine and RaiseMe, and at indirect ones, Coursera, edX, Skillshare and Udemy. I also watched videos of students opening their acceptance letters to understand the emotional side. Problem: Students who don't have money for college need a free place to find funding. Many of them start applications and give up halfway. Solution: A dashboard with a to-do wizard for the first visit: fill out the profile, find colleges, apply. College search with personal results by location, majors and budget, filters, and a map of colleges near home. A college page in tabs: an overview, a simple cost calculator, and social media with campus life and reviews. Cheering notifications and digital achievements keep students going. How we got there: - Information architecture: The first version of the product had no My Scholarships, Global Searching and My Awards. When they came, I reworked the information architecture to fit the new flows. - The acceptance letter: For the new notification we looked at how acceptance letters from Harvard arrive: people open them without knowing what is inside, and their reaction is pure emotion. We wanted the same feeling on the platform, so we designed an interaction where the student opens the news like a real letter. The client loved it. - Motivation: The main goal was to keep students from giving up halfway, so I added cheering notifications and digital achievements. - Mobile first for teenagers: Teenagers spend more time on phones than on laptops, so the mobile dashboard works like an app and lets them do their tasks on the go. Key contributions: - Research: competitors and the emotional side of getting into college. - Structure: the information architecture and its rework for new flows. - Platform: dashboard, college search, college page and mobile version. - Motivation: notifications and digital achievements. - Acceptance letter: an interaction that brings the emotion of a real letter from a college. - Design system: built and handed over to the client. "A teenager who gives up halfway needs a reason to keep going, so the platform cheers them on." ### Kinetik (2019) Platform that helps patients get to their medical appointments on time - Case: https://slavadesign.xyz/work.html?p=kinetik - Tags: healthcare, B2B, SaaS, UX design, UI design, design system - Under NDA: the case opens with a PIN on request - Archive project