Tim runs a small business and is a long time customer of a software firm that put together his information systems. There had been some staff turnover in the software firm over the years, but the quality of the work and service they offered was always maintained. They had a good working relationship.
However in the last year things had changed; there was a new team that handled his work, and things hadn't been the same since then. Initially it was small glitches that he ignored given the long-time association he had with the firm, but now the problems seemed to be escalating. Deadlines were constantly missed, and he was not kept informed of the delays. Everybody on the team was extremely intelligent and competent but they never seemed to provide a service of the same quality.
A few months back Tim had a meeting with Mark the team leader and discussed the problems with him. He was given an assurance that Mark would look into the matter so the problems would not crop up again.
However, this wasn't the case, the new software module that the team installed had serious problems and didn't meet up with the requirements laid out in the brief. Tim felt he had no choice but to ask for a meeting with the Managing Director of the firm to express his concerns.
The symptoms of team ineffectiveness can be gauged by observing the process followed and behavioural aspects that are evident within the team. For example; the way they talk to and about each other.
It is important for companies to act immediately if they see any of these symptoms of team ineffectiveness and investigate the cause, a few examples of which are below: