In a remote-first software house, meetings and asynchronous chats quickly become the backbone of communication. As every new tool suddenly becomes AI-powered, instead of following the usual AI everywhere trend, Paweł Feliński and his team took a brain-first approach: first understanding how knowledge actually moved through the organisation, and only then deciding where AI could genuinely help.

That led to an unexpected discovery: many recurring agile “ceremonies” existed mainly to move information from one person to another.

Once they started treating organisational knowledge as an operational problem, not just a documentation problem, several things changed quickly. Post-meeting note-taking disappeared. Developers stopped joining estimation sessions by default. Specifications became asynchronous, reviewable, and easier to evolve. Some meetings became shorter. Others vanished entirely. What disappeared were not feedback loops or collaboration, but the manual overhead around them.

To support this, the team built a lightweight, LLM-agnostic internal knowledge layer designed around their actual delivery workflows rather than generic AI productivity demos.

Not every experiment worked. In several cases, removing a ceremony also removed hidden coordination value they had not noticed before.

This talk is a practical before/after case study of how a growing software company used a brain-first AI approach to reduce coordination overhead – and discovered that many agile “ceremonies” existed mainly to compensate for broken knowledge flow.