Primotly, ex-DocPlanner
www
Maciek Kemnitz
I believe in awareness, ownership, and transparency. For me, business starts with asking why – understanding the purpose behind every step – and ends with delivering on commitments.
I thrive on building from scratch, taking full responsibility for outcomes, and driving teams forward with clarity and purpose. Success matters, but so do the lessons that come with failure – they shape the resilience and vision needed to scale.
From my early days at DocPlanner, through scaling Slowhop as a co-founder, to leading transformation and operations at Primotly, one constant has guided me: I take full ownership of results. Whether it was introducing new technologies, scaling products into new markets, or leading teams into agile ways of working, I’ve always combined hands-on problem-solving with long-term business vision.
Today, I’m devoted to creating a culture of clarity, accountability, and collaboration – one where individuals are empowered as true drivers of innovation. When people are connected with purpose and structure, businesses don’t just grow – they evolve.
What We Stopped Doing: A Brain-First Approach to AI in Delivery
In a remote-first software house, meetings and asynchronous chats quickly become the backbone of communication. As every new tool suddenly became "AI-powered", instead of following the usual "AI everywhere" trend, we took a brain-first approach: first understanding how knowledge actually moved through our 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 we started treating organisational knowledge as an operational (not just 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, we built a lightweight, LLM-agnostic internal knowledge layer designed around our actual delivery workflows rather than generic AI productivity demos.
Not every experiment worked. In several cases, removing a ceremony also removed hidden coordination value we 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.
Maciek will be speaking with Paweł Feliński.