3 ms·
This is one of the most absurd, black-and-white things I've ever read. Does innovation come from running, showering, lying in bed? Absolutely, no question. Bu
by crazygringo 4y ago
This is one of the most absurd, black-and-white things I've ever read.
Does innovation come from running, showering, lying in bed? Absolutely, no question.
But at the same time, when you get a diverse group of people to solve particular problems, they generally come up with far better solutions than any one of them would have on their own.
Because these are really about two totally different types of problems. The first "private innovation" one is often about finding a clever solution to a relatively well-defined problem that is "puzzle-like" -- math, code, chemistry, whatever.
The second "group collaboration" one is often about finding a workable solution to a relatively ill-defined problem that is people/organizational/product -- what is the right marketing campaign, right new product, right new vacation policy? Where the most valuable contribution is "wait, but have you thought of this?" or "wait, but if we do that <bad thing happens>" and everyone says "oh good point, I didn't know that was a constraint/solution!"
The obvious answer is that both are valuable. The idea that they are somehow at odds, or that only the first one is "work", is ludicrous. It's true that "individual contributor" jobs often fall more into the first category. But to denigrate the second category as "not work" is both disrespectful and, frankly, just idiotic.
- P5fRxh5kUvp2th 4y agoI disagree, the value of a group is in keeping people grounded. That security person is going to overvalue security, that web person is going to overvalue the frontend and that cloud advocate is going to overvalue microservices. But we have another name for that process, requirements gathering. It's not work in any meaningful sense outside of it being something that needs to happen before implementation. But it's output isn't all that useful unless you ARE an implementer. And that's the rub. The PROBLEM is that people love to talk and wax eloquent to show their intelligence and you get pulled into stupid conversations as a result.
- hinkley 4y agoGroup collaboration can rely on cleverness when someone builds a hypothetical on top of a set of assumptions that sound reasonable but contain elements that are foreign to everyone on the team. And clever ideas often benefit from a round of annealing to smooth out corner cases and ergonomics. This can either be direct feedback or the result of asking questions about the solution, triggering the author to refine the idea while explaining it.
- MetaWhirledPeas 4y ago> The obvious answer is that both are valuable. The idea that they are somehow at odds, or that only the first one is "work", is ludicrous. It's true that "individual contributor" jobs often fall more into the first category. But to denigrate the second category as "not work" is both disrespectful and, frankly, just idiotic. But let's be honest. Most mantras try to force all work into the "group collaboration" bucket. If HR and other management-training groups value isolated work and individual contributions they sure don't show it. Literally every piece of training I've received about working effectively has been about collaboration.* I think that's because most work training material is not really about innovation or productivity at all; it's about avoiding HR gaffes and workplace conflict. *Don't get me wrong; collaboration is a superpower, and many ineffective work relationships I've observed were hampered by someone's inability to collaborate well.
- crazygringo 4y ago> Most mantras try to force all work into the "group collaboration" bucket. If HR and other management-training groups value isolated work and individual contributions they sure don't show it. Literally every piece of training I've received about working effectively has been about collaboration. I think that's because isolated/individual work is so obvious and default that there's nothing to train. People know how to work alone. They often have to be actively encouraged to collaborate, however. HR isn't trying to force "all" work into collaboration, that's silly. But the right way to collaborate often isn't remotely obvious, when there are so many types of collaboration and so many different types of tasks/projects. So training makes sense and pays off here.
- deleted 4y ago[deleted]
- dec0dedab0de 4y agoI think design by committee rarely turns out well. However, listening to the groups response to an already working product/demo can be very valuable before the next release.
- Joeri 4y agoWhat the group is good at in your second category is precisely defining the shape of the problem. In my experience the solution is then still born from an individual's creative efforts, even during this group effort. I prefer the sandwich model of cooperation: get together to define the problem, separate to work on it, get together to review solutions, iterate.