Expert knowledge for digital decisions

How does collaboration work in daily project life?

Short answer

Through a fixed contact person, brief alignments instead of long meetings, and visible interim results. A short meeting per week is common, where the current status is shown and the next steps are defined – plus a channel for questions in between.

The Rhythm

A short meeting once a week. Twenty to thirty minutes: What is finished, what comes next, what is blocking. No status report, but a look at the ongoing status.

A channel for in-between. Email or a messaging service for questions that cannot wait until the meeting.

A shared list. All open points in one place, visible to both sides. This eliminates the question, "Didn’t we discuss this?".

What We Need from You

A contact person with decision-making authority
Feedback within a few days
Access to the people who will work with it later

The second point is the most important. Waiting times for decisions are the largest single cost factor in software projects.

What You Can Expect from Us

A runnable status to review after each section
Feedback if something takes longer – before the meeting passes
A note if we consider a requirement to be uneconomical

Languages

German, English, and Arabic.

In Case of Discrepancies

Address them as soon as they arise. A project where both sides accumulate dissatisfaction will not improve – it will only become more expensive if it is brought up later.

Key facts

Rhythm: A short meeting once a week
Most Important Contribution from the Client: Quick decisions
Languages: German, English, Arabic