Riley Wood

it starts clean. admin, editor, viewer. three roles, clear boundaries, everyone knows what they can do.

then the product grows. a customer needs access to one thing but not another. a team member needs editor rights in one context and read-only in another. someone asks for a role that's basically admin but without the billing tab. and suddenly you have eleven roles, three of them named some variation of 'editor-but-not-really,' and nobody is confident the permissions are actually right anymore.

At Product Hunt, we re on a mission to help builders find users and help users find the best new products.

We ve been at it for over a decade, and we ve accumulated a ton of data, but we ve rarely shared it with the outside world. Until now.

Would love to hear thoughts.
Here's my perspective.
I'm against AI slop, but I'm not against AI. I believe AI is a great tool but it also needs greats pilots to use it well. This is what I'm working on. AI Fluency.

Biggest marker of AI fluency is AI judgement. Where and when to use AI and where and when not to.

BAD AI JUDGEMENT