Excerpts:
Interviewer: Does the creation of Design admit constraint?
Eames: Design depends largely on constraints.
Interviewer: What constraints?
Eames: The sum of all constraints. Here is one of the few effective keys to the design problem: the ability of the designer to recognize as many of the constraints as possible, his willingness and enthusiasm for working within these constraints. The constraints of price, size, strength, balance, time and so forth. Each problem has its own peculiar list.
Interviewer: Does Design obey laws?
Eames: Aren’t constraints enough?
[1] http://blog.designersrevolt.com/post/52143068880/the-definit...
Also, their interview set in a beautiful layout by House Ind, sure did help drive the point better - http://eames.houseind.com/objects/catalog.html
It might still be freely available as a catalog to those interested in their products. I highly recommend that one.
I totally agree with you on shifting away from manager-centric approaches. I really like the Lean focus on customer value. Out from that center are people who directly add value: line workers, engineers, designers. Managers become necessary overhead (when they're just coordinating) or indrect value-adders (when they're helping tune the processes that actually add value). That's in contrast to the traditional western approach, where managers are bosses, people whose opinions win because they're big kahunas.
I think this is also the reason so many really old-school video games are still not just playable, but can actually (arguably, of course) be even more fun than most of the current-gen eye candy. I'm thinking of Pac-man, Joust, and their ilk. Talk about embracing constraints.
EMBRACE CONSTRAINTS!
"If all our airplanes keep getting japanese bullets in the wings and tail, don't put more armor there--that's were we don't need it. Put it where the airplanes that don't survive get shot." - Abraham Wald
I also think there is a better point to be made about what sorts of constraints produce elegance and which ones are just frustrating and produce hacky workarounds. I think in order to make that point, someone would have to do some engineering history research and some insightful thought to see how an engineer's mindset and a projects constraints interact to produce elegance. I suspect the development of those video games could be a fruitful place to look for that history.
Social networks have thrived on obvious constraints. When looking for a startup idea, sometimes I try to reimagine a popular tool or service with additional constraints.
Which is to say that creatively working within hard constraints being a good thing is a universal creative rule, not specific to tech or social networks at all.
So 4chan perfectly fits in the parent's list of social network like things based on arbitrary contraints
But at the earliest stages, when exploring a market and business opportunity, premature constraints can be deadly because they often encourage you to ignore feedback from the market and make assumptions that aren't necessarily correct. The result, in many cases, is that companies end up solving problems that don't exist, or that aren't painful enough to support a real business.
In my experience, there are just as many engineers trying to make their jobs easier (by pushing to constrain scope at all costs) as there are product managers/business owners who aren't very good at defining problems and crafting sensible solutions to them.
Your manager-centric versus engineer-centric comment suggests that managers are inherently less capable of developing solutions to problems than engineers but in reality, the real issue is that there are relatively few product-savvy engineers and relatively few engineering-savvy product managers.
Form is liberating.
As far as I could see, it seemed to boil down to finding and fixing bottlenecks. Focusing on the critical paths in a process whether project schedules or chip designs is just par for the course. I don't know whether I missed something.
> As an engineer, I love hearing firm constraints from the beginning.
Sure, but note that these two points aren't in conflict. As someone building solutions, of course you want as firm a definition of the problem as possible, and constraints are part of that. But its still a critical failure to over-constrain the problem at the start (or any other time) -- constraints are essentially just a different way of phrasing requirements, and overconstraining a problem is exactly specifying superfluous requirements. Extra, unneeded constraints make the ultimate solution worse, because they mean you are solving the wrong problem -- and a more complicated problem than the one you actually needed to solve.
Well yes tautologies are tautological and all, but the point is that GP and the people agree with it suspect that their definition of "over-constrain" happens way way past where the article's author does.
However the truth is that constrains can be broken as long as you realize that doing so has a cost. Taking this into account expands the solutions space hugely, which both means that if you can take advantage of this you might find overall better solutions, while at the same time it can be overwhelming and paralyzing.
Edit to add: sometimes when the solutions space is too big artificially and arbitrarily limiting it might help.
Constraints (e.g. player class systems) reduce the raw number of choices you can make, but the ones left behind are more interesting and meaningful.
As an engineer, I love hearing firm constraints from the beginning. The constraints are what breed elegance; there is no such thing as an elegant solution when there is no shape to the problem. It's nice if the constraints are prioritized so you know what to give up if you can't satisfy them all. But there's nothing quite like saying "Yeah, we did this thing in two weeks that everyone assumed was impossible, and we did it without a binary push" or "Through our clever architecture, we accomplished with one server what everyone thought required a whole rack."
I believe design is the same way. The designs I've seen where the dictum is "Let your creativity run wild!" tend to be uninspired, while the ones I've seen where it's "This is what the user is trying to accomplish, and we have a 4 inch screen and 10 seconds to hook them" are often much more creative.
As a manager, the constraints are annoying. But one consequence of that is that setting firm constraints will tend to shift your culture from being manager-centric to being engineer- and designer-centric, which IMHO is a good thing.