shrinkage Slack is the opposite of organizational memory(6)

There’s one way in which slack edges out trello & jira for project managemnet. T&J don’t implement backpressure; slack does, because there are limits to attention.

But this is a goldilocks problem – neither the jira ‘kitchen sink’ model nor the slack ‘off the dome’ model is ideal. Also, lots of people want to use slack trello AND jira simultaneously without any sense of shame (2 is egregious but 3 is insane). Also, slack isn’t the right solution for project management, at minimum because it doesn’t have good aggregation views; not that jira really does either. We need to build scheduling tools that have well-considered limits, not the arbitrary limit of what people can process under high attention pressure.

Are also things I hate.

They promote this icebox theory of design. What did a PM think of six months ago that hasn’t been started? Let’s do that. If your best people aren’t inventing and assigning projects, why should anyone bother showing up to work?

JIRA has a screen real estate problem. Have you seen the articles about SERP shrinkage, where a G results page in 2004 was mostly results and now it’s mostly ads? JIRA started out this way. 90% of the text on the screen isn’t your project’s information, it’s JIRA chrome.

Another JIRA flaw: highly formalized process is usually a hindrance, especially considering who in your organization invents, applies and benefits from process. Hint: middle managers.

The commoditization of communication isn’t working. So let’s get off the wagon and start making considered plans again. A blank sheet of paper is all anyone has ever needed to do this well.

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