# Communication Hygiene for AI-Era Teamwork

**Author:** Alexey Krivitsky
**Date:** 2026-09-26
**Reading time:** 2 min
**Category:** AI X OD
**Tags:** ai, agentic-engineering, org-design, framework-fatigue, remote-work, operating-model
**Canonical:** https://krivitsky.com/post/framework-fatigue-lightweight-rituals

---

**TL;DR:** People just wanna work. Alone. Managing agents. Not being distracted.

If you're trying to come up with a new framework or an operating model for the new times, forget it. Unless it is **the most lightweight thing you can think of**.

## New Status Quo?

We have entered a very practical and pragmatic era. Also, the **framework fatigue** is still in the room. The tyranny of [dark Scrum](/post/scrum-was-a-harness) is shadowing the memories.

People just wanna work.

Alone. Managing agents. Not being distracted. Avoiding any sort of unnecessary communication.

People want to pretend they are [the company of their own](/post/super-ic-trap-guild-hypothesis) and there's nobody else around. That they can finally ideate and produce.

People wanna stay in this new world because the old world was overwhelmingly impeding.

"A three-day all-hands meeting to identify and visualize the inter-team dependencies."

Did we really do it ourselves? Nobody wants to look back. It looks shameful and sick.

In this new era, [remote and individualistic work](/post/remote-work-synthesizing-the-studies) gets stronger day by day.

The pendulum swings completely in the opposite direction from the previous "hugging era of flowery retrospectives".

People just wanna work. With their heads down, headphones on, dark mode.

Terminals over meetings. Agents over people.

We all feel this is all not sustainable but this is the time we are in. This is an overcompensation that people deserved.

## The Resolution?

We, lean practitioners, systems thinkers, engineering craftsmen and methodologists, we need to respect whatever people want.

At this time, we just need to offer **basic communicational hygiene**. Something super simple and lightweight that doesn't resemble anything of the old times.

Options:

- Monday morning "business context loading" (product engineers talk about business metrics, user feedback, top product issues, basic reminders of the customer needs, snacks…)

- Full week of work! (product engineers need to be motivated to work together, pair, mob, gang prompt…)

- Friday afternoon "lessons learned" (product engineers talk about changes in agentic setups, good/bad code examples, failed experiments, new ideas, cold beers…)

Embrace change!