Skip to main content
Kristof Kovacs šŸ§‘ā€šŸ’»

Teamwork ground rules

·2 mins
Author
Author
Kristof Kovacs
Software Architect & Devops Consultant

Hello, Iā€™m Kristof, a human being like you, and an easy to work with, friendly guy.

I've been a programmer, a consultant, CIO in startups, head of software development in government, and built two software companies.

Some days Iā€™m coding Golang in the guts of a system and other days I'm wearing a suit to help clients with their devops practices.

When you're in a team that I lead, there are three minor things that I'd like to ask you. I believe these ground rules are the lubricant of an effective team, and it's not only others I want to adhere to them, I do them myself, too.

There's only three things:

  • ASK: If a task is not clear, or more information is needed, please ask as soon as possible. Asking is always ok. Doing the wrong thing (or doing nothing) because you didn't ask is not ok.
  • DEBRIEF: It's not done until you reported it done. This is often just a one-sentence email to me or to the client, sometimes a "100%" mark in the task list, or a ticket closed. It is done, completed or fixed only when whoever needed it done knows about it.
  • WARN: If a deadline you know is important will likely be missed, warn me soon, as the situation is evolving, and then we can usually figure something out. If I have to learn at the moment of the deadline that it was missed, that's not ok. (In multi-boss situations that occur frequently in matrix organisations, or if you're a freelancer, also warn me if your workload is above what you can actually do, instead of not doing certain tasks.)

Thanks.