Project check-ins


“Would it be beneficial to set up the scope of an agreement? In other words, to get clarity among all parties to an agreement what the expectations are? For Example: the team will have check-ins to share project progress even without aspects being fully complete.”


It is true that Americans have a much higher frequency of status-checks than do Germans. For Americans, an agreement actually kicks off the collaboration. And collaboration in the U.S. means a lot of back and forth, a lot of engagement, high levels of communication. That’s how Americans work in teams.

And it is true that Germans have a much lower frequency of status-checks. For Germans, an agreement actually kicks off each party to the agreement working on their part of that agreement. And collaboration in Germany does not mean a lot of back and forth, does not mean a lot of engagement, does not mean high levels of communication. 

That is not how Germans work. They first get clarity on who does what. Then they as individuals get to working doing the what. They come together only when necessary. Ideally when each is finished with their part, with their deliberable. 

So, if you feel that check-ins, also called status meetings, are important, propose to your German colleagues: when they should take place, for how long, who should participate, and most importantly why the status meeting is necessary, how it adds value.

But be prepared for your Germans colleagues to ask why all of this is necessary. You need then to explain to them how Americans work in teams, that much of it is iterative, tactical, flexible, less structured.

They will tell you how they as Germans work in teams. You should find a happy middle ground.

Project check-ins