3 ms·
At my last company us developers complained that we were getting interrupted too much, so the boss asked us to keep a list of interruptions. By lunch on the fir
by grecy 14y ago
At my last company us developers complained that we were getting interrupted too much, so the boss asked us to keep a list of interruptions. By lunch on the first day we all had 3+ pages, so he believed us and we implemented the following:
Each week, one pair of programmers would be designated the "consulting developers", and a big sign would be put above their desk. They were the only developers that could be interrupted for the week, allowing the rest of us to get a lot of work done. If the consulting developers needed to ask something of other developers, we tried to save it up for lunch, as we mostly all ate together anyway.
This made an enormous difference to our productivity, which everyone in the company took notice of when the number of "development days" we got done each week increased dramatically.
At the start we thought of "sacrifice one for the good of all" and we didn't look forward to our turn. As time went on it actually turned out differently. We usually enjoyed the "consulting" time as it meant a break from the routine of working on endless tickets, and it also kept us in touch with what the rest of the company was doing with regards to deploys, environments, configs, etc. etc.
AFAIK they still do it today
- bifrost 14y agoThis is actually pretty standard ops methodology. You designate an "intake" person, and then the rest of the group works productively while only one person gets harrangued with interrupts. Its very effective.
- MatthewPhillips 14y agoDon't you find it distracting listening to people ask the consultants questions all day? Often times about projects you work on? I don't think there is any cure for interruptions other than no at-desk meeting rules or private offices.
- grecy 14y ago> Don't you find it distracting listening to people ask the consultants questions all day? People are very respectful of the shared space and keep the noise down. Also, it's nice when you are not consulting to actively ignore whatever is being said to the consultants, so you can be more in the zone. > I don't think there is any cure for interruptions other than no at-desk meeting rules or private offices. That's what we do at my current company (try to limit drive-bys) and it's horrible - I just get people booking time in my calendar every 20 mins, so that it's not a drive-by when they want to interrupt me.
- deleted 14y ago[deleted]
- mtrimpe 14y ago> I don't think there is any cure for interruptions other than no at-desk meeting rules or private offices. A simple feedback mechanism for this would get us quite far already. Just something that will glow red for 'dont disturb,' orange for 'only if you have to' and green for 'go right ahead.' If someone wants to make (a Kickstarter for) a simple ball that does this I'll gladly transfer my domain names interruptiball.com and interruptaball.com to you by the way. ;)
- X-Istence 14y agoI've thought about doing something like this, and tying it into a web based services so you can see what state everyone is in. Might work on this some in the near future, but I am not sure if I want to commit to a Kickstarter ;-)
- mtrimpe 14y agoIf/when you do... just ping me and I'll hand over the domain names ;)
- neltnerb 14y agoNice idea. I'm sort of straddling the position between management and engineer at this point in my career, so I understand the utility of meetings but also definitely appreciate how much more I can get done when I'm allowed to just be in the zone and define my own objectives. Do you think it would be feasible to have a competent manager assign somewhat high level tasks to engineer-managers, have them assign subtasks to engineers, and then have the engineer-managers deal with integration, systems design, and interfacing with real management? It seems like if that situation works in practice (I'm too new to know, and didn't go to management school, so this is largely experimental or anecdotal for me), tasks can simply be assigned by someone close enough to understand the complexity and skill of the engineers actually doing the coding via something like exchange based tasks, a to-do list of open issues that need to be dealt with, etc. Or do you think that the core engineer staff is not mature enough to handle that level of independence at most big companies? I would assume that at startups the structure is more flat in such a way as to make my suggestion less meaningful. I ask this because I'd really like to be a better manager, and I find that for myself, having a list of goals (i.e. "define API and write spec", "draw out abstraction structure", "CAD up mechanical enclosure", etc) is more than sufficient for me so long as I'm in regular enough communication with the people around me to know what those shortened descriptions mean for sure.
- sbilstein 14y agoWe do this at my startup. We call that developer the Sheriff and he/she sends a photo to the company chat with a sheriff hat on Mondays. They aren't expected to get anything done that week (although they typically try to do their work) and just deal with any live site issues or questions from the rest of our rather small company. Sometimes they end up implementing lots of quick fixes that other employees ask for.
- troels 14y agoWe did this at one previous company I worked at. At my current company, I've introduced the same thing. The person also doubles as the "maintenance person", who will pick up minor production-level failures.
- tseabrooks 14y agoWe're experimenting with something like this now. I'm currently acting as the "consulting" dev here. Our first experiment is on a quarterly basis. We'll reconsider after the quarter. We're actually struggling with finding the right amount of time for this. A week didn't feel long enough for us because that person would also handle tier "3" support for the week. Any thoughts on finding the right amount of time for something like this?
- lrem 14y agoMy wife's working in a major European corporation and they do one/two weeks shifts. They also have it divided into classes of problems they're fighting (the "need it solved now" vs "this weird thing happened and we think it's your team's fault" vs "OMG it's 3 am and the world is on fire!"). I can't recall now which class corresponds to which duration. Edit: there's also one person who is the permanent point of contact for a single release. New releases are once per three months. This person obviously has one hot week, but the amount of contacts decays exponentially.