Just do your job and shut up.

No problem.

The software company I worked for got acquired.

Some people were let go, some were added, and some teams and functions were restructured.

Prior to acquisition, we had a multiple hats situation where you basically did whatever was in your capacity.

Teams played to each other's strengths and one person would

generally take a client from the first demo right through the configuration, implementing,

and training phases of the software. Some of us had strengths in technical areas, others had more

than a decade in the client's subject matter. Clients would give us some feedback or wish lists. We'd talk amongst the team

about how the functionality could be added or changed, make a functional mock-up, and then

bring that to the development team for polish and integration into the production code.

It worked wonderfully, like 100% positive feedback and nothing broken when it went to production.

We had a good rapport with the dev guys and some of us were able to write queries or code

portions that would save them from having to ask a billion subject matter questions.

When we weren't dedicated to a task, would handle support calls.

Clients would call up, receptionists learned who to pass things to based on clients, and

the nature of issues,

and resolution was typically instantaneous unless the problem required research. Clients loved

that and had the understanding that if we couldn't resolve their problems right away, it was

because we needed to look into it. After the acquisition, the parent company reorganized

things into a much more rigid,

you have one job, kind of scenario. The trouble was, with the people they let go, I was the

...