3 ms·
Is this really all that surprising? In school everyone always complains about group work sucking.
by bawolff 4y ago
Is this really all that surprising? In school everyone always complains about group work sucking.
- haswell 4y agoI think this is a good anecdote that reiterates the kind of “collaboration” the article is talking about, but is not the “real” collaboration people strive for. The reason group projects in school felt so terrible was because the end goal was collaboration, not some higher outcome. Collaboration can unlock outcomes that can’t be achieved as an individual, but collaboration can’t be the desired end state.
- pojzon 4y ago> The reason group projects in school felt so terrible was because the end goal was collaboration, not some higher outcome At least in my school the end goal was never collaboration but getting a good grade. Thus individuals who cared did most if not all work. Those group projects had sense only if you were paired with equally skilled and motivated ppl. And ofcourse you had to LIKE them. Its exteremely hard to be cooperative with ppl you consider as assholes.
- haswell 4y agoI’m sure that was your end goal, but when someone assigns a collaborative project, it’s usually to teach students how to collaborate, while forgetting that just forcing a group to do the same task together is not the same thing as collaborating. It is from this base that problems emerge, IMO. Kind of like “synergy”, which is a real thing, but hard to define and difficult to artificially achieve.
- yodsanklai 4y ago> In school everyone always complains about group work sucking I supervised software engineering projects at university. It works well when students in a group have similar motivation and abilities. This is the case when they are free to choose who they collaborate with. Otherwise, students are usually frustrated. In a company, teams can be much more heterogeneous (cultural background, skills, age, social status, experience...), and the pressure is higher: goals can be loosely defined, evaluation is less fair, stakes are higher for everyone, managers can be less benevolent than teachers...
- ergocoder 4y ago> managers can be less benevolent than teachers... Depend on what benevolent here means. It is much easier to address low performers in a company setting.
- closeparen 4y agoIn my corporate software projects, a particular engineer owns the outcome. They have lines of communication with the managers of other assigned engineers, and considerable pull in their performance reviews and promotions. The floor is that someone cares and the others will make what could be mistaken for a good-faith effort, which is lightyears better than a school project.
- ergocoder 4y agoGroup work has all the bad attributes: - can't be fired - reward is low - members often have the exact skillset. - nobody has superior authority. How does one even make a decision where people disagree? Teachers have no experience working in the real world and will often say "you will need to learn to work with bad people". Meanwhile every successful person will tell you to fire bad people as soon as possible. If you assign a bunch of low performers to Steve Jobs and tell him he can't fire them and have to give them work, even Steve Jobs would probably fail.
- lucb1e 4y agoSchool group work doesn't have to be bad. We had a semester-spanning 6-person group project during my software engineering study. Long story short, by the fourth and final semester project, I cooked up a recipe that solved some of these problems. I had re-invented having a manager. Because I was good at coding, and by this semester this was known so people trusted me to not just idle around, I could propose on day 1 that I'd just be the 'manager' with no assigned share of the work. I'd be the solver of problems as they popped up, the person that goes around making sure nobody is stuck and everyone can work. And also that everyone does work, which turned out to be important because the notorious Joel was assigned to us and, indeed, he barely showed up and didn't do work at home either. After some conversations, going back-and-forth, and spending time on this, I managed to convince the teachers to officially kick him out after about three weeks (into a ~half-year semester). The rest of the semester, I spent most of the project time helping with problems that others were stuck on. (Not that I was a superbly amazing coder, but two know more than one and this really helped our pace.) It's a real shame that was the last semester of that study because the setup worked like a dream. Two of the group members weren't so strong in coding and we were one person down with roughly the same workload (though for this, too, I had some time to spend on 'lobbying', and we got a slight reduction), but by juggling tasks correctly and sitting together when necessary, it ended up working really well. One guy in particular I remember wasn't too good at the job, but he would always work hard and, once unstuck, make good progress for the day. Great guy, always in good spirits, fun to work with and I'd hire him today if he applied despite the mediocre skills. I think knowing his strengths and weaknesses (knowing what tasks to assign and do some pair programming) is all you need to have a great colleague in him that cheers up five others and is still a net-positive in the amount of work done.
- closeparen 4y agoIt is perhaps surprising to a management class that believes collaboration is the ultimate good in all circumstances and you can never have enough of it.