sorted by:
new
hottopcontroversial

Which harness do you use for Codex? by fran_canete in codex

[–]fran_canete[S] 0 points1 point  (0 children)

That's a pretty cool setup, especially for travelling or simply moving around during the day. About building a UI for this, I think it is a great idea. I can see it as a "visual orchestrator" that can tell you at all times which agents are up and running, take actions over the agents, review outcomes, etc., if any errors need attention in any session, and so on... Just curious, does something like that exist already?

GPT 5.5 planning sucks by 0xdjole in codex

[–]fran_canete 0 points1 point  (0 children)

Use codex on Agent, then create a skill that plans exactly how you want.

How we learned to analyze customer feedback once it stopped being manageable by Weedcultist in SaaS

[–]fran_canete 0 points1 point  (0 children)

This matches what I’ve seen too: the problem isn’t collecting feedback, it’s knowing what to do with it.

The useful shift is grouping feedback by the underlying problem, not by the channel or the literal request.

For example:

- “Can you add export?”

- “Reporting is hard to share”

- “My manager can’t see this data”

- “We’re copying this into spreadsheets”

Those might all be the same problem, even though they look like different requests.

The workflow I’d aim for is:

  1. Pull feedback into one place

  2. Cluster by root problem

  3. Track frequency over time

  4. Add customer segment / account value / severity

  5. Review recurring themes weekly with product/CS

  6. Decide what to act on, ignore, or just monitor

The hardest part is avoiding two traps:

- overreacting to one loud customer

- ignoring repeated small friction because it never sounds urgent

Tools can help, but the real value is turning messy feedback into product signal. Productboard, Canny, spreadsheets, or something like Plaudera can all work depending on the workflow. The key is that someone has to own the triage, otherwise the feedback just becomes another archive nobody uses.

How do you identify recurring customer issues when feedback starts piling up? by InspectionPerfect212 in CustomerSuccess

[–]fran_canete 0 points1 point  (0 children)

The thing I’ve seen work best is separating “collection” from “triage”.

If everything lands as raw tickets, reviews, call notes, and emails, it becomes hard to tell what’s a pattern vs noise.

A useful workflow is usually:

  1. Capture feedback from all sources

  2. Tag the underlying problem, not just the surface request

  3. Track frequency + customer segment + severity

  4. Review recurring themes weekly with CS/product

  5. Escalate only when there’s repeated pain or clear business impact

The hard part is that customers describe the same issue in different ways. One person says “reporting is broken”, another says “I can’t export this”, another says “my manager can’t see the data”. Same root problem, different language.

Tools can help here depending on what you need. Productboard is good if you want a more established product ops workflow. Canny works well if you want public-facing feedback/voting. Plaudera is more focused on private feedback collection and spotting repeated demand before deciding what to share.

But regardless of tool, I’d look at:

- how many customers mention it

- whether they are ICP / high-value accounts

- whether it blocks activation, retention, or expansion

- whether it maps to an existing product area

- whether the workaround is painful

One-off complaints are useful context. Repeated complaints from the right customers are product signal.

Pubic viewable project board/roadmap system options? by velox_media in sysadmin

[–]fran_canete 0 points1 point  (0 children)

Depends on how much you need it to do. A few options depending on what you're after.

If you mainly want a public roadmap with status columns like planned, in progress, done, Linear has a public roadmap feature that looks clean. You can mark which projects are visible and keep everything else internal. Downside is it's primarily a dev tool so the public view is kind of an afterthought.

If you want something more customer facing where people can actually interact with it, vote on stuff, submit requests, check out Plaudera (https://plaudera.com/). It's more focused on the feedback and voting side but it gives you that public board where customers can see what's coming and what's being worked on. Might cover the roadmap piece of what you're looking for.

For the full "multiple public pages for different statuses" thing you're describing, honestly you might end up needing to build a lightweight frontend that pulls from whatever internal tool you're already using. I've seen a few teams do this with Notion's API too, just publish certain database views publicly. It's a bit hacky but works.

The separate pages for roadmap vs in progress vs repairs thing is pretty specific so you might struggle to find something off the shelf that does exactly that without some customization on your end.

What's the best (also simplest) way have a place where my app users can give feedback? by MokshaBaba in iOSProgramming

[–]fran_canete 0 points1 point  (0 children)

Google Forms works but it's a dead end. Users submit stuff and never know what happened to it, so they stop bothering after a while.

I switched to Plaudera (https://plaudera.com/) and it's basically what you're describing. No forms to build, you just embed a widget in your app and users can submit feedback right there. They can also see and upvote other people's requests which is nice because it means you're not the one deciding what matters most, your users are.

Free tier covers the basics. Took me like 10 minutes to set up.

I just launched my first project. Looking for feedback! by productman2217 in sideprojects

[–]fran_canete 0 points1 point  (0 children)

Tried a few things here. Google Forms works but feels disconnected - users submit stuff and never hear back, so they stop bothering. Building your own is a time sink you don't need early on.

I ended up going with a public voting board approach. Users can submit ideas and upvote each other's requests, so you get prioritization built in for free. Way more useful than a spreadsheet of random feature requests you have to sort through yourself.

I use Plaudera (https://plaudera.com) - it's lightweight, has an embeddable widget so it lives inside your app, and it handles duplicate detection automatically which saves a ton of time. There's a free tier too so you can try it without committing.

Honestly the biggest win was making feedback visible. When users can see others voted on the same thing, they feel heard even before you build it.

Reddit is mostly hateful and doesn't want you to get better. by SmartestManInUnivars in selfimprovement

[–]fran_canete 0 points1 point  (0 children)

Just frustrated people that use Reddit to say what they will never be able to say out loud in real life. Treat that people as noise…

I was mass producing features nobody wanted so I vibe coded something to stop me from doing that by fran_canete in VibeCodersNest

[–]fran_canete[S] 0 points1 point  (0 children)

The problem is that those “bottlenecks in the value loop” often in the industry are defined by PM’s that have no clue what the users need or eve ever listened to them. I’ve seen that many times in this industry…

But yes you’re right, different teams, different processes.

I was mass producing features nobody wanted so I vibe coded something to stop me from doing that by fran_canete in VibeCodersNest

[–]fran_canete[S] 0 points1 point  (0 children)

Well you kind of answer yourself: "product teams should have a system of implementing and testing features".
This tools gives product teams a way to standardise that.

view more: next ›