Do any founders have a good method of applying A/B testing when doing feature iteration?

How do you split your test groups and collect feedback? Do you always test with people directly, or is there a smart way to implement it into the normal user experience?

Internet Stan | nickbrodeur.com | I like books, traveling, and coding

build, lift, & coffee | ENS Steward | namestone.xyz | slobo.xyz

I could see over-analysis being a waste.

But surely a/b testing provides better info on actual user preferences than their direct feedback, right?

a/b testing is harmful sub scale

talk to customers

Product researcher & /ux strategist, incubating ideas on Farcaster, experimenting with /firstdraft, journaling /angeluser | nf.td/markfishman

@markfishman would love to get your input on this :)

I try to limit A/B testing to slight differences in the UI, where you can see usage analytics in live builds.

If you’re trying to get qualitative feedback on what people want, do some mockups and get people to give you some feedback. Eventually ship the highest conviction thing and iterate on implementation