Having a rigid process is often an overkill for small companies.
Processes don't have to be "rigid". For example, "everyone online between 2-4pm GMT" is not all that rigid, and imposes very little overhead, but greatly helps with team communications.
Comments
Having a rigid process is often an overkill for small companies.
Processes don't have to be "rigid". For example, "everyone online between 2-4pm GMT" is not all that rigid, and imposes very little overhead, but greatly helps with team communications.
Agreed, but I wouldn't call that "process". A set of 1 or 2 rules is fine, of course.