3 ms·
I like this blog. As a "semi-retired old dude," I have been absolutely reveling in the productivity I have achieved, working at home. It's been awesome. It is
by ChrisMarshallNY 7y ago
I like this blog.
As a "semi-retired old dude," I have been absolutely reveling in the productivity I have achieved, working at home. It's been awesome.
It isn't just because I'm working at home. I suspect that a lot of it is because I'm working alone.
I was a manager for a long time, and quickly realized that "team overhead" was the true enemy of productivity. This includes things like Slack convos, and water-cooler chats.
It's a long topic, but all sorts of things are required to enable a good team integration; especially if we need to have a bunch of less-experienced team members on board. I was fortunate to lead a team of very experienced engineers. We shared a vocabulary and a common vision, so a great deal of "basic" overhead was avoided.
The (big) downside of working alone, is that I need to keep the scope of my projects reasonable. I can get a lot more done than most lone developers, but it's still a great deal less than what can be accomplished by a tight team.
As long as we have teams, we'll have overhead challenges.
- quietbritishjim 7y agoI think it is well accepted that the larger the team/company, the greater the inefficiency, and one person is the most efficient is all. But that it's only productivity per person, not the total amount produced. At the end of the day, some products (be they software, cars, or whatever) are complex enough that you need more than one person working on it. Even if that means moving from a signs person to a team of (say) four when your only wanted to double the amount of work done. Still, I can see why returning to working on one-person projects where you get loads done would be really satisfying.
- treis 7y ago>But that it's only productivity per person, not the total amount produced. I'm not sure that's true because of differing expertise, bouncing ideas off someone, and help in getting unstuck. I'm guessing productivity peaks in a team of 3-5.
- lonelappde 7y agoDo you believe that Google or Microsoft would be more successful in aggregate as 10000 5person startups?
- treis 7y agoNo, because some projects are big enough where they can't be done by a 3 person team. If Google takes 100,000 developer hours to write, it would take a 3 person team 15+ years to create. But you can't take 50 developers working 2,000 hours and get it done in a year. You need something like 100 developers because they are half as efficient when working in that big of a group.
- brianmcc 7y agoIndeed - 200 people at 25% efficiency is still 50 people-units of contribution!
- knightofmars 7y ago>I was a manager for a long time, and quickly realized that "team overhead" was the true enemy of productivity. This includes things like Slack convos, and water-cooler chats. An enemy to the productivity that you observed and measured. If you removed these Slack convos and water-cooler chats then you may find an increase in the productivity you measured but a drop in the actual value provided. Why am I saying that is the case? Because, water cooler-chats and Slack conversations have an effect of disseminating information throughout an organization. Someone in team A may realize that they're working on a problem similar to a person in team B. While this may not be an issue in smaller companies as a company grows it becomes more and more common that team silos start to arise. Overlap in work to be completed also becomes more common as the "start-up solve it ourselves" mentality is applied by each team instead of organizationally. Second, if you don't have a rapport with your co-workers (fostered through Slack conversations and water-cooler chats) then you're going to have a harder time communicating with them. Why? Because everyone communicates in different ways. Being able to understand a persons communication style and emotional state comes through understanding the person. The article calls this out, "I love collaboration, whiteboard sessions, small brainstorms, midday team coffees, and happy hour drinks. These things build community, make the work better, and are defintely needed. "
- ChrisMarshallNY 7y agoExactly. If anyone was a fan of the old BOFH articles, they may remember that Simon's aim was to make the network as efficient as possible, by eliminating the biggest inefficiencies; namely, the users. I just think that folks conceive of remote work as some kind of "overhead-free" panacea.
- felideon 7y ago> I was fortunate to lead a team of very experienced engineers. Too bad you were more worried about your own productivity than paying it forward and mentoring less experienced engineers. God forbid you would have had that misfortune.
- ChrisMarshallNY 7y agoI'd gently suggest that this may not be the best place to make posts like that. As a matter of fact, you'd be very surprised at the amount, and type, of mentoring that I do and have done, for decades.