Networking sold outSales open until 15.09 · 23:59--d --h --m --s
Design Strategy

What the...Kanban!? Team management. I think.

Long Lecture
🇵🇱 Polish

About

A presentation on team management in the world of politics. Collaboration with politicians is a different perspective. "Collaboration" is often a semantic misuse. How do you manage the unmanageable? How to arrange the work of a team when the team doesn't know it is one? Real-life examples from election campaigns and the processes behind them. A sprint with competitors running in different directions, from a leader's perspective. If you learn the behind-the-scenes of election campaign management, you will consider your standard work assignments not a problem. Is this type of project for you? Do you want to design a political campaign and derive value from it? The next election is a year away - get ready.

‍

Talk by

Photo of Marcin Andrzejewski, Owner of marcinandrzejewski.pl
Marcin Andrzejewski
Owner of marcinandrzejewski.pl at Independent

Watch the full talk

Watch this WaysConf session, then continue with related talks or explore the current programme.

Explore the 2026 agendaMore WaysConf recordings
From the recording

Talk in brief

A surprising Kanban case study drawn from organizing an election campaign in a low-trust, high-constraint environment. Candidate lists, institutional obligations, volunteers, content limits, approvals, and financial responsibility created a complex flow of work that spreadsheets and informal messages could not make visible. A Trello-based board and disciplined information templates clarified status and handoffs. The broader lesson is that Kanban is less about software than shared visibility: define the work, constrain its format, expose responsibility, and let feedback improve the system.

Key takeaways

  1. 01

    Use visibility where trust is already fragile

    A shared board reduces ambiguity about commitments, status, and responsibility in an environment where people expect political work to fail.

    Watch from 2:04
  2. 02

    Represent obligations as explicit workflow

    Candidate constraints and institutional relationships become manageable when the team models them instead of relying on memory.

    Watch from 7:10
  3. 03

    Invite feedback that reveals the real flow

    A fast, detailed response from a new collaborator exposed how clearly the system communicated work and where it could improve.

    Watch from 12:24
  4. 04

    Constrain information before it enters the board

    Required fields and character limits prevent unstructured submissions from creating downstream editing and coordination work.

    Watch from 18:02
  5. 05

    Make authority match accountability

    People responsible for financial or political consequences need enough competence and decision power to manage the work safely.

    Watch from 23:59
Read edited transcript highlights

These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.

A visible system can counter organizational distrust

When participants expect politics to be opaque or chaotic, a shared view of work has unusual value. A board cannot create trust by itself, but it can make commitments, owners, status, and blocked decisions inspectable. This reduces the space for conflicting private stories and gives the team a concrete place to resolve disagreement.

Watch from 2:04

Political constraints still need product modeling

Candidate placement, institutional relationships, and strategic goals create rules that are difficult to hold in conversation alone. Representing these constraints in the workflow helps the team see dependencies and prevents a local decision from violating the larger plan. The model does not remove negotiation; it makes the subjects of negotiation explicit.

Watch from 7:10

Feedback tests whether the workflow communicates

A new collaborator should be able to understand what exists, what is expected, and where to respond without reconstructing the project through private messages. Fast, precise feedback indicates that the board and its conventions have reduced onboarding cost. Confusing responses, by contrast, are evidence that the system needs clearer states or information.

Watch from 12:24

Structured intake protects downstream attention

Open text fields invite people to submit pages where a concise campaign message is required. Required fields and character limits force early decisions about relevance and format. This is not administrative strictness for its own sake; it prevents editors and coordinators from repeatedly transforming ambiguous material after it has entered the production flow.

Watch from 18:02

Accountability requires corresponding control

Someone carrying financial or legal responsibility cannot safely depend on decisions they are unable to inspect or change. Workflow design should align authority, competence, and accountability, while making escalation paths clear. The principle applies beyond campaigns: ownership labels are meaningful only when the owner has enough information and power to act.

Watch from 23:59
Explore WaysConf 2026

View the agenda

Get tickets