Context first
I dig into the business model, metrics and team constraints before the first mockup. Design starts with «why», not with references
Ten years designing products for finance, blockchain and B2B. I run design alongside product and engineering: hypothesis, prototype, validation, release, metric
Some projects are under NDA — I'll share details and process on a call
Every project follows the same rules — from the first call to release and a metrics review
I dig into the business model, metrics and team constraints before the first mockup. Design starts with «why», not with references
Every hypothesis has a number: conversion, session time, support cost. A decision without a metric is just taste
Components, tokens and rules that outlive a redesign. The team ships new flows without a designer in every ticket
Wording on screen matters more than decoration. I take copy all the way to buttons and errors so people understand what's happening without a manual
Specs, reviews and acceptance together with engineers. Design is done when it ships and works, not when it's drawn
Tests, analytics and iteration after release. I watch how the solution behaves in real life and fix what didn't work
Vyacheslav Maletskiy
Ten years designing interfaces in fintech, blockchain and B2B: from research and hypotheses to release and metrics. I work next to product and engineering instead of handing over mockups
Inside a project I dig into business, marketing and engineering processes: that gets me deeper into the product context and shows more possible solutions
I research and understand users' pains and emotions, then look for the way to help them
I look at a problem from several angles and switch between research, references and conversations with the team when I'm not sure
I work through every scenario and how elements behave in different contexts, and I sweat the copy down to each button label
I don't try to carry everything alone: a good product is the whole team working in sync, not just design
I plan ahead where and how each element sits on desktop, laptop and mobile, and on web, iOS and Android
Pedantic about spacing systems, copy, composition, hierarchy and typography — but I know when to stop
When the context allows, I look for unusual, elegant solutions instead of the obvious ones
I don't get emotional when things go wrong. I focus on the fix rather than the problem, and explain the reasoning to the team
I bring AI tools into the product cycle: AI agents for research, prototyping, coding and task automation. I connect design → AI → engineering through Figma, MCP, Claude and Codex, shortening the path from an idea and a mockup to a working prototype
Open to projects
Four tracks: product design, websites, vibe coding and AI automation. Describe the task — I will reply within the day with a format suggestion