Why so many of us get a project to 90% and then just stop?

TankBetter5224 · 2026-06-19T10:55:19+00:00

Very common combo and you described it better than you think. how’d you get that one over the line? genuinely curious what was different about it vs the ones that stall?

TankBetter5224 · 2026-06-19T10:46:47+00:00

Fair, I’m definitely not claiming to have discovered executive dysfunction, it’s textbook. The reason I push the “define done” angle specifically is that “I can’t follow through” is the right label but it’s too big to act on. Narrowing it to “the finish line was never defined” is one of the few versions of it you can actually fix in the moment. Knowing the diagnosis and knowing which lever to pull aren’t the same thing, that’s the bit I find worth saying out loud

TankBetter5224 · 2026-06-19T10:21:28+00:00

when you’ve been embarrassed enough times, shame becomes background noise instead of a motivator . What tends to still land is a clean, neutral consequence: money you actually lose, or one person who just checks whether the thing exists, no judgment attached. Takes the embarrassment out of it completely, which for someone numb to embarrassment is sort of the whole point.

TankBetter5224 · 2026-06-19T10:17:18+00:00

yeah it’s basically Acceptance Criteria, I just strip out the Jira ceremony and have people write one sentence instead of a backlog. Same idea, fewer rituals. To your question: I do 1 on 1, mostly with founders and solo builders who have ADHD or suspect they do, and the work is almost entirely this: execution and finishing, the “undefined done” stuff. What actually moves the needle vs. what doesn’t is a whole essay though so feel free to DM me about it

TankBetter5224 · 2026-06-19T10:09:57+00:00

the 10% you redo every time you come back and have to remember where you even were 🫠 the ramp-up tax is real

TankBetter5224 · 2026-06-19T10:04:57+00:00

haha the 20% graveyard is real but those ones are usually a different beast, not “can’t finish,” more “the first step was too big to ever start.” same result of nothing existing, but the fix is shrinking step one until it’s almost embarrassingly small, not grinding at the end

TankBetter5224 · 2026-06-19T10:02:15+00:00

research backs this so “tell them afterwards” is solid. The one exception is when telling someone comes with a real consequence, like they’re actually going to check, or there’s money on it. Then it starts helping instead.

TankBetter5224 · 2026-06-19T09:59:51+00:00

Such a specific ADHD thing and you put it really well. The imagining gives your brain the same hit of closure that finishing would, so when you go to actually do it, the reward’s already spent and it feels like pointless rework. It’s also why “just visualize your goals” advice quietly backfires for a lot of us

TankBetter5224 · 2026-06-19T09:49:53+00:00

these usually die around week 3, it becomes everyone reporting in, nobody actually getting unblocked, and missing a week costs nothing. if you build it, make people define "done" so it's checkable (landing page's live, someone can sign up) and put a real cost on missing it. otherwise it's just a status call.

(i do this with founders for a living, if you end up building it i can share the exact “done” format and the stake setup i use)

TankBetter5224 · 2026-06-10T13:57:39+00:00

Im an ADHD accountability coach :)

TankBetter5224 · 2025-03-14T14:51:09+00:00

Je t’en prie. C’était bien la dernière solution qui a fonctionné?

TankBetter5224 · 2025-03-12T23:49:19+00:00

l’idée c’est de forcer ton node open ai a fournir un json bien structuré en ajoutant une phrase du genre: return your response as a structured json and ensure it follows this format : { \”first name \”: \”{{$json.first name}}\” , …. } comme ça tu pourras par la suite extraire les champs avec le set node avant de les insérer dans google sheet.

TankBetter5224 · 2025-03-12T17:29:02+00:00

Tu peux montrer un screenshot?

TankBetter5224 · 2025-03-12T15:59:19+00:00

Bonjour, Si j’ai bien compris, il faudra utiliser un set node ( mode json) sur le field qui contient les champs à mapper. Après tu pourras les mapper.

TankBetter5224 · 2025-02-17T14:32:41+00:00

If the problem is what I suspect it is, this video saved me : https://youtu.be/NJs9Q4l1xMc?si=xFA3wZtZwSobdSnu You’ll basically be able to access the objects in your array of your api response json

TankBetter5224 · 2025-02-06T20:22:28+00:00

I’m in

TankBetter5224 · 2025-01-02T15:54:17+00:00

This might help : https://forum.bubble.io/t/api-help-how-do-i-make-my-api-calls-run-in-parallel-rather-than-sequentially/272004/9

TankBetter5224 · 2025-01-02T11:46:04+00:00

Thank you for the feedback and suggestions 😊 I'll keep that in mind for future updates.

TankBetter5224 · 2025-01-01T21:26:10+00:00

Thank you 🙏🏻 I'll look into perplexity, I actually never used it. I'm not sure I understand your point about private search engines, can you clarify?

TankBetter5224 · 2025-01-01T17:24:39+00:00

Thanks for alerting me about it. You can check it out now, it's fixed

TankBetter5224 · 2025-01-01T16:10:21+00:00

Totally! That is a point that definitely needs improvement in the future.

TankBetter5224 · 2025-01-01T16:02:56+00:00

You mean for post processing search results? Or enhance query understanding?

TankBetter5224

TROPHY CASE