Laureen

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.

Three months ago our team tried an automated content workflow to publish fifty SEO articles in just one week. The speed was amazing. Our content calendar filled up faster than ever before.

Two weeks later the problem appeared in our search console metrics. Google labeled the mass-generated pages as low-quality content and our organic impressions fell by sixty percent. Readers left within seconds because the text had no original case studies, no data points and no real-world founder experience.

Our team paused the automation pipeline. Returned to manual drafting for the core guides. Now AI is used to build outlines create headline variations and arrange rough bullet points into logical flows.

Our team writes every paragraph, by hand adding our product mistakes and real performance metrics to the text. Organic traffic. Even surpassed the previous levels in just forty days.

I think one of the interesting things about vibe coding is how quickly you can end up with something that works.

As a product designer, I used to spend more time figuring out how something should work before seeing it in action.

Now I can build a working version with AI much earlier in the process.

But there s something I ve started paying more attention to.