chanil-92

We talk a lot about retention, but I think there are products where people not coming back is actually a good sign.

If I use something to prepare for an interview or sort out a one-time problem, I probably don t want to keep using it. I just want it to work so I can move on.

Obviously that doesn t work for every product, especially subscription-based ones.

But it makes me wonder how much we rely on retention simply because it s easy to measure.

I ve been working on permission and role management for a B2B AI product.

One thing that makes this tricky is that a user s role doesn t always tell you what they should be able to do.

For example, someone might manage a project without managing the entire workspace. They need control over their project s settings and members, but that doesn t necessarily mean they should have access to organization-wide settings.

This creates an interesting UX problem.

I ve been using prototypes a little differently since I started building more with AI.

For internal reviews, I still find simple prototypes useful. They help the team understand the overall flow and discuss whether we re looking at the same problem.

But when I want to explore how an idea actually works, I often go straight to building a working version with AI.

The interesting part is that I m not necessarily trying to skip the design process.