SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Stress – It’s Not Fair


Stress – It’s Not Fair

Author
Message
SQLRNNR
SQLRNNR
SSC-Forever
SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)SSC-Forever (40K reputation)

Group: General Forum Members
Points: 40273 Visits: 18565
Nice hot topic button Andy. If you are already under a fair amount of stress, adding this outside stress compounds the problem. Being able to communicate the cause of this secondary stress (and report reasons for delay) while keeping emotions at bay is difficult. Nonetheless, it is an important thing to learn.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

TravisDBA
TravisDBA
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2390 Visits: 3069
WolforthJ (11/28/2011)
The chart went up in the break room, so everyone saw it when a project was behind and knew which team caused it. After a while we didn't need the chart.



Personally, I'm not a big fan of this kind of public display to get a point across, because it destroys team building and tends to promote a pay-back atmosphere (us vs. them) in the department. I think there are other more tactful ways to deal with this, even if it did turn out to be effective. You can motivate people in other positive ways than mounting signs in the break room for EVERYONE to see (including the janitors and vending machine operators) IMHO.:-D

"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
ken.trock
ken.trock
SSC Eights!
SSC Eights! (813 reputation)SSC Eights! (813 reputation)SSC Eights! (813 reputation)SSC Eights! (813 reputation)SSC Eights! (813 reputation)SSC Eights! (813 reputation)SSC Eights! (813 reputation)SSC Eights! (813 reputation)

Group: General Forum Members
Points: 813 Visits: 1730
The single most common cause of both work overload and project failure is doing work twice. The most common cause of that is picking up some piece of work (opening an e-mail, looking at a piece of code, whatever), and not handling it right then and there, but instead deciding to handle it later. Right there, you just made yourself do at least twice the work of analyzing whatever it is you just had to analyze a first time. The second most common cause of double-work is not doing something right the first time, usually in a false sense of "just get it done".


That is a great point. Try to finish something now that you've already started. Don't go 3/4 down a task and say "I'll finish it up next time", even if it's Friday afternoon. Or maybe especially because it's Friday afternoon :-D

Ken
rfr.ferrari
rfr.ferrari
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1661 Visits: 13630
ken.trock (11/28/2011)
.....That is a great point. Try to finish something now that you've already started. Don't go 3/4 down a task and say "I'll finish it up next time", even if it's Friday afternoon. Or maybe especially because it's Friday afternoon :-D

Ken



it's true and very common in most people!!!!


rfr.ferrari
DBA - SQL Server 2008
MCITP | MCTS

remember is live or suffer twice!
the period you fastest growing is the most difficult period of your life!

GSquared
GSquared
SSC-Dedicated
SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)SSC-Dedicated (30K reputation)

Group: General Forum Members
Points: 30167 Visits: 9730
ken.trock (11/28/2011)
The single most common cause of both work overload and project failure is doing work twice. The most common cause of that is picking up some piece of work (opening an e-mail, looking at a piece of code, whatever), and not handling it right then and there, but instead deciding to handle it later. Right there, you just made yourself do at least twice the work of analyzing whatever it is you just had to analyze a first time. The second most common cause of double-work is not doing something right the first time, usually in a false sense of "just get it done".


That is a great point. Try to finish something now that you've already started. Don't go 3/4 down a task and say "I'll finish it up next time", even if it's Friday afternoon. Or maybe especially because it's Friday afternoon :-D

Ken



Actually, starting something Friday and finishing it Monday is a good way to end up with your mind locking on the incomplete action all weekend, thus ruining any chances to pay real attention to the weekend at all. Essentially, you get to work the weekend for free, off the clock, even when you're asleep, because your mind will still have pieces of that work stuck in it. So, finish what you start, if you can, and finish as close to when you start as you can.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Eric M Russell
Eric M Russell
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16455 Visits: 10930
Members of different teams often follow a rigid "start [this] only after [that] has been completed" development path that isn't necessary.
For example, when developing the data model and stored procedures for a new database, I'll shortly provide the application developers with prototype stored procedure calls that have input/output parameters and mockup resultsets that closely match what the final version will have. Of course, this works much better when the app developers are only making procedure calls and don't have direct access to tables. The stored procedures provide the necessary abstraction layer required for unit based development.
Likewise, when I need to interface with tables on a remote database owned by another team, I'll mockup my own local tables or procedure calls based on the design specifications they are currently working from. Once their end is ready, I only need to make a few minor retrofits to the datasource and programming on my end.
I've found this to be more effective than sulking, nagging, and raising a stink.


"The universe is complicated and for the most part beyond your control, but your life is only as complicated as you choose it to be."
WolforthJ
WolforthJ
SSC-Enthusiastic
SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)SSC-Enthusiastic (162 reputation)

Group: General Forum Members
Points: 162 Visits: 268
TravisDBA (11/28/2011)
WolforthJ (11/28/2011)
The chart went up in the break room, so everyone saw it when a project was behind and knew which team caused it. After a while we didn't need the chart.



Personally, I'm not a big fan of this kind of public display to get a point across, because it destroys team building and tends to promote a pay-back atmosphere (us vs. them) in the department. I think there are other more tactful ways to deal with this, even if it did turn out to be effective. You can motivate people in other positive ways than mounting signs in the break room for EVERYONE to see (including the janitors and vending machine operators) IMHO.:-D


I agree. This was a pretty dysfunctional company. But in this case, it inspired the department that had to order stock to start using an actual project management tool. Exactly what we wanted them to do, and had been suggested, but when it became their idea they were more enthusiastic about it and other departments adopted it. Eventually most departments were included, except IT, which was listed, but never had any time assigned to it. So, if you looked at their GANTT chart apparently we were doing our job in zero time.

Anyway, the guy who put up the chart was eventually fired because of his anger issues and the director was promoted just because. She was diagnosed with Alzheimers not too long after that. Stranger than fiction.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)

Group: Administrators
Points: 81721 Visits: 19210
TravisDBA (11/28/2011)
WolforthJ (11/28/2011)
The chart went up in the break room, so everyone saw it when a project was behind and knew which team caused it. After a while we didn't need the chart.



Personally, I'm not a big fan of this kind of public display to get a point across, because it destroys team building and tends to promote a pay-back atmosphere (us vs. them) in the department. I think there are other more tactful ways to deal with this, even if it did turn out to be effective. You can motivate people in other positive ways than mounting signs in the break room for EVERYONE to see (including the janitors and vending machine operators) IMHO.:-D


Tend to agree with this comment. I think this is the type of thing that should be handled by a manager in a less public setting.

It breaks teams up. Many people may not realize what the slowdown is, or understand if there is a good reason. Like an unrealistic schedule.

If you think a team is slow, or not doing their best, then deal with them directly.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Steve Jones
Steve Jones
SSC Guru
SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)SSC Guru (81K reputation)

Group: Administrators
Points: 81721 Visits: 19210
Stress can be very hard to deal with, especially when it comes from friction between teams. I've tried to be more efficient at work, but also do a professional job. Set my own limits on what I can accomplish, and then move forward to do them.

If I fall behind, I can only do so much to catch up. I can't live to work, at least not for more than a week or two.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
mtucker-732014
mtucker-732014
SSC-Enthusiastic
SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)

Group: General Forum Members
Points: 151 Visits: 369
A month or so ago there was an entire issue of Scientific American MIND devoted to Stress, causes, effects and how to deal with it. The research suggests that by far the best strategy is to avoid getting into stressful situations, by good forward thinking, planning etc. Strategies for dealing with stress, such as modifying the way you think about the situation are only moderately useful (according to the research) in comparison.

I would say that it is reasonable to express a certain amount of dissatisfaction if other people have let you down. The approach suggested by Andy of dealing with other people's failures as if they are just another problem to solve might make you miss the most effective problem solving technique of all - a good kick up the ****!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search