shrinkage Slack is the opposite of organizational memory(4)

ctrl-f, the one constant of web interaction, is broken in channels if you’re searching more than one page up. We can blame this on the DOM but I assume this is because slack’s heavy CSS uses too much memory to keep a long scroll history.

I get that this is just a UX issue and is fixable but (1) I don’t know if it isfixable when your foundation is the sandy marsh that is the DOM and (2) if slack were a tool for augmenting thought rather than preventing it, it would have a working search feature.

Goodhart’s lawis the one where turning a metric into a target makes it a bad metric. Slack subverts valuable work by making productivity = availability on slack.

Productivity as a metric is problematic because it’s so hard to measure or even to define in a general way. In economics, total factor productivity is basically wages minus capital, and is flummoxed by the fact that better tools don’t put more money in people’s pockets (employees are generally paid for their time).

At work, productivity conflates delivery and business value. We know how to measure the first but we mostly care about the second. Optimizing delivery rate has bad effects on products and teams:

Middle managers will make deliverables smaller and less valuable so they can declare a win to their bosses or so the C-suite can brag to shareholders

Which in turn moves design work from domain experts to PMs, resulting in nuts designs

And it increases utilization, which leads to burnout, reduces safety margins, stifles innovation (that’s what those spare cycles were getting used for)

本文来自电脑杂谈，转载请注明本文网址：
https://www.pc-fly.com/a/jisuanjixue/article-73401-4.html