Kevin Johnson — A Guide

01 — WHY KEVIN

The pattern is systems clarity plus product taste.

The useful thing about my background is the overlap: I can sit inside a messy business process, understand the people and data moving through it, then turn that ambiguity into something teams can build, test, and actually use.

01

Find the real workflow

Before the solution, I map what people are trying to do, where handoffs break, and which constraint is creating the most friction.

02

Make it testable

Requirements, user stories, data fields, acceptance criteria, QA paths, and UAT need a shared definition of done.

03

Build the loop

For product work, I care about what makes someone return: the trigger, action, reward, and emotional payoff.

04

Ship the artifact

The proof is a screen, schema, prototype, flow, case study, test, or working product. Once it exists, the conversation gets sharper.

02 — THE GUIDE

There are a few ways to read me.

Pick the lens that matches why you're here. Each one reframes the same person — a builder who cares about taste, behavior, and getting real things into the world.

Choose a lens above, or just explore the dimensions below.

I make the artifact, not the deck.

I'd rather ship a rough working build than describe a perfect one. Native iOS, React prototypes, mobile apps — I go end to end: data model, auth, UI, motion, the small states most people skip. Four live projects on this page are proof, not promises.

→ Native SwiftUI apps with real auth, persistence & onboarding
→ React/Babel prototypes that feel like finished products
→ Expo React Native for mobile-first collection experiences
→ Supabase backends — data, auth, sharing, invites

4live projects building right now

3platforms in build — iOS, web, RN

∞small states others skip

Behavior is the real spec.

A feature isn't done when it works — it's done when it changes what someone does tomorrow. I design around loops: the trigger, the action, the reward, the reason to return. I obsess over the first session, the empty state, and the moment a product earns a second open.

→ Retention & habit loops over vanity features
→ First-run experience treated as the product
→ Quality of feel: motion, copy, micro-states
→ User psychology > feature checklists

1stsession is where I spend the most time

2ndopen is the metric that matters

0tolerance for dead empty states

Learning velocity is the moat.

I pick projects partly for what they'll force me to learn. In the last stretch that's meant SwiftUI motion, Supabase data modeling, AI-assisted development, and data storytelling. I get to working code fast, then go deep where it counts.

→ SwiftUI · React · React Native · Supabase
→ AI-assisted development as a daily multiplier
→ Data viz & storytelling (see Call of the Siren)
→ Ship → measure → learn → repeat, tightly

4stacks fluent & in active use

<1wkidea → working prototype

AIwoven into the whole workflow

Validate by building the real thing.

I don't validate ideas with surveys — I build the smallest real artifact and put it in front of people. I care as much about distribution and behavior as the feature set. High agency, low ceremony: I'd rather own the outcome than the org chart.

→ Real artifacts over decks & mockups
→ Distribution & behavior are first-class
→ Comfortable owning ambiguity end to end
→ Taste + speed as a competitive edge

Ownthe outcome, not the title

Shipthen learn in public

0→1is the part I love most

Curious, outdoors, in motion.

Off the keyboard I'm usually on a trail, tracking where I've been, or building small things for friends. I like systems for living well — journaling, reflection, collecting summits. A lot of my projects are quietly autobiographical.

→ Hiking & collecting summits (that's literally PeakDex)
→ Journaling, reflection & personal analytics (Momentum)
→ Music, history & data as story (Call of the Siren)
→ Bringing people together IRL (Lets)

Trailis where the best ideas land

Dailyreflection & review habit

Buildfor the people around me

03 — PROOF OF WORK

The workbench is the signal.

The strongest evidence is the trail of real work: requirements turned into shipped systems, data repositories made easier to trust, UAT cycles that catch misses early, and product prototypes that prove taste.

A founder workbench with product screens, code, maps, and design notes.

CURRENT OPERATING MODE

Clarify the system, then make the product real.

I work from concrete artifacts: a user story, a data map, a testable workflow, a prototype, a schema, or a native screen. Once it exists, teams can judge behavior instead of debating abstractions.

~4years in BA delivery

4active product builds

1operator owning the loop

01

Turn ambiguity into a sprint-ready shape.

Requirements, user stories, data fields, acceptance criteria, QA handoff, and UAT all need the same thing: a shared picture of what done means.

02

Make data easier to trust and use.

Data work becomes valuable when source systems, fields, mappings, quality questions, and access patterns are clear enough for teams to move without rework.

03

Make complexity feel calm.

Insurance workflows, AI platforms, product prototypes, maps, and habit loops can get dense fast. The craft is making them understandable without extra explanation.

RECENT RECEIPTS Evidence over adjectives.

BA lead for a project squad: scrum, requirements, stories, QA, UAT, and sprint organization New data repository design with mapping requirements and SME planning sessions AI platform SME support across analytics, business, and data teams Active product builds across Lets, Call of the Siren, Momentum, and PeakDex

04 — THE WORK

Four live worlds, one builder.

Each project is its own little universe — different surface, different thesis, different thing I'm learning. Step into any of them.

SOCIAL PLANNING Lets

Turns group-chat chaos into one decisive plan card.

DATA RITUAL Call of the Siren

Makes Bitcoin history feel like music, memory, and timeline.

LIFE ANALYTICS Momentum

Turns passive movement into a private reflection loop.

OUTDOOR COLLECTION PeakDex

Turns hikes into proof, progress, and a trophy case.

05 — THE RÉSUMÉ

Same story, three lenses.

Switch the view to read my experience the way you need to. Everything stays scannable — expand any role for the detail.

06 — NOW

Field notes.

What I'm building, learning, and chewing on lately. Curated, not a changelog.

07 — DIRECTION

A living roadmap.

Where I'm pointed across products, learning, craft, and life. It moves; that's the point.