Oleg Bazhyn
Contact

Process

How a project runs with me

From the first conversation to support after the handover, every project goes through the same six steps, whether it is a new product or the redesign of one that already runs. Each step ends with something you can see and check.

  1. Conversation

    You tell me about the product, I read it need by need

    We start with a short brief or a call: the product, the people who will use it and what has to work. I go through it need by need and ask about anything unclear, so we agree on what I own and what stays outside design. I sit with the people who will use an operations tool before proposing anything for it.

    • Your needs, in your words
    • What is in scope and what is not

    A brief, read need by need — Wage Fantasy Crypto

  2. Plan

    The jobs, the stages and the cost, before any screen

    I turn the needs into the jobs the product has to do and a plan of stages with dates. You see what each stage costs, and the work starts when you agree.

    • The jobs the product has to do
    • Stages, dates and cost

    Naming the jobs first — Productively

  3. Flows

    Flows and structure first, together with the developers

    I write the flows and the information architecture before the screens and review them with the developers who will build them. For each decision that matters, I bring the options I did not choose and what each would cost.

    • User flows
    • Information architecture
    • Decisions with their options

    One decision, weighed in the open — Productively

  4. Interface

    Every screen, with the states around it

    Then the high-fidelity UI for web and mobile, built from one set of components. Empty, partial, denied, stale and offline states are drawn in the same file as the main path, not left for a later ticket.

    • High-fidelity screens
    • States beyond the happy path
    • Components and a style guide

    Beyond the happy path — Nerd Town

  5. Prototype

    A working prototype in code, and instructions to build from

    When it helps, I take the design into code with OpenAI Codex and Claude Code, and I check the states, the layout and the accessibility myself. I don't show a prototype that hides the difficult cases. Handover is part of the design: decisions are written as instructions a developer can build from, not a picture to copy.

    • A prototype in code
    • Implementation-ready instructions

  6. Support

    Results you can check, changes you decide on

    Each result comes with what changed and what to check, and you accept a stage when it is right. After the handover I stay in touch: every new change is estimated first, and you decide whether it goes ahead.

    • Results to check
    • Changes estimated before they start

Working together

Two ways to work together

Tell me about your project