An automated system that eliminates a class of feedback when reviewing a work product. Similar to how code formatters like prettier work to remove code style comments during code review, an organizational linter can take an opinionated, repetitive form of feedback and automate it. This frees up time because automating cooperation decreases the cost of coordination.
Links to this note
If every time a group of people need to work together they need to agree on how they work together, who is involved, and expectations, the cost of cooperation would grow with the number of people (possibly exponentially). By automating established norms, practices, and processes, the cost of coordination goes down because you are no longer solving the same problems repeatedly.
There are a few ways to get linting of prose (grammar and style, not just spellcheck) in Emacs. Unfortunately, there is no good language server implementation for the popular open-source command line tools. The best option right now is probably
valegives better suggestions.
Grammarly improves the overall level of communication within an organization, but if you think of it as an organizational linter it does much more. It eliminates a class of common feedback that would otherwise need to repeated for each work product for each person (with some decay curve as new employees internalize these rules). Even better would be if it could lint the structure of documents (i.e. a minto linter) and not just grammar and phrasing.
A theoretical tool that checks a piece of business writing against a set of rules from The Minto Pyramid Principle. Like a code linter, this would serve as a ratchet for improving the output of others—in this case, those sharing business writing like strategy memos, 1 pagers, and project briefs.