Same brain, different angles.

Turbo Isn't a Gift — It's a Lever

Lyft's Turbo mode offers drivers a small per-ride bonus in exchange for maintaining a high acceptance rate. On the surface, it looks like a reward. In practice, it's a behavioral nudge that pressures independent contractors to act like employees — accepting every ride regardless of profitability.

Run the ABCs: the antecedent is the Turbo badge and streak counter in the app (constant visual pressure). The behavior is accepting rides you'd normally decline — long pickups, low-pay trips, surge-adjacent dead zones. The consequence is a small bonus that doesn't offset the cost of the bad rides you accepted to keep it.

I tracked my own data across weeks with and without Turbo active. The weeks I chased the bonus, my effective hourly rate dropped. The app was optimizing for their metric (acceptance rate) at the expense of mine (profit per hour). The bonus wasn't a gift — it was the cost of my compliance.

The Acceptance Threshold Is a Point of Performance Problem

Rideshare apps give you seconds to decide on a ride. That's the point of performance — the exact moment where a decision happens. Most drivers either accept everything (and lose money on bad rides) or cherry-pick aggressively (and tank their acceptance rate, losing bonuses and priority).

I built a simple decision tree — a printable heuristic — that reduces the decision to three numbers: $/mile, $/minute, and estimated hourly. If two out of three clear the threshold, accept. If not, decline. No mental math, no gut feelings, no guilt.

The insight isn't the numbers — it's recognizing that the problem is cognitive, not mathematical. Under time pressure, with dopamine hits from streak counters and Turbo badges, your brain can't make rational calculations. The decision tree is an antecedent intervention: it changes what's available at the point of performance so the right behavior becomes the easy behavior.

Watch → Record → Adjust: The Loop That Keeps My Week on the Rails

Every system I've tried for "getting organized" eventually collapsed. Planners got abandoned. Apps got cluttered. The problem wasn't the system — it was that they all assumed a neurotypical brain that can maintain consistent routines through sheer intention.

So I stopped looking for the perfect system and built a three-step loop instead:

Watch: Observe what's actually happening without judgment. What did I do this week? Where did I stall? What flowed? This isn't reflection — it's data collection. Record: Write it down. Not a journal entry — a quick log. What worked, what didn't, what surprised me. Timestamped, short, honest. Adjust: Change one thing. Not five things. One. Reduce the friction on what stalled, or double down on what flowed.

This is just the ABC framework applied to yourself. The antecedent is the weekly check-in (I do it Sundays). The behavior is making one small adjustment. The consequence is compounding improvement over weeks and months — not perfection, but momentum.

The Environment Always Wins

In behavior science, when a behavior isn't happening, the first question isn't "what's wrong with the person?" — it's "what's wrong with the environment?" Is the antecedent clear? Is the behavior easy to perform? Is the consequence immediate enough to matter?

I see this everywhere. A dog park where guests don't clean up isn't a "bad guest" problem — it's a missing dispenser at the exit. A warehouse where pickers make errors isn't a "lazy worker" problem — it's a bad label design at the point of performance. Cart abandonment at a retail store isn't a "theft" problem — it's a friction problem in the return flow (that's literally the whole Cartma case study).

This applies to personal life too. I don't keep junk food in the house because I know the antecedent (seeing it in the pantry) makes the behavior (eating it) almost inevitable. I charge my phone in another room so the antecedent for doomscrolling is removed at bedtime. I'm not more disciplined than anyone else — I just redesign the environment instead of trying to override my brain.

Good Enough to Ship Beats Perfect in Your Head

I have a folder of abandoned projects. Ghost Counter. Cable-Box Reinvention. Monster Pixel Packs. Each one was going to be "the thing." Each one died in the planning stage because I wanted it to be perfect before anyone saw it.

The projects that actually exist — Paws of Olympus, the apparel line, this portfolio — all shipped messy. The first version of every one of them was embarrassing. But they were out there, getting feedback, getting better. The abandoned ones are still sitting in a folder, pristine and useless.

In behavior science terms: I was trying to engineer the consequence (public approval) before performing the behavior (shipping). That's backwards. You don't get feedback on things people can't see. Shipping is the antecedent for improvement, not the consequence of it.

Building in Public Is Accountability You Can't Fake

"Build in public" sounds like a content strategy, but for me it's a behavioral intervention. When I commit to sharing progress — even rough, incomplete progress — I'm creating an antecedent that makes follow-through more likely. There's now a social consequence (people saw me start this) that reinforces the behavior (keep working on it).

This isn't about personal brand or clout. It's about recognizing that my ADHD brain discounts future rewards. Finishing a project "someday" isn't motivating enough to override the immediate pull of a new idea. But "people are watching and I said I'd update them Friday" — that's an immediate enough consequence to keep me in the loop.

It also invites help. When I posted early Cartma concepts publicly, people pointed out edge cases I'd never considered. When I shared rough apparel designs, friends told me which ones actually resonated. The feedback only exists because the work was visible.

AuDHD Isn't a Superpower and It Isn't a Tragedy

I'm tired of both narratives. The "ADHD is my superpower!" crowd ignores the executive dysfunction, the emotional dysregulation, the relationships strained by forgotten promises. The "it's a disorder and I'm broken" crowd ignores the pattern recognition, the hyperfocus sprints that produce genuinely original work, and the creative problem-solving that comes from a brain that won't stay inside conventional lines.

AuDHD is neither. It's a different operating system. Like any OS, it has things it does well and things it handles poorly. The job isn't to celebrate it or mourn it — it's to learn the specs and build accordingly. My brain discounts future rewards? Build shorter feedback loops. I'm prone to analysis paralysis from autistic pattern-matching? Ship earlier and iterate. I get overwhelmed by sensory input? Design my environments with that in mind.

This is behavior science applied to yourself. Know the antecedents that trigger your struggles. Design environments that make the right behaviors easy. Create consequences that are immediate enough for your brain to care about.

Boundaries Are Kind — Especially to Yourself

With AuDHD, I have a tendency to overcommit. The ADHD side gets excited about new ideas and says yes to everything. The autistic side wants to deliver perfectly on every commitment. The combination is a recipe for burnout: too many promises, each one with impossibly high internal standards.

I learned — slowly, painfully — that boundaries aren't selfish. They're the antecedent intervention that prevents the burnout behavior. Saying "I can't take this on right now" isn't rejection — it's me protecting the quality of the commitments I've already made.

This applies to time, energy, relationships, and especially to new project ideas. My brain generates ideas constantly. The boundary isn't "stop having ideas" — it's "ideas go in the backlog, not on the active list, until something ships." That one rule has done more for my output than any productivity app ever did.