设计与产品twitter.com
企业软件为什么这么难用
Why Enterprise Software Sucks
2019 — 2024，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
这条推文串讨论企业软件为什么难用，围绕购买者与使用者分离、企业流程复杂、功能臃肿和内部工具用户没有选择权等角度展开。评论里既有真实教育平台的一线踩坑记录，也有开发者对企业采购与工作流现实的辩护。
为什么经久不衰：因为它用“买单的人不是使用者”点破企业软件的激励错位，并引出复杂工作流与可配置性的权衡，今天读仍能解释大量糟糕的 B 端体验。
HN 评论精选
一线教师用具体流程说明：功能繁多的教育平台因忽视真实工作流而变得几乎不可用。
我在一所使用 Frog VLE 的学校工作。学校大力推动我们用它做学生评估，我试过，真的试过。作业要求上传 .py 文件却被禁止，学生只能交 .txt；查看提交时只显示前 5 份，每份都要下载、本地改回 .py、测试、打分，再点 5 到 10 次到另一个页面录成绩，返回后翻页逻辑还会把第 6 份打回第一页；到第 30 份时一次作业可能要点五十次，4 个班还不能合并批改。我花了几周最后放弃，改让学生邮件交作业。这些平台功能齐全，却由从未踏进教室的人委托、设计、测试和开发。
MarcScott查看英文原文
I worked at a school that used the Frog VLE. There was a big push for us to use it for student assessment. I tried, I honestly did. 1. I used it to set homework assignments. 2. .py files were blocked and students couldn't upload them. 3. They submitted code as .txt instead. 4. I'd click on my class to view submissions, it showed the top 5 submissions. 5. I'd click on a submission and it would download. 6. I'd view the submission locally. 7. I'd convert to .py to test the code worked. 8. I'd assign a grade. 9. I'd then have to click (maybe 5 - 10 times) through to a different page to record the grade. 10. I'd then have to go back to the submissions page. 11. After grading the first 5 submissions, I'd click through to the next page. 12. After grading the 6th submission, I would be returned to the first submission page and have to click forward again. 13. When you get to the 30th submission, you're maybe doing fifty clicks for each homework assignment. 14. I had 4 classes all doing the same assignment. 15. This could not be amalgamated into a single marking spree. I spent weeks trying to grade my students and then just gave up and had them email me their assignments from that point on. These platforms are all full of features; commissioned, designed, tested and developed by people who have never set foot in a classroom.
企业软件臃肿是因为企业流程复杂且独特，成功软件靠可配置性适配它们；开发这种软件本身也很难。
我认为这说错了。企业软件糟糕的真正原因是企业流程复杂且独特，他们宁愿买能适配流程的软件，也不愿让数万员工重新培训、改变盈利业务的工作流。史上最成功的软件——Word、Excel、SAP、Photoshop、Salesforce、JIRA——都与 Unix 哲学相反：复杂、可配置、上千功能；这也正是它们能卖进律所、炼油厂、动画工作室等不同行业的原因。大多数企业软件糟糕，是因为写复杂可配置软件很难，且很少有公司有那几家巨头数十亿美元的开发预算。最终用户不是购买者，改变不了企业本身很复杂这一现实。
freddie_mercury查看英文原文
I think this gets it wrong. The real reason enterprise software sucks is that enterprises have complex and unique workflows and would prefer to buy software that they can fit to their workflow rather than change the workflows of their profitable business with tens of thousands of staff who will need retraining. If you look at all of the most successful software of all time they are the complete antithesis of the Unix philosophy that so many designers and developers prefer. Word, Excel, SAP, Photoshop, Salesforce, JIRA. People hate them because they are complex, configurable, and have 1000 features. But that's the same reason they can sell into law firms and oil refineries and animation studios and all those other very diverse businesses. And most enterprise software sucks because 1) writing complex, highly configurable software is hard and 2) very few companies have the billions of development dollars the above handful of companies have to throw at the problem to try to make it tractable. That the end user isn't the purchaser isn't going to change that fundamental reality that businesses are complicated.
企业软件开发者也承认产品若可选自己都不会用，内部工具用户没得选，组织惯性和不重视 UX 让改进极难。
我为财富 100 强公司写企业软件。如果站在用户角度且有替代品，我很可能会卸载我们做的东西转投别处；但他们不能，这是内部应用，用户被迫使用。我努力争取做对的事，可每次听到“我们不是谷歌/亚马逊”“只有 xx 人会用它”“我们只是为了摆脱旧技术栈，需要 1:1 重写”都能得一美元的话，我早发财了。大船掉头慢，改变很难；UX 不受重视；敏捷其实是瀑布，发现 bug 时它总是关键阻塞问题。企业完全是另一种野兽。
dividido查看英文原文
I write enterprise software for fortune 100 companies. If I put myself in the user’s shoes and had an alternative, I’d most likely uninstall what we built and jump ship. But they can’t. It’s an internal app and the user is forced to use it. I try and fight for what’s right but if I had a dollar everytime I heard “ we aren’t google/amazon” , “only xx people will use it”, “we are just doing this to get off the old tech stack and need a 1:1 rewrite”. Big ships turn slowly and change is difficult. UX isn’t valued. Agile is really waterfall and when a big is found it’s always a critical showstopper. Enterprise is a different beast altogether.
一句话概括企业软件的结构性问题：购买者与使用者分离，导致产品不优化真实使用体验。
我不确定这个说法源自哪里，但我听过对“企业软件”最简洁的定义是：付钱买它的人不是使用它的人。
mjlee查看英文原文
I'm not sure where this originates from, but the most succinct definition I've heard for "Enterprise Software" is that the person who pays for it isn't the person who uses it.
历次讨论
同类还值得读
贝塞尔曲线入门
A Primer on Bézier Curves
Pomax 编写的贝塞尔曲线在线教程，从基础概念一路讲到曲线求交、投影、曲率等进阶内容，并配有可交互的示例和配套的 bezier.js 库。
设计与产品上首页 7 次 · 2014–2022pomax.github.io编辑精选WebGL 水面模拟
WebGL Water
Evan Wallace 制作的 WebGL Water 演示：在浏览器里实时渲染一片水面，展示折射、反射和焦散等 GPU 图形效果。
设计与产品上首页 6 次 · 2011–2025madebyevan.com设计建议：永远不要使用黑色
Design Tip: Never Use Black
设计随笔提出“永远不要用纯黑”的建议，主张在界面和绘画中改用深灰或带色相的暗色，并借阴影与色彩关系来论证。
设计与产品上首页 5 次 · 2012–2021ianstormtaylor.com用于思考不可想象之物的媒介
Media for Thinking the Unthinkable
Bret Victor 的这个页面围绕《Media for Thinking the Unthinkable》展开，探讨我们用来思考和表达复杂问题的媒介，以及以文字/符号为主的传…
设计与产品上首页 5 次 · 2013–2020worrydream.com编辑精选页面重量很重要
Page Weight Matters
博文讲 YouTube 工程师 Chris Zacharias 的一次页面瘦身实验：团队做了一个更轻量的页面版本，起初从整体平均加载时间看反而更慢；按地理区域分层后才发现，轻量版…
设计与产品上首页 4 次 · 2012–2022blog.chriszacharias.com