01/04: Through Jefe good things come..
I just a quizzical email a few minutes ago, and I frankly think it was directed at Falloutboy (but it was emailed to the whole team).
The crux of the email was procedures for emailing or contacting people out side of the team.
1. Reply all to everyone
Wait, isn't that a bad thing?
2. Always CC Jefe and DK for anything admin - to keep them in the loop.
Mkay.. the directly doesn't work I guess.
3. If our system conflicts with another team or someone else from another team contacts us
a. CC Jefe and Dk - always!
b. Something about work schedule
c. Something about stuff being an issue if not escalated.
Basically the communication should always funnel through Jefe and DK to other teams. The other teams are the enemy.
There was a nice line about how Jefe would want to hear about an issue from one of us versus a third party.
I am sitting here wondering what might have caused this email then I remember Falloutboy saying he has a list of our tables another team uses and if we are making changes to them (or something might cause an issue) he shoots an email off to this other team's person. My guess is someone on the other team made a comment to Jefe about it, she had no idea, got flustered, became a bit embarrassed, and then finished strong with anger.
There's probably also some sort of power play going on in her head. If my team is contacting other teams about problems that will come up... then they will become friends... and I lose my grip over the team.
That and she would rather garner the platitudes from an issue someone on the team found and not that person directly.
This hearkens back to a time my emails were required to be approved by Jefe. Thankfully entropy took care of that rule.
The crux of the email was procedures for emailing or contacting people out side of the team.
1. Reply all to everyone
Wait, isn't that a bad thing?
2. Always CC Jefe and DK for anything admin - to keep them in the loop.
Mkay.. the directly doesn't work I guess.
3. If our system conflicts with another team or someone else from another team contacts us
a. CC Jefe and Dk - always!
b. Something about work schedule
c. Something about stuff being an issue if not escalated.
Basically the communication should always funnel through Jefe and DK to other teams. The other teams are the enemy.
There was a nice line about how Jefe would want to hear about an issue from one of us versus a third party.
I am sitting here wondering what might have caused this email then I remember Falloutboy saying he has a list of our tables another team uses and if we are making changes to them (or something might cause an issue) he shoots an email off to this other team's person. My guess is someone on the other team made a comment to Jefe about it, she had no idea, got flustered, became a bit embarrassed, and then finished strong with anger.
There's probably also some sort of power play going on in her head. If my team is contacting other teams about problems that will come up... then they will become friends... and I lose my grip over the team.
That and she would rather garner the platitudes from an issue someone on the team found and not that person directly.
This hearkens back to a time my emails were required to be approved by Jefe. Thankfully entropy took care of that rule.
Wangnet.org RSS Feed