Proof of concept
Psychology Tech
Usability test participants in 3 days
01 — Business Context & Goals
An Empty Space in a Crowded Market
The Opportunity
Olga Velichko is a clinical psychologist with a global Instagram audience. Her methodology — metaphoric associative cards — is evidence-based and clinically recognised. Between sessions, there was nothing. No digital extension. No way for clients to practice independently.
Her plan was a physical deck. I proposed testing digitally first — validate demand before print costs and logistics.
The Market Gap
Calm and Headspace solve ambient relaxation — not self-reflection or psychological methodology. Tarot and oracle apps lean into mysticism and divination. Neither overlaps with what Olga does.
After a global search, we found zero digital products built around metaphoric associative card methodology. Not a niche competitor. Nothing. That's not a gap in a crowded market — that's an empty space.
From Olga's existing practice to a pre-launch teaser — AI-generated visuals posted to Stories before the product existed.
02 — Problem
A Binary Choice — Neither Option Works
The Business Problem
Olga had a proven methodology and global client base — but no way to reach them at scale. Physical cards meant print runs, shipping costs, and weeks of wait. No digital product existed to carry her clinical framework between sessions.
The User Problem
People who want self-reflection tools are stuck choosing between generic meditation apps and mystical card readers. Nothing calm, grounded, and evidence-based existed — something that treats users like adults.
Success Metrics Defined
Ship something real before losing momentum. Validate demand before investing in print. Get feedback from Olga's actual audience — not assumptions.
What We Believed
Olga's audience would respond to something positioned honestly — not dressed up, not dumbed down
Metaphoric cards need framing to not feel like fortune-telling — the onboarding would have to do real work
People would pay if the product matched the quality of the methodology behind it
What We Didn't Know
Whether demand existed before the product existed — no pre-launch data
Whether a web app was the right format, or whether something simpler (PDF, Telegram bot) would do
How to position something that doesn't fit an existing category
What Turned Out Wrong
We assumed we needed more content before testing. After two Instagram Stories, 100+ people asked for access — with 1 deck and 2 meditations not yet live. Content wasn't the blocker.
We assumed people would want to understand the methodology first. They didn't. First reactions were emotional, not analytical — people responded to how the cards looked and felt before reading a single word of explanation.
Starting point — references, colour palette, and enough coverage to build from — welcome, onboarding, auth, cards, meditations, settings.
03 — My Role
What I Actually Owned
The digital product was my idea. Olga's plan was a physical deck — I proposed a digital version to test demand and reach a global audience without print and shipping costs. From that point, I owned everything except the psychological content and card artwork.
Scope
Product strategy, platform decision, UX, UI design, design system, and full technical execution — from design system to deployed product, including auth and infrastructure setup.
Collaboration
Olga as content owner, methodology expert, and primary tester. A small group of friends for early feedback. No developers involved at any stage.
Influence
Olga trusted the product direction completely. I led on scope, framing, and execution — every decision made together.
Timeline
May 2026
Idea to deployed product in 3 weeks of weekend work. Both of us working full-time in parallel.
Designed the system, then built it — design tokens, components, and code execution all owned by me.
04 — Direction
What We Decided to Build
A bilingual mobile-first web app where users draw metaphoric associative cards and listen audio meditations — framed as a psychology tool, not a spiritual one. One deck, two meditations, live and testable before anything else was ready.
1.
Mobile-First from Day One
Olga's Instagram analytics showed 80%+ mobile traffic. Her audience wouldn't switch to desktop to explore something found in Stories. Every layout decision was made for a phone screen first.
2.
Web App, Not PDF or Bot
The methodology needed to feel credible and designed. A PDF wouldn't work as needed, bot would've worked functionally but killed the positioning. The product needed to feel like something Olga could stand behind professionally.
3.
Ship with 1 Deck, 2 Meditations
Demand validation doesn't require a full library — it requires enough to give someone a real experience. One deck with proper card draw mechanics, flip animations, and hint text was enough.
Onboarding does the real work — framing metaphoric cards as self-reflection, not fortune-telling. Copy and flow took more time than any visual component.
05 — Impact
150+ People Raised Their Hand Before Anything Existed
Two Instagram Stories. No product live yet. Just a signal it was coming.
150+
Access requests
Real people asking for access from two Stories — demand is real before the product is public.
46%
Engagement rate
Across all views on Instagram — the positioning resonates before a single screen was built.
58
Usability test participants
in 3 days
Currently in progress. No ad spend. No launch strategy. Just Olga's existing audience and a clear, honest product promise.
3 weeks
Evenings and weekends to ship
From idea to live product — proves the designer-as-builder format can move fast enough to validate before momentum dies.
That's not a metric from a dashboard — that's real people raising their hand before there was anything to try. For a zero-budget, no-team side project, it reframed what "MVP" means.
This is the condensed version.
Want the full story?
The deeper sections cover: why the card fan layout took 6+ full rebuilds to stabilise, the real cost of AI-assisted development without an engineer reviewing output, what I cut and why (including animated blob backgrounds that felt distracting in testing), and what I'd do differently. Plus: 100+ unprompted access requests before the product was public.
Happy to walk you through the complete story at interview.
