Original Summary

I do automation work for small businesses, and the most common request isn't "add a feature." It's "give me back the thing you took away." A field they used to edit directly. A report they could tweak without filing a ticket and waiting a week. The hard part isn't letting someone poke at the software. The hard part is deciding what they're allowed to poke at without breaking what sits underneath it. I've seen a client-facing edit button wired straight to a column that three other features quietly depended on. One edit, three regressions, no error message to explain why. So the real fix for locked-down software isn't more configurability. It's a clear boundary: here's what you can touch, here's what happens when you do, and here's the undo if you're wrong. Most products skip the undo because it's the expensive part to build, not the exciting part. Curious if anyone here has shipped real user-facing extensibility that survived contact with actual users without turning into a support nightmare.   submitted by   /u/KimLikeJ [link]   [comments]

  • 情报分类：综合情报
  • 分类依据：内容未命中明确的垂直分类规则，归入综合情报
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/5 02:38:06