Projects · a quick tour

Six projects, from marketing systems to a daily dungeon game.

Different subjects, the same way of working: clarify the question, build the useful system, check the result, and explain the boundary.

You do not need a technical background to follow these. Each project starts with a clear problem, shows what changed, and keeps the deeper method optional. Some have a measured outcome; others show the build and judgment honestly.

A clear starting point Start with marketing measurement. It is the closest match to my day job. The rest of the directory branches into operations, research, and product work.
corrected cost per customer in the selected 25
11 of 446 Options verdicts cleared the research gate
1 in 412 source clips marked used in the production ledger
0 ideas cleared the bar in the August 21 paper snapshot
Start with the professional work

Six builds, organized by the kind of problem they solve.

Marketing measurement and the day job are the closest fit. The job-search and video systems show operational range; Options and Sports show research discipline; Delve shows product and creative range.

Some projects produced a measured result. Some did not, deliberately. Each one shows the question, the build, what failed, and the judgment that followed.

Want the professional context first? Start with the day job, then come back to the projects.

01

Marketing & Measurement

The closest match to the day job: reporting, attribution, and decisions.

Case study

Marketing Measurement

Checks whether reports counted conversions that arrived after the budget decision.

I built a plain-language way to compare what a report says today with what a marketer could have known when the budget decision was made. This is the closest match to my day job and the easiest place to start.

Corrected cost per customer was about 4× higher in the selected 25.

Read the marketing measurement case →
Supporting method

Measurement Method

The deeper evidence trail behind Marketing Measurement.

The planned checks, supporting charts, and source record for readers who want the technical layer.

Read the method →
02

Automation & Operations

Systems that reduce repetitive work while keeping the decision human.

Case study

Job Search Workflow

Narrows job postings to a shortlist worth reading.

It reads many sources and narrows the list against a written profile. The useful output is a smaller shortlist that I can actually read and evaluate.

683 roles screened; 57 worth reading first.

See the workflow →
Case study

YouTube Workflow

A clip-sifting and editing pipeline with an owner release check.

I play the games and choose what is worth sharing. The workflow handles the repetitive work of finding, formatting, and remembering what the channel has already used.

33,365 clips entered the funnel; 150 reached owner review.

See the video workflow →
03

Research Systems

Paper-only systems built to reject weak ideas before they become action.

Case study

Options Research

A paper-only testing process designed to make ideas fail safely.

The system runs experiments, checks them against controls, and keeps the results away from real money. The useful story is the discipline around saying ‘not enough evidence.’

15,412 backtest results; 11 of 446 cleared the gate.

See the options research →
Case study

Sports Research

A testing process that writes down how a sports idea could be rejected.

This project turns a hunch into a fair test, records the answer, and refuses to call something a win just because the first result looked interesting.

814 questions logged; none cleared the bar in the August 21 paper snapshot.

See the sports research →
04

Product & Creative

A small product built around a clear return loop and honest release boundary.

Case study

Delve

A small daily dungeon game built around returning.

I wanted a game I would actually open tomorrow: a short session, meaningful choices, different ways to play, and a collection that gives the next run a reason to exist.

Five floors, four classes, six themes, and a Friday boss.

See the build story →
Shared method

The shared operating standard underneath all six projects.

It asks where a number came from, what would change the conclusion, and who controls the release call. The other projects show the same discipline across marketing, research, media, and product work.

See how I check the work →
How to read these

Start broad. Go deeper only if useful.