Timeline for How can I manage team distractions like chit-chat?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2013 at 13:28 | comment | added | Josh Bruce | +1 For a very thorough answer, which is very much on target. As to the concept of "chit-chat" - as I currently work in a development role - it bothers me when team members talk about things wholly unrelated to development as a whole (kids, family, the weather, etc.), but I know that some people just work better that way. The "chit-chat" I usually engage in something related to development or process - while not directly related to a project I'm working on - it is related to how work gets done...but, that's how I operate. | |
| Jan 14, 2013 at 16:15 | comment | added | MrFox | Unless you're a developer (or some senior iteration of a developer like an architect) then you should never be telling them how to do their jobs, because frankly you don't know how to do their jobs. Unless you're looking at the frequency of their commits and the quality of the code that they're putting in then you're in no position to be their coach. They might spend half of their day with their hands behind their backs leaning back in the chair and talking about the weekend, and be way more productive than someone who stares at the screen for 8 hours straight and keeps their mouth shut. | |
| Dec 28, 2012 at 20:54 | comment | added | Lunivore | +1, and two notes: Every time a dev does something they've never done before, estimating it will be impossible anyway. By holding devs to deadlines, you kill creativity and innovation. Also, the "chit-chat" helps engender trust, which can help devs reach out to each other for help when they need it, which saves a lot of time in the long run. | |
| Dec 27, 2012 at 18:10 | comment | added | ChrisFM | Thank you for taking the time to write a thoughtful and well constructed answer that challenges the why. The root of the problem is our internal management, and as I stated is a symptom. I'm not attempting to usher in a renaissance of fascism starting with my team, just keep the chit chat from becoming a runaway train. Every great athlete has had a coach that drives them and tells them to "do it again." All of your challenging questions are helping me to find a clearer path to becoming better playing team. p.s. Next time I will include footnotes to support my statements. Thanks! | |
| Dec 27, 2012 at 8:18 | comment | added | Earlz | I'm a developer, and I think this advice is spot-on. It's primarily how the company I work at manages things. Also, that "idle" chit-chat isn't necessarily a waste of time. It might be for hours on end, but some chit-chat I'd consider beneficial. The usual chit-chat times are when two people are stuck on a problem. For me, it helps to forget about the problem for a few minutes and do something else, and then come back to it with a fresh mindset. If they aren't chit-chatting, they're reading the onion or whatever. Don't try to eliminate this because you'll always fail. | |
| Dec 26, 2012 at 22:31 | comment | added | Tiago Cardoso | figuring out how to engage them rather than on ways to make them look engaged +1! | |
| Dec 26, 2012 at 22:25 | history | answered | Todd A. Jacobs♦ | CC BY-SA 3.0 |