Craft · Core Competency

Research I run myself, and experiments instead of arguments

Research that produces a deck nobody reads is a cost. Research that changes what ships — or stops something that shouldn’t — is an engineering investment. I run the interviews and the usability sessions myself rather than reading someone else’s call notes, put the riskiest flow in front of people who have not seen the system, and where the traffic allows it, settle the argument with a controlled experiment instead of a meeting. The measured programme I can show is the homepage of an eight-figure e-commerce funnel in 2017–18. Beyond that, an early-access page on which the first customers of a fintech product connected their data, and a marketing site for a biometrics platform that I built myself — neither with an A/B number behind it, and I would rather say so here than have you find out later. Accessibility gets the same treatment: mechanics in the stylesheet you are reading, measured, rather than an audit booked at the end.

Specialization
Discovery, Usability & CROUser interviews, moderated usability sessions, A/B and multivariate tests
Scope
Funnels, Fintech, BiometricsAn 8-figure e-commerce homepage, discovery with small-business owners inside a bank-channel product, a face-recognition gate
Core Tooling
GA Content Experiments, Hotjar, FigmaPersonas, journey maps, wireframes and prototypes, Webflow
Primary Metric
+6.73% Measured Lift100% probability of outperforming control; never shipped, and costed
187K Sample
Sessions Across the Decisive Three-Arm Test, 43 Days
100% Confidence
Probability of Outperforming Control
4 Rigor
Sequential Experiments, Aug 2017 – Mar 2018, One Decisive
5.38 : 1 Accessibility
Contrast of the Accent on This Page, Measured Per Theme
01 · Evidence

Where this showed up in real products

UvoteamHomepage CRO
The Homepage of an 8-Figure Funnel, Tested Instead of Redesigned
The page a new visitor saw first had been redesigned for years on instinct. Four sequential experiments, each built around one controlled dimension; 187K sessions across the decisive three-arm test; a winner at +6.73% with 100% probability of outperforming. It was never shipped, so I costed that decision for the stakeholders.
Read the case →
upSWOTDiscovery → Activation Page
Why Owners Wouldn’t Connect Their Data — and the Page on Which They Did
Interviews showed small-business owners felt assessed, not helped, when a bank asked for their books. No interface fix answers a motivation problem, so the response was a direct-to-SMB product, and its early-access page does the asking without saying it: three steps to early access, a progress bar that counts connected apps, a reward at each checkpoint, trust badges in the header. The first customers connected.
Read the case →
02 · Method

How I actually do it

STEP 01
Interviews and Funnel Data Before Hypotheses
Never test a random idea. A hypothesis starts from a leak in the funnel data — the page a new visitor lands on, the activation step, the screen where a free user decides whether to pay — or from what people say in interviews, and the two disagree often enough to be worth running both. On a bank-embedded fintech the interviews showed a motivation problem no screen could fix, so the answer was a different product, not a better form.
STEP 02
Usability-Test the Flow That Fails in Public
The flow worth a moderated session is the one that fails in front of other people. Liveness instructions for a biometric gate — which have to work at a glance, in a hurry, for someone who has never seen the system — were usability-tested before they shipped. An enterprise HR platform went from personas and journey maps through wireframes and prototypes to usability tests of three roles on one data model. The question is never whether they liked it; it is whether they got through without being told how.
STEP 03
Isolating the Variable
Test variations along one controlled dimension at a time. Holding block structure constant and changing styling alone is how the one decisive result was produced — and why it transfers to the next page instead of being a lucky accident.
STEP 04
Statistical Rigor, Sample Size, Segments
Run experiments long enough, across new and returning traffic, and segment by device from the first day. Use Bayesian probability of outperforming rather than a read taken too early — on a large funnel an early read produces a number that is confidently wrong, and one wrong call ends a team’s appetite for testing.
STEP 05
Accessibility as Mechanics, Not an Audit
I will not claim an audit I cannot show, so the evidence is the site you are reading. One focus rule for every interactive element, visible in both themes — it replaced a password field that hid its outline behind a border too faint to count as one. A skip link and a main landmark on every page. Scrollable results tables reachable from the keyboard, because the columns past the edge are the point of the table. Reduced motion honoured in one rule, added after a review found the motion page promising it and the stylesheet not delivering it. Contrast measured per theme, not assumed: the accent sits at 5.38:1 in light and 8.60:1 in dark; the one it replaced measured 3.71:1 as a link and 4.10:1 under white button text, so it failed twice. And one adjacent habit from early on: self-service terminals in Arabic and Urdu taught me that localisation is a layout problem before it is a translation problem.
STEP 06
Translate It Into Money, Including the Cost of Not Shipping
Convert the delta into currency, conservatively — the floor, not the ceiling, because a number nobody can argue down is worth more than one that invites argument — and put it in front of the people who decide. When the organisation does not ship the winner, put a number on that too. The strongest result of the programme on the eight-figure funnel was never rolled out; the forgone-revenue figure is the case I should have made beforehand rather than documented afterwards.
03 · Stack

Tools, in service of the above

Analytics & Experiments
Google Analytics Content ExperimentsHotjar funnels, step drop-off, session recordingsBayesian probability of outperformingNew vs returning and device segments
Research & Discovery
User interviewsJTBD framingModerated usability sessionsPersonas & empathy mapsJourney mapsRole-based IA
Accessibility & Localisation Mechanics
Contrast measured per theme:focus-visible on every controlSkip link & landmarksKeyboard-reachable scroll regionsprefers-reduced-motionArabic & Urdu terminal layouts
Pages & Variants
FigmaWebflowCoded prototypes: HTML, React, VueStorybook states
The full version

What the complete version of this page adds

  • The GA Content Experiments table for the decisive test, and the round-by-round account of the other three
  • The Hotjar funnels behind each conclusion — variant against control, step by step, round by round
  • The forgone-revenue calculation, and how it was presented to stakeholders
  • The early-access connect page of the direct-to-SMB product, at desktop and at 320px — the activation page behind the line 'the first customers connected'

It lives at alex.zhovnir.com/craft/research-and-data, behind a password — client agreements, not theatre. Send me a note and I’ll open it: alex@zhovnir.com.