Collaboration Workshop: What description do you like best?
Hi! Hope you can help me. I’m creating a new half-day workshop on collaboration, giving designers some ideas on how to work together better. I’ve got two possible descriptions for the workshop. Both are accurate summaries of the exact same workshop, with different emphases. Which do you like better?
Option A: Aspects of Collaboration
The world seems intent on classifying people as introverts or extroverts. And people who strongly identify with each group seem intent on defending their way of life.
The truth is that humans are far more complex, and that regardless of preference you have to work with other people. Collaboration is here to stay.
But how does collaboration work? What makes it work? Why is it deceptively hard?
Most organizations assume that people know how to work together. They assume that such skills are either innate or taught during childhood. If your experience was anything like mine, you didn’t get Collaboration 101 in college. No, you were taught how to work with other people by being thrown into the deep end.
And now, we all have some bad habits to unlearn.
The focus of this workshop is to learn essential behaviors for successful collaboration. We’ll provide context by:
- Validating the need for collaboration
- Debunking the myths of collaboration
- Dismantling the obstacles that prevent collaboration
- Describing the four aspects of positive collaboration
The four aspects of positive collaboration are:
- Definition & Clarity: Everyone must have a shared understanding of the work
- Accountability & Ownership: Everyone must understand their role and each other’s roles
- Awareness & Respect: Everyone must treat other members of the project team respectfully
- Openness & Honesty: Everyone must be as transparent as possible
Behaviors that embody these aspects generally yield positive outcomes. Though this workshop, we’ll identify and discuss such techniques and how to integrate them into your process.
Option B: Collaboration Framework
More than ever before, web design demands active and pervasive collaboration. With the complexity and extensive integration of online services design teams must work together effectively. Gone are the days when dropping a set of wireframes over the wall was the extent of my collaboration.
Successful collaboration relies on a harmony between three things:
- Tools: the techniques, applications, and methods we use to support collaboration
- Mindset: our attitude and preferences that guide our choices for how we approach work
- Culture: the ecosystem of policies, incentives, and peer pressure that provide context for our work
Each of the elements in the tools-mindset-culture triplet must be structured to enable collaboration without overpowering individual contributions.
In this workshop, we will:
- Learn skills for listening better, and behaviors that impair our ability to listen
- Consider the obstacles that prevent people from using collaboration effectively
- Examine designers’ insecurities and frustrations that often prevent them from working together effectively
- Discuss techniques (tools), attitudes (mindset), and organizational policies (culture) that yield positive collaboration
- Identify day-to-day behaviors that designers can adopt to improve their working relationships
You will come away from the workshop with a collection of new skills to try on your next project, whether you’re working one-on-one with a client, or on a large multi-disciplinary design team.
The Role of the Design Mentor
A couple days ago, I got an email from a local designer asking me to be his mentor. (I’m listed on the Information Architect Institute’s web site for this.) Whenever I get such a request, I immediately ask about expectations: goals, commitment, and topics. Upon getting his response, I crafted the following, which I thought would make a pretty good addition to this otherwise anemic blog. Enjoy.
I’ve mentored about a dozen people over the years. One thing to realize is that for both of us, this commitment will fall to the bottom of the to-do list. Client commitments, business commitments, and family commitments will always come first. Because this kind of “professional growth” lacks the context of real work, it’s easy to de-prioritize it, you know?
I can’t commit to working on this for more than one hour per month. That is, no work outside a monthly phone call, as little preparation as possible. I do this not because I’m lazy (though I am) but because I know I’ll never get to those assignments. I have more billable work than I can possibly accomplish, more tasks to run my business than I can possibly get to, and I turn off work in the evenings and weekends to spend time with my family. What little “free” time I do have, I dedicate to side projects that are personally important to me.
I tell you all this to help you understand what I’ve learned over the years mentoring people both inside and outside EightShapes. By far the best possible way to grow professionally is to take time to reflect on your work. As a mentor, my job is to facilitate that internal conversation with yourself, to build your self-awareness, and to improve your ability to critique your own work.
By setting these expectations with “mentees,” I hope to institute a specific dynamic for our conversations. We look at the previous month’s work and we talk about what they could have done better. We talk about difficult conversations they experienced and talk about what insecurities and mental ticks lead to those situations. We consider upcoming work and talk about how to incorporate lessons learned from their previous gigs. Though I’ve been a teacher (lectures and workshops), in this relationship I’m less tutor and more therapist and sounding board.
If that’s not what you need, then I’m not the right mentor for you.
Everybody’s Got Something: Reflections on Rare Disease Day
Today is Rare Disease Day, a day set aside by the National Organization of Rare Diseases and other international groups to raise awareness for this group of conditions. A rare disease is one that affects less than 200,000 Americans. Taken together, however, 10% of Americans have a rare disease.
I believe that number is going to grow.
With increasing scientific knowledge and life expectancy, we will discover more diseases faster than we eradicate them. Fine-tuning our scientific “vision” will allow us to see nuanced differences between conditions. Our increasing reliance on genetics for diagnosis and treatment will further personalize the lens through which we see conditions.
Me and the orphans
I have two rare diseases (sometimes known as orphan diseases), not related to each other. I was diagnosed with the first at age 6 and the second at age 15. Though eminently treatable (compared to many other conditions in the rare disease database) they do have a daily impact on my life.
That said, I consider myself lucky: lucky to have been born into a family that took my symptoms seriously, that sought the best treatment, and that could afford to pursue those therapies. I’m fortunate to have found a life partner who took it upon herself to learn more about these conditions than I know, and to stand patiently by my side as I continue to confront them in adulthood. She made the diseases “ours,” not just “his,” and that alone makes me confident I found the right person for me.
Coping strategies
In 1997, I set up a support group for one of my rare diseases. It’s an endocrine disorder with a relatively simple treatment. Untreated or undiagnosed, however, the symptoms can be insidiously devastating. Caught early, and treated reliably, the patient can have a semblance of normalcy. Otherwise, the disease becomes as much a psychological one as a physical one. The support group I set up was online: the Internet, it seems, was made for connecting just my kind of people together.
Today that group has 1700+ members, and I’m not very active in it as I once was. But the traffic on it is as vibrant as ever. Read the messages and you’ll see complex patterns: lots of similarities, but lots of differences, too. The disease is the same from person to person, but each one is equipped differently to cope with it. They internalize it in different ways, and use it to magnify their insecurities, or obscure their strengths.
For many members, the mere existence of a support group is therapy enough. In the early days, most of us expected to go through this condition alone. The doctors that treated us generally hadn’t heard of the condition, much less treated other people with it. With a support group came sympathetic voices, empathetic ears, and myriad information and advice.
Everybody’s got something
When I first set up the group and still watched the traffic on the mailing list I felt a strong bond with the other members: we share so many life experiences. And yet, I couldn’t help but feel that each of us was dealing with a different disease. That may have been the moment when I adopted “everybody’s got something” as a sort of motto, incorporating it into the philosophy of my early adult life.
It is about as close to compassion as I get, though not for lack of trying. No doubt compassion is hard work, but it seems as most people aren’t even trying any more. I can’t say whether people are feeling less for each other, but I can say that people aren’t doing much about it. I hope this doesn’t come across as cynical ramblings of a man with a few years’ experience under his belt. Daily interactions with most strangers reveal a stark lack of compassion. Daily accounts of global news show this playing out writ large.
The rare disease is a double-edged sword. On the one hand, the increasing specialization and customization of medical conditions implies a greater focus on “me”. As people are confronted with increasingly individualized conditions, where they may never meet anyone else with the same one, they are out of necessity turned inward. Each person faces his or her own natural disaster, not one that affects an entire community.
On the other hand, people with rare diseases realize that they aren’t alone. They see what I came to see: my demons look and act differently from yours, but they are no less significant, relevant, or impactful. It can be easy to dismiss one’s own plights (as my peer group does frequently appending tweeted complaints with “#firstworldproblems”) but plight is plight. Just because someone else is suffering from something, perhaps more devastating or more debilitating doesn’t make my suffering less important.
And in the context of me in my life (or you in yours) obstacles and challenges can’t be compared to those of another. It is this, the emergence of unexpected challenges in unique contexts, that gives us our united front. It is in this confrontation we find our compassion for others. Whatever I’m dealing with, you’re dealing with something equally complex, equally challenging, and equally consequential.
My rare diseases have taken much from me. But what they’ve given me is a perspective that I doubt I could have gotten elsewhere. That said, you don’t need a rare disease to have this perspective. Everybody’s got something, and not just a medical “something”. That fact doesn’t diminish what you have — the challenges in your life you don’t get to choose — but don’t let your own challenges distance you from other people. As we increasingly confront different things, we need compassion more than ever to cope, to make sense, and to heal.
Silly Amazon Prime Business Rule
A few weeks ago, my wife got an email from Amazon saying that she could no longer take advantage of Amazon Mom benefits. After a brief exchange with customer service, she learned that because she shares my Amazon Prime account, the Amazon Mom discount on diapers no longer applies.
We’re talking about 15% off diapers.
Seems like an easy fix: Make Sarah the Amazon Prime primary account-holder. Of course, this doesn’t appear to be possible through the Manage Prime Account.
So, now, for all the world to see, the email I wrote to customer service. I’ll be sure to post their response in the comments.
Currently, my wife and I are Amazon Prime members. The primary membership is attached to my account and shared with my wife. I’d like her to have the primary membership. Please let me know how to accomplish this.
Why do we want to switch?
My wife is no longer allowed to take advantage of Amazon Mom benefits through our Amazon Prime account. According to your policy, only the primary account-holder can use Amazon Mom benefits.Why do we care?
Frankly, I’m sorry to bore you with the details, but it’s your silly rule. In our house, Sarah’s in charge of ordering all the stuff for the kids. She stays on top of this stuff. I order the stuff for the kitchen — paper towels, garbage bags. But you already know this. You know more about how we run our house than my own mother. Not that she hasn’t tried to find out.The question is, why do YOU care?
Seriously, Amazon. The diapers come to the same house. We pay with the same credit card. Why do you care whether the Amazon Mom account is attached to the primary Prime account or a shared account.Thanks,
Long-time customer, First-time complainer
Dan
As someone who designs for the web, I’m no stranger to silly business rules. Remember when you couldn’t return stuff to the store that you bought online? This seems like that, only more arbitrary and more obscure.
Book Review: Meals in Minutes, by Jamie Oliver
My wife and I peg my transition to “family chef” at around the time our first son was born. Until then, we’d mostly shared cooking duties, but with her tied up in a strict baby schedule, it made sense for me take over. Cooking soon went from household responsibility to serious hobby.
The Secret Ingredient is Improv
For the family chef, the key to cooking is improvisation. Home cooks need to learn enough to work with what’s around the kitchen when we haven’t had time to shop. This isn’t an Iron Chef kind of thing: I haven’t been forced to cook with squid ink and styrofoam. But the family cook needs to know whether he can get away with making Meal A when he’s missing ingredients X, Y, and Z.
While the Best Recipe series has been a staple of our kitchen for more than a decade, Bittman’s “How to Cook” cookbooks were eye-opening. His approach is entirely modular, going beyond 1-2 variations for most recipes. He also lists ways to extend recipes and includes tables showing how to incorporate different ingredients. For me, Bittman’s books helped escalate my skills by giving me a broader platform for improvisation.
Enter Jamie
Jamie Oliver’s Meals in Minutes: A Revolutionary Approach to Cooking Good Food Fast
is quite the opposite. Each page is a self-contained meal, including three or four courses including dessert. The ingredients list at the top of the page covers all the dishes and the method intersperses instructions for each one. In short, you follow directions to prepare a meal, not to prepare each individual dish.
Jamie Oliver is not the kind of person I’d want to go have a cup of coffee with. He strikes me as a bit of a goofball. (Not that I’m not a goofball, just a different sort. To be fair, I’m not sure I’d want to coffee with Bittman, either.) But we see eye to eye philosophically, and Meals in Minutes culminates many of his ideas. In short, Americans should be cooking more. (Not eating more, mind you, cooking more.) Our cultural dependence on convenience and consumerism has made us–as a whole–lose perspective on what it means to invest time in our food. Beyond this, his message is one of encouragement: You can do this. For Americans who are stymied by the kitchen, he seeks to make cooking not just accessible, but meaningful.
To that end Meals in Minutes is a mixed bag. There are some things I love about this book:
- The design is beautiful. The method is easy to follow visually, and not having to turn pages is, surprisingly, one of the best things ever to come to my kitchen.
- The meals depart nicely from family cook staples like “chicken, rice, and steamed vegetable”. I’m making things I didn’t think would be easy to do.
- The recipes have a nice mix of fresh ingredients and pantry items.
- The method is efficient. Both recipes I’ve prepared in well under an hour.
- For more experienced cooks, Jamie’s recipes have some nice techniques you can borrow.
What Kind of Chilis?
Some reviews have criticized the format, since it’s not easy to make just one recipe. These reviewers, I think, miss the point of the book. Instead, the main drawback of Meals in Minutes is in the ingredients. There are some pretty obscure ingredients, and Oliver offers no guidance on substitutes.
I’m reluctant to experiment with substitutions since the balance of the method seems to depend so much on the ingredients. That said, I used jalapeno chilis instead of scotch bonnet in the Jerk Chicken. And when Sarah couldn’t find mixed organic mushrooms, we just used shitake in the Mushroom Risotto. (I know, I know, First World problems.) With the success of these meals, I’ll definitely use the book again.
What’s Next: Chicken Pie and Asian Salmon
There are at least half a dozen other meals in the book I want to try. (About a third of the meals involve red meat, and I only eat fish and fowl, so getting 8-10 meals out of the book is actually a really good ratio.) I’m a sucker for chicken pie, and Oliver’s meal includes that with some nice vegetable sides. He also has a chicken peri-peri meal with dressed potatoes and arugula salad. I’m eager to find a way to use frozen salmon in a recipe without it tasting like it was frozen. Meals in Minutes has two–asian salmon and crispy salmon–that look worth trying.
Bearing in mind that Meals in Minutes may send you on a wild good chase in your grocery store, it’s a worthy addition to the family cook’s bookshelf. It will inspire me to add new meals to the rotation and expose my cooking to some new ingredients. It will teach me to be more efficient in the kitchen, and add some new techniques to my repertoire.
Surviving Design Projects (Dan’s little distraction)
The quick version
Surviving Design Projects is a collection of ideas about managing conflict in creative environments. For now, it’s a blog that deals with three things: Situations — the circumstances that lead to conflict. Traits — the aspects of designers’ personalities that may contribute to or help them solve conflict. Patterns — techniques for addressing conflict.
Why conflict management?
The first edition of my book Communicating Design includes some thoughts on how to present and use design artifacts — sharing a site map with the programmers, for example. The second edition expanded on this, suggesting a repeatable, adaptable outline for leading discussions about design. From the outset, I knew that the artifact in itself was small consequence to the success of the design project. Instead, it was how the designer used the artifact to advance the project.
Advancing the project is more than just hitting milestones. It’s soliciting feedback and validatation. It’s helping the project team understand implications. it’s ironing out details in working sessions. In short, it’s getting everyone not just behind the design concept, but the approach to design as well. This ongoing alignment effort is where conflict is incubated. No team is ever perfectly aligned, and that’s where conflict emerges.
I’ve facilitated dozens of workshops on deliverables, and similar conclusions emerged from every one. Workshop participants report that their greatest challenges aren’t solving design problems or representing their ideas through artifacts. Instead, design teams the world over struggle to deal with the conflict that arises in these endeavors. They mention lack of engagement, or stepping on each others’ toes, or working at cross purposes, or general creative differences. They mention confronting demanding bosses and unreasonable clients. They roll their eyes remembering that one person who caused so much trouble.
Through these discussions about creating design artifacts, I learned that my initial efforts to provide a framework for talking about them wasn’t enough.
So, what have you been doing?
For the last several years, I’ve been thinking a lot about this, asking myself questions like:
Why is there conflict on design projects?
What are the different kinds of conflict on design projects?
What would it take to ensure a conflict-free project?
Are successful projects always conflict-free?
What techniques do we use to moderate conflict?
How can designers be more self-aware?
I’ve done a few things in the public eye on this topic:
- Co-facilitated a workshop with Chris on Difficult Conversations
- Presented some ideas on how to deal with difficult situations at the Web App Summit and at a NYC UPA event
- Wrote a few blog posts on self-awareness
- Presented a virtual seminar entitled Surviving Design Projects for UIE
Throughout this thought process, I sought a way to make the topic practical. Ultimately, collecting sob stories about challenging projects is cathartic but otherwise irrelevant to my day-to-day work. About a year ago, shortly after I finished the second edition of Communicating Design, I was reviewing some old notes and realized that I could capture conflict management techniques as patterns.
Patterns, situations, and traits
A pattern in interface design is a starting point solution for a typical problem. There might be a pattern, for example, for the log-in process, describing the basic elements of the interface and the flow of the interaction. Likewise, conflict management patterns provide simple starting points for approaching a difficult situation. These patterns suggest behaviors or things to say to deflate or redirect or avoid the conflict. Here’s an example:
Pattern: What’s your first step?
Ask colleagues what their immediate activity will be upon receiving a new assignment.
Use when:
- Employing a new methodology or technique, and you’re not sure how your team will proceed.
- Team members can’t offer specific answers about how they’ll contribute to the overall project or how they’ll address the project’s objectives.
Like design patterns, conflict management patterns have a brief description and a “use when,” which defines appropriate circumstances for trying the pattern. Upon developing them further, I’m confident I’ll identify other aspects I can use to structure them further. Many of these patterns are variations on some big themes like “listen better” or “start small”.
It was easy to identify other elements of conflict management — situations and traits. Situations are circumstances in which someone’s behavior is threatening to derail the project. I’ve also been thinking about how designers can be more self-aware — the traits that define our style of participation and contribution to design projects.
Where are you now?
These three aspects of conflict management — situations, patterns, traits — are described in my new blog Surviving Design Projects. At this point, I’m using it as a dumping ground to capture these individual elements.
What’s missing is the connections between them: how patterns apply to different situations, how traits may cause or avoid situations, and how patterns might challenge designers with particular traits. For each situation, I could point to half a dozen patterns that would help deal with those circumstances. For each pattern, I could tell a story about how it was used successfully. For each trait, I could talk about how different designers exhibit the trait differently.
What’s next?
To be totally transparent, I’d like to turn this into a book — a handbook on dealing with conflict in creative environments. Threaded with stories about how designers and design teams face conflict every day as a natural part of the process, the book would help them deal with this ongoing tension.
For now, I’m content to mould the bricks, but if you’re a publisher and think this is remotely interesting, please drop me a line.
Workshop: A visual approach to planning web sites
Join me in October and November for two workshops I’ll be leading the DC area. Each is a half-day on a Friday afternoon (when nothing good ever happens anyway) and we’ll dig into flow charts, site maps, and concept models–diagrams essential for planning web sites.
Here’s what we’ll talk about:
- How to create beautiful and effective diagrams describing the underlying structure of web sites.
- How to use those diagrams in planning web projects and how pictures can make the process more efficient.
- How to “level-up” your skills in flow charting and site mapping.
- How to walk through these diagrams with clients and colleagues.
Here’s what you’ll get:
- A four-hour workshop in a comfortable training room in the heart of downtown Bethesda (October) or DC (November).
- A workbook chock full of examples.
- A chance to win a copy of the 2nd edition of Communicating Design.
The workshops are $299 each, but with early bird pricing you can save 15%!
