You should protect your team’s “deep work” at all costs. Traditional work environments optimize for rapid-fire communication. Meetings, Slack, text messages, and stand-ups are examples. Levels thinks these defaults are disastrous and reduce the amount of “deep work” its team can do. It does everything possible to protect this time.
And that’s for comparatively structured questions, like “What is the optimal way to convert input X into output Y?” It’s even harder for uncertain jobs, like “What should input Y be?” Was the team that designed the “like” button more productive than the team that produced Slack’s “emoji react” feature? We can argue indefinitely. Maybe the “like” ti... See more