Agile boards instead of meetings: how Maitech set up Directum Projects

The key decision was not one shared board but a separate one for each stream of work with its own columns and rules.

• The CEO's board: development ideas that used to get lost in correspondence.
• Marketing: the content plan as cards by date and status.
• IT: a task backlog with priorities.
• Contract approval: stages from draft to signature.
• Client work: enquiries and their status.

Meetings mostly exist to learn status: who is doing what, what is stuck, who needs help. When all of that is visible on a board to every participant, status meetings lose their purpose. That is how Maitech explains the reduction: manual information gathering and redundant communication disappeared, and process bottlenecks became visible without polling people.

The 20 % faster data lookup follows from documents, tasks and discussions living in one system next to the card instead of in email, messengers and folders at the same time.

The company plans to visualise the deal process, track employee requests and integrate Git so development tasks and commits are linked. It is a logical path: the board becomes the single interface to all processes while integrations pull data from the systems where it originates.

The effect comes from three rules, not from a specific platform. One board per process rather than a 'company board'. Statuses that reflect real stages rather than 'in progress / done'. And a mandatory link to data sources: CRM, email, repository. The same rules work in Bitrix24, YouGile, Kaiten or Jira. If processes exist, boards merely reveal them.

The Maitech case is valuable for its numbers: 20 % faster lookup and 10 fewer meeting hours a week through transparency. It repeats on any platform when boards follow processes rather than fashion.