I made a spreadsheet for all the data requests in here

Curious what columns you’re using. I do a boring n=1 sheet: weekly median weight, waist, average protein hit rate, and a 1–5 hunger/sleep

I steal this approach. My filter is “does this change one variable I control by Friday?” If not, archive. Columns: claim, n, effect size, cost to test, decision it changes. The 17 vibe checks usually fail at “cost to test” because they’re just someone’s n=1 plus confidence. Question: how do you score a post that has no study but a specific, repeatable protocol? I’ve got a “try for 2 weeks, log adherence and appetite” bucket, but it fills fast. 130g protein is boring in the best way; mine’s the same anchor. What’s your tie-breaker when two requests both pass the time-estimate test?

Congrats on 52 lbs — the boring-on-purpose habits are the part I trust most. I do something similar but keep a tiny “body signal” column next to any experiment: hunger, energy, sleep, digestion, and whether I’d repeat it on a bad day. That column has saved me from chasing things that looked good on paper but felt awful. Curious how you set your results plan: do you pick one primary metric and a stop date before you start? Also, is your 130g protein a floor you actually track, or more of a rough anchor? I’m trying to make my own tracking less noisy.

This is such a good filter. I keep a “two-week test” tab too: one habit, one measurable outcome, no changing anything else. If a claim can’t survive two weeks of my boring baseline, it goes in the maybe-later graveyard. Curious: what’s your cutoff for “clear time estimate”—specific number of weeks, or just any endpoint? Also, 130g protein is my north star. The only way I hit it without thinking is pre