collaboration
It passes by the river
Business people and developers
Engineering, design, and product management
The problem with CAD
We want you to work with an artist
The power of One
picnic.lectoro.me
Designer + Developer Workflow
An Article by Dan MallThe way designers and developers work together today is broken. It’s too siloed and separate; “collaboration” is a fantasy that few enjoy.
The state of advertising in the 1940s was similar. All of that changed when copywriter Bill Bernbach met art director Paul Rand. Their collaborative working style led to the birth of the idea of “the creative team,” the mutual respect and partnership between art director and copywriter that tended to yield unique results. Bob Gage, an art director that worked for DDB, the agency Bernbach co-founded, described it like this:
“Two people who respect each other sit in the same room for a length of time and arrive at a state of free association, where the mention of one idea will lead to another idea, then to another. The art director might suggest a headline, the writer a visual. The entire ad is conceived as a whole, in a kind of ping pong between disciplines.”
Isn’t that what we all strive for in our jobs? True collaboration with equals and partners? Ideas that build off one another? Why does this seem so far away for some of us?
The Hot Potato Process
An Article by Dan MallThe big misconception I’ve seen designers and developers often fall victim to is believing that handoff goes one way. Designers hand off comps to developers and think their work is done. That puts a lot of pressure on the designer to get everything perfect in one pass.
Instead, great collaboration follows what Brad Frost and I call “The Hot Potato Process,” where ideas are passed quickly back and forth from designer to developer and back to designer then back to developer for the entirety of a product creation cycle.
Nobody gives a hoot about groupthink
An Article by Baldur BjarnasonTwo relatively common ‘fashions’ today are real-time collaboration and shared data repositories of one kind or another.
Both increase productivity in the naive sense. We work more; everybody is more active; the group feels more cohesive.
The downside is that they also both tend to reduce the quality of the work and increase busywork.
Pair Design: Better Together
Pair design is the counterintuitive practice of getting more and better UX design done by putting two designers together as thought partners to solve design problems. It’s counterintuitive because you might expect that you could split them up to work in parallel to get double the design done, but for many situations, you’d be wrong. This document will help explain what pair design is, how it works, and tour through the practicalities of implementing it in your practice.
Asynchronous Design Critique: Getting Feedback
An Article by Erin CasaliGetting feedback can be thought of as a form of design research. In the same way that we wouldn’t do any research without the right questions to get the insights that we need, the best way to ask for feedback is also to craft sharp questions.
When we were all together in-person
A Quote“We believe that in-person collaboration is essential to our culture and our future,” said Deirdre O’Brien, senior vice president of retail and people, in a video recording viewed by The Verge. “If we take a moment to reflect on our unbelievable product launches this past year, the products and the launch execution were built upon the base of years of work that we did when we were all together in-person.”
Building Momentum
An Article by Dan MallFight the Waterfall
Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.
The Small Group
An Article by James MulhollandLying somewhere between a club and a loosely defined set of friends, the SMALL GROUP is a repeated theme in the lives of the successful. Benjamin Franklin had the Junto Club, Tolkien and C.S. Lewis had The Inklings, Jobs and Wozniak had Homebrew.
Around a dozen members is the sweet spot of social motivation: small enough to know everyone, yet large enough that the group won’t collapse if one or two members’ enthusiasm wanes; small enough that you are not daunted by competing with the whole world, yet large enough that you still need to be on your toes to keep up.
Scenius
Scenius stands for the intelligence and the intuition of a whole cultural scene. It is the communal form of the concept of the genius.
Mutual appreciation
A Fragment by Matt WebbTo use slightly different terms, mutual appreciation is a healthy jealousy without envy – a drive to achieve the same but without wanting to take it from the other.
Design Thinking
Ducks and decorated sheds
A duck is a building whose confirmation is a complete symbol or icon. A decorated shed is a building to which symbols, often commonplace signs, have been attached.
Clinging to ideas
Another aspect of design thinking that was evident in the foregoing case studies is the tenacity with which designers will cling to major design ideas and themes in the face of what at times might seem insurmountable odds. Often the concept the designer has in mind can only come to fruition if a large number of apparently countervailing conditions can be surmounted.
Even when severe problems are encountered, a considerable effort is made to make the initial idea work, rather than to stand back and adopt a fresh point of departure.
A concept of style
It is a concept based not on the classification of various physical features of architecture and urban design but on the problem-solving process itself. We have seen that the final outcome of a design process is strongly determined by at least three aspects of that process:
- the subject matter of the organizing principles which are adopted,
- the manner in which these principles are interpreted and reinterpreted in the context of the problem at hand, and
- the sequent of applying such organizing principles.
Consistency in style among the output of designers can thus be understood as a habitual way of doing things, of solving problems.
Form and figure
Form applies to “a configuration with natural meaning or none at all,” whereas figure applies to “a configuration whose meaning is given by culture."
Design skirmishes
it is apparent that the unfolding of the design process assumed a distinctly episodic structure, which we might characterize as a series of related skirmishes with various aspects of the problem at hand.
As the scope of the problem became more determined and finite for the designer, the episodic character of the process seems to have become less pronounced. During this period a systematic working out of issues and conditions took hold within the framework that had been established. This phenomenon is not at all surprising when we consider the fundamental difference between moments of problem solving when matters are poorly defined and those with clarity and sufficiency of structure.
Within the episodic structure of the process, the problem, as perceived by the designer, tends to fluctuate from being rather nebulous to being more specific and well-defined. Furthermore, moments of "blinding" followed by periods of backtracking take place, where blinding refers to conditions in which obvious connections between various considerations of importance go unrecognized by a designer.
Such plans were deemed efficient
The terrain of cities was subdivided along the lines of distinct and discrete patterns of use, with very little opportunity for mixing (separation and concentration of functions). After all, the home environment should be just that…while places of work should be aggregated and serviced with their appropriate supporting functions.
Such plans were deemed efficient.
Constrained by the medium
The inevitable reciprocation that occurs between the act of drawing and the thinking associated with it. The hand moves, the mind becomes engaged, and vice versa. We might ask: How much does the medium of expression actually constrain a design process?
A medium has a way of constraining our choices, and this influence may not involve conscious choice at all. The planner, in the end, sees and understands only those things for which they can provide expression.
Autonomous constraints
Autonomous or independent constraints do not derive from the problem as given and understood…there was nothing in the problem statement, or brief, that required any reference be made to it. This constraint, introduced by the designers, usefully transcended the givens of the problem situation.
Unless the entire problem at hand can be solved using strictly problem-oriented constraints, we have to step outside the known problem context in order to continue problem solving activity.
The strange familiar and the familiar strange
The problem solver, when confronted with a new and yet unsolved problem, overlays the structure of the unsolved problem with an apparently similar problem with which he or she is experienced.
Making the strange familiar and the familiar strange are also principally based on the use of analogy.