DOC 01SHIPPED The product TASKDesign and build simple and intuitive interfaces focusing on mobile-first approach. PROBLEMThe original desktop app had grown over the years. Customers spend more time in the field than in their office, and need the ability to use the app on a device they always have at hand. SOLUTION Map the current state of assigned modules, if exists. Define user flow, asign roles and access. Design and test a functional prototype before shipping.
DOC 02LIVE Info Manager TASKDevelop a system to keep track of deadlines. PROBLEMA company has many entities and needs to monitor them and provide alerts when they require attention. SOLUTION From one date and one number (how many days ahead to warn) produce a status, a colour, a notification and an e-mail, for four kinds of objects: people, machines, jobs and the company. At most three urgent items per category on the overview. New entries are prefilled from existing registers. Add an audit log, so each change is recorded.
DOC 03LIVE Livestock Records TASKRevamp the livestork recording module to track primarily health-related data, as well as other information. PROBLEMData about an animal is created next to the animal, in the barn, phone in hand and often in dirty gloves, but it was only written down in the office in the evening, if at all. SOLUTION Designed phone-first: expandable cards instead of table rows, large touch targets and a bottom bar within thumb reach, the only one in the whole app. Treatments are added right on the animal, not on a separate screen, which saves two taps on every entry. Photos straight from the module, a status badge with colour and word, and repeated treatments grouped instead of ten identical rows. Pedigree and timeline answer different questions: where the animal comes from, and what happened to it.
DOC 04LIVE Meal Ordering TASKReplace the paper menu on the noticeboard: the administrator uploads the weekly menu, employees pick a meal for each day before the cut-off, and the kitchen gets one summary e-mail. PROBLEMPeople signed a paper sheet, someone had to copy it out and phone the kitchen every week, and anyone who wasn’t in the building that day was out of luck. SOLUTION Choices can change until the cut-off, as on paper; locking after the first click would have been worse than paper. A visible countdown shows how long is left. Uploading a new menu no longer wipes existing orders. It once did, and a whole company’s orders vanished. The kitchen e-mail can’t be sent twice: the check lives in the database, not in a disabled button. Most changes came from how the module behaved in use. One lesson repeated: it did things the user didn’t know about.
DOC 08LIVE Profile & settings TASKOne place where a user sets up everything about themselves rather than their work: account, password, signed-in devices, notifications, language and appearance. PROBLEMSettings were scattered: language in the header, appearance nowhere, notifications couldn’t be switched off, and there was no single place to say how you want things. SOLUTION A side panel on desktop that becomes a list with arrows on mobile, a different structure rather than a squeezed panel. Notification toggles appear according to permissions; a toggle the server wouldn’t save isn’t shown at all, rather than greyed out. Personal details come from the signed-in session, after a bug where a stranger could appear in someone’s profile. Install-as-app button only when the browser can really install it; dark mode that each page opts into, so older pages don’t break.
DOC 09SHIPPED Components TASKCreate a design system from a single base colour, and put it to work in Info Manager, Livestock Records and Meal Ordering. PROBLEM[ADD: what the screens looked like without a shared system] SOLUTION Primitives and semantic tokens; buttons in three levels plus a destructive variant. Inputs with all of their states, modals, cards, tiles, badges, empty and loading states, a focus ring. Dark mode defined as a second set of values, not an inversion. Monochromatic palette built from the primary blue, with yellow reserved for micro-accents where needed. Sign-in components Buttons Form controls
EVIDENCE6 EXHIBITS Visual concepts Select a photo to see it full size. Exhibit A · Warehouse Exhibit B · Warehouse flow Exhibit C · Table or chart Exhibit D · Lunches Exhibit E · Lunches flow Exhibit F · Week overview
DOC 01DEMO Brief TASKCreate a solution to improve CX for reporting a car accident. PROBLEMCurrent accident claim process is complex and time-consuming. People often feel stressed and are prone to make mistakes, when filling out personal or vehicle information. SOLUTION Rather than reinventing what is already digitalised I focused on improving the exisitng process with unique approach. Why focus only on the insurance claim and not the driver? Intuitive design that reduces cognitive load and provides clear guidance throughout the reporting process. No more drawing cars and the accident scene.
DOC 02DEMO Research & users TASKFind out and research existing solutions to determine what they offer and lack. PROBLEMExisting options converted the paper form into a digital one without addressing the core issues of the physical form. They started with the form itself, rather than the user's needs. People under stress cannot think clearly and require a guidance throughout the process. SOLUTION Rather than starting with the form, I focused on the user's needs and duties. Before the user gets to the form they are guided through 3 crucial steps: safety, injuries and calling emergency services. After making sure everyone is safe, the app helps users document the incident with minimal cognitive load. The situations are categorised into different approaches, whether another party is involved, drove off, or an accident with no other party.
DOC 03DEMO Analysis TASKMap every field of the European Accident Statement. PROBLEMEnsure that the proposed improvements are not too different from established practices. SOLUTION Each driver fills in their own half on their own phone exchanging information via a QR code. Designed an incidents page to display, track and manage reported accidents. Garage management features to store and organize vehicle information including information regarding ownership as the vehicle can be a personal, leased or company car. Based on this information the form would pre-fill relevant fields.
DOC 04DEMO Information architecture TASKStructure the app so the report itself has almost nothing left to ask. PROBLEMThe report needs data about the driver, the vehicle, its owner and the insurance contract, and people are stressed when they fill it in. SOLUTION Four tabs: Home, Reports, Garage, Profile. Every piece of data is entered once, in the tab that owns it. Ownership type does more work than it seems: personal, leased or company car decides who the policyholder is.
DOC 05DEMO Logo TASKA mark for an app people open on one of their worst days. The logo should evoke symbolism related to motor vehicles. PROBLEMFind a shape that is both a symbol of motion and a representation of a vehicle. SOLUTION Built from geometry: the ring between two circles is split into eight equal sectors, and the same cut removes a wedge from each. Removing one sector on the right opens the closed circle into a C, and the empty inner circle reads as a wheel hub. One shape that is both. The custom logotype follows the same rule: sharp inner cut, rounded outer corner, flat edges. Construction Logo variants
DOC 06DEMO Brand identity TASKColours, components and tone for a product people use a few times in their life, under stress. PROBLEMBlue is the default in insurance, so a blue app says “insurer”, and CLAIM isn’t one. SOLUTION Petrol instead of blue: calm without sameness. Amber as the accent, the colour the road already uses to say something happened (hazard lights, hi-vis vests). Every fill is bound to a variable in light and dark mode; tested screens had 97–100 % coverage. No illustrations. A cute drawing doesn’t soften a crash; restraint is the decision.
DOC 07DEMO Screens & prototype TASKTurn the structure into high-fidelity screens and a clickable prototype. PROBLEMThe structure was rebuilt five times, each time because the analysis revealed something, for example that a branch has to close before the first shared screen or the prototype can’t carry the choice. SOLUTION 36 screens with a token-based component library: a button in 36 variants, inputs, status pills, progress, segmented filter, bottom navigation and icons. Motion only where it explains something: the submark is a wheel, so on launch it makes one full turn and reveals the rest of the name. Open the prototype in Figma.
EVIDENCE4 EXHIBITS Visual concepts Select a photo to see it full size. Exhibit A · Key visual Exhibit B · App overview Exhibit C · Report flow Exhibit D · Garage & profile
DOC 01ARCHIVED Brief TASKRedesign the site to its next version with a focus on answering customer questions. PROBLEMPrices had to be requested, there was no information on materials, and getting in touch meant leaving the website. SOLUTIONA new design built on research and process mapping, with three new interactive parts: a price calculator, a materials page and a contact form.
DOC 02ARCHIVED Research TASKUnderstand the business, its customers and what the website has to do. PROBLEMTwo very different audiences: companies comparing in-house production with ordering a part, and households without technical knowledge. SOLUTION A technical and content analysis of the site. Data showed that mobile usage was dominant. A SWOT analysis and a comparison of six CMS platforms.
DOC 03ARCHIVED Price calculator TASKLet customers see what a print will cost without having to ask. PROBLEMThe price list was a static table of hourly rates. Every quote was calculated by hand, and for people outside the industry it was hard to tell which services they actually needed. SOLUTION An interactive calculator on the homepage: pick the services, the material and set the weight and print time with sliders. The estimated price updates live and is clearly marked as a guide price. The separate price list page was removed, which freed a menu slot for Materials.
DOC 04ARCHIVED Materials TASKHelp customers choose the right filament for their project. PROBLEMCustomers had to look up filament properties elsewhere, and while searching they could end up with a competitor. SOLUTION A new Materials page for PLA, PETG, ASA, PC and FLEX, each with a picture, key properties and a “Find out more” detail. A filter by strength, flexibility, heat, UV, chemical and moisture resistance, looks and biocompatibility.
DOC 05ARCHIVED Contact TASKMake it easy to get in touch from anywhere on the site. PROBLEMThere was no way to send a message from the website itself. SOLUTION Phone, e-mail and social links moved to the footer of every page; one tap opens the phone or mail app. A contact form with an automatic confirmation that the message arrived.
DOC 06ARCHIVED Build TASKTurn the mock-ups into a fast, responsive site the owner can keep editing. PROBLEMThe page builder Elementor generated a lot of extra code, which slowed the site down and limited fine control. SOLUTION Moved to the native Gutenberg block editor on the free Neve theme: cleaner code, better SEO, more control. Separate hero layouts for desktop and mobile, full-width buttons and a hamburger menu on phones. A redesigned logo, an orange-white-grey palette (60-30-10) and a sans-serif with full Slovak diacritics. A custom back-to-top button in HTML, CSS and JS instead of buying the premium theme.