Showing posts with label creativity. Show all posts
Showing posts with label creativity. Show all posts

Monday, October 6, 2014

Good Notes

Final lovely quote from Creativity, Inc. by Ed Catmull. Please get the book for yourself if you want to know how to foster creativity in a community or company.
In the very early days of Pixar, John, Andrew, Pete, Lee, and Joe made a promise to one another. No matter what happened, they would always tell each other the truth. They did this because they recognized how important and rare candid feedback is and how, without it, our films would suffer. Then and now, the term we use to describe this kind of constructive criticism is "good notes." 
A good note says what is wrong, what is missing, what isn't clear, what makes no sense. A good note is offered in a timely moment, not too late to fix the problem. A good note doesn't make demands; it doesn't even have to include a proposed fix. But if it does, that fix is offered only to illustrate a potential solution, not to prescribe an answer. Most of all, though, a good note is specific. "I'm writhing with boredom," is not a good note.
Catmull quotes Andrew Stanton at length explaining the difference between criticism, and constructive criticism, ending with: It's more of a challenge. "Isn't this what you want? I want that too!" [103]

I think this bit is the key: good criticism focuses on the common goal: a great product. It inspires, rather than creating defensiveness.

I read Reviewboard feedback in a sort of random way, and see a lot of "good note" behavior. But that timely part is sometimes missing. We have some Reviewboard requests languishing, along with patches in bug reports. Fortunately, the Gardening project has sprung up to improve this part of the community. Help out if you have time! https://mail.kde.org/mailman/listinfo/kde-gardening and https://community.kde.org/Gardening.

Friday, September 26, 2014

Overcoming fear

In the last few posts, I've been exploring ideas expressed by Ed Catmull in Creativity, Inc. Everyone likes good ideas! But putting them into practice can be both difficult, and frightening. Change is work, and creating something which has never existed before, is creating the future. The unknown is daunting.

In meetings with the Braintrust, where new film ideas are viewed and judged, Catmull says,
It is natural for people to fear that such an inherently critical environment will feel threatening and unpleasant, like a trip to the dentist. The key is to look at the viewpoints being offered, in any successful feedback group, as additive, not competitive. A competitive approach measures other ideas against your own, turning the discussion into a debate to be won or lost. An additive approach, on the other hand, starts with the understanding that each participant contributes something (even if it's only an idea that fuels the discussion--and ultimately doesn't work). The Braintrust is valuable because it broadens your perspective, allowing you to peer--at least briefly--through other eyes.[101]
Catmull presents an example where the Braintrust found a problem in The Incredibles film. In this case, they knew something was wrong, but failed to correctly diagnose it. Even so, the director was able, with the help of his peers, to ultimately fix the scene. The problem turned out not to be the voices, but the physical scale of the characters on the screen!

This could happen because the director and the team let go of fear and defensiveness, and trust that everyone is working for the greater good. I often see us doing this in KDE, but in the Community Working Group cases which come before us, I see this breaking down sometimes. It is human nature to be defensive. It takes healthy community to build trust so we can overcome that fear.

Tuesday, September 9, 2014

Fixing mistakes and growing stronger

In Creativity, Inc., Catmull explores an example of where their structure had created some problems, and how they identified and fixed that, improving their over-all culture. I know this is a wall of text, but Catmull asks excellent questions. I felt it was worthwhile to copy for you. He says,
Improvements didn't happen overnight. But by the time we finished A Bug's Life, the production managers were no longer seen as impediments to creative process, but as peers--as first-class citizens. We had become better. 
This was success in itself, but it came with an added and unexpected benefit: The act of thinking about the problem and responding to it was invigorating and rewarding. We realized that our purpose was not merely to build a studio that made hit films but to foster a creative culture that would continually ask questions. Questions like: If we had done some things right to achieve success how could we ensure that we understood what those things were? Could we replicate them on our next projects? Perhaps as important, was replication of success even the right thing to do? How many serious, potentially disastrous problems were lurking just out of sight and threatening to undo us? What, if anything, could we do to bring the to light? How much of our success was luck? What would happen to our egos if we continued to succeed? Would they grow so large they could hurt us, and if so, what could we do to address that overconfidence? What dynamics would arise now that we were bringing new people into a successful enterprise as opposed to a struggling startup?

What had drawn me to science, all those years ago, was the search for understanding. Human interaction is far more complex than relativity or string theory, of course, but that only made it more interesting and important; it constantly challenged my presumptions.... Figuring out how to build a sustainable creative culture--one that didn't just pay lip service to the importance of things like honesty, excellence, communication, originality, and self-assessment but really *committed* to them, no matter how uncomfortable that became--wasn't a singular assignment....

As I saw it, our mandate was to foster a culture that would seek to keep our sightlines clear, even as we accepted that we were often trying to engage with and fix what we could not see. My hope was to make this culture so vigorous that it would survive when Pixar's founding members were long gone. [p. 64-5]
Again, I see an almost perfect match between their task and ours, where ours=KDE e.V.. In the Community Working Group (CWG) in particular, I see my task as essentially gardening. This includes improving the soil, weeding, but never removing valuable little shoots which can grow into exciting new directions for the community. Of course I can't carry the metaphor too far, since others do the planting. But we can keep the conditions for growth optimal with our work.

In the documentation workshop yesterday, we explored the current state of the KDE documentation, how we can improve access, and grow the documentation team again. We also found some large choke points, which includes KDE.org. We really need a web team! KDE.org is valuable real estate on the web, which has been neglected for too long. More about that later.....

For now, looking forward to another day of hard work and fun in Brno!


Saturday, September 6, 2014

Creativity and KDE

Creativity Inc., by Ed Catmull, President of Pixar

My book to read for this trip finally arrived from the library last week, and I could hardly wait to dip into it. I see a profound parallel between the work we do in KDE, and the experiences Catmull recounts in his book. He's structures it as "lessons learned" as he lead one of the most creative teams in both entertainment and in technology. His dream was always to marry the two fields, which he has done brilliantly at Pixar. He tried to make a place where you don't have to ask permission to take responsibility. [p. 51]

Always take a chance on better, even if it seems threatening Catmull says on p. 23. When he hired a person he deemed more qualified for his job than he was, the risk paid off both creatively and personally. Playing it safe is what humans tend to do far too often, especially after they have become successful. Our stone age brains hate to lose, more than they like to win big. Knowing this about ourselves sometimes gives us the courage to 'go big' rather than 'go home.' I have seen us follow this advice in the past year or two, and I hope we have the courage to continue on our brave course.

However, experience showed Catmull that being confident about the value of innovation was not enough. We needed buy-in from the community we were trying to serve.[p 31] My observation is that the leaders in the KDE community have learned this lesson very well. The collaborative way we develop new ideas, new products, new processes helps get that buy in. However, we're not perfect. We often lack knowledge of our "end users" -- not our fellow community members, but some of the millions of students, tech workers and just plain computer users. How often do teams schedule testing sessions where they watch users as they try to accomplish tasks using our software? I know we do it, and we need to do it more often.

Some sources rate us as the largest FOSS community. This can be seen as success. This achievement can have hidden dangers, however. When Catmull ran into trouble, in spite of his 'open door' management style, he found that the good stuff was hiding the bad stuff.... When downsides coexist with upsides, as they often do, people are reluctant to explore what's bugging them for fear of being labeled complainers.[p. 63] This is really dangerous. Those downsides are poison, and they must be exposed to the light, dealt with, fixed, or they will destroy a community or a part of a community. On the upside, the KDE community created the Community Working Group (CWG), and empowered us to do our job properly. On the downside, often people hide their misgivings, their irritations, their fears, until they explode. Not only does such an explosion shock the people surrounding the damage, but it shocks the person exploding as well. And afterwards, the most we can do is often damage control, rather than helping the team grow healthier, and find more creative ways to deal with those downsides.

Another danger is that even the smartest people can form an ineffective team if they are mis-matched. Focus on how a team is performing, not on the talents of the individuals within it.... Getting the right people and the right chemistry is more important than getting the right idea.[p. 74] One of the important strengths of FOSS teams, and KDE teams in particular, is that people feel free to come and go. If anyone feels walled out, or trapped in, we need to remove those barriers. When people are working with those who feed their energy and they in turn can pass it along. When the current stops flowing, it's time to do something different. Of course this prevents burnout, but more important, it keeps teams feeling alive, energetic, and fun. Find, develop, and support good people, and they will find, develop, and own good ideas."[p. 76] I think we instinctively know in KDE that good ideas are common. What is unusual is someone else stepping up to make those "good ideas" we are often given, to make them happen. Instead, the great stuff happens when someone has an itch, and decides to scratch it, and draws others to help her make that vision become reality. 

The final idea I want to present in this post is directed to all the leaders in KDE. This doesn't mean just the board of the e.V., by the way. The leaders in KDE are those who have volunteered to maintain packages, mentor students, moderate the mail lists and forums, become channel ops in IRC, write the promo articles, release notes and announcements, do the artwork, write the documentation, keeps the wikis accurate, helpful and free of spam, organize sprints and other meetings such as Akademy, translate our docs and internationalize our software, design and build-in accessibility, staff booths, and many other responsibilities such as serving on working groups and other committees. This is a shared responsibility we carry to one another, and what keeps our community healthy.

It is management's job to take the long view, to intervene and protect our people from their willingness to pursue excellence at all costs. Not to do so would be irresponsible.... If we are in this for the long haul, we have to take care of ourselves, support healthy habits and encourage our employees to have fullfilling lives outside of work. [p. 77] This is the major task of the e.V. and especially the Board, in my opinion, and of course the task of the CWG as well. 

Isn't this stuff great!? I'll be writing more blog posts inspired by this book as I get further into it. 

Saturday, May 10, 2014

Good Advice from Bad People: Selected Wisdom from Murderers, Stock Swindlers, and Lance Armstrong

Wow, what a book title: Good Advice from Bad People: Selected Wisdom from Murderers, Stock Swindlers, and Lance Armstrong, by Zac Bissonnette. I heard the author talk about his book on the Tavis Smiley radio show earlier, and it made me think about Jonathan Haidt's point about how people have wonderful advice for others, even when they themselves seem unable to follow it.

That got me thinking about some recent discussions, arguments and even fights in the KDE community in the past few months. Some arguments are exciting. You hear the deep thinking, the examination and presentation of fresh points of view, and hear people thinking together. This is what we want for every conversation! But sometimes instead, you hear criticism, to which the reaction is defensiveness. This is painful to watch, as both (or all) sides are injured, and their hurt is being ignored.

What makes the difference? It seems to me what is lacking in the second scenario is trust. Haidt advises asking people for their advice and judgement about you, and listening with an open mind and heart.  That is rather hard to do when it is your project that is being measured and criticized. Yet it is critical to success, because we often literally cannot see flaws in our processes and products that others can see quite clearly.

One thing that has bothered me for years in the whole FLOSS movement is the attitude towards users, as "lusers." I know that started out as a pun, but it seems to me that it correctly labels the orientation that developers often have. Good projects have people who use bug reports, critical blog posts and complaints on the lists, forums and IRC as feedback, in order to not just fix crashes, but to make their product better. Projects in trouble make it difficult to file bugs, or simply ignore them, and rather than viewing criticism as feedback, interpret it as a personal attack.

Unfortunately, I am seeing this defensive attitude far too often lately in KDE. This can happen within teams, when someone proposes a new idea, and then others shoot it down. I don't mean they dispute the idea, or propose a different alternative, but rather state the criticism in a take-no-prisoners way. I've also seen this after a release, when an aspect of the new application or feature is criticized by users. Rather than collaborating with the reporters, to make the application or feature better, the discussion is framed as a war by both sides. In other words, "KDE developers are dictators" vs. "KDE users/distributions/packagers hate progress".

Guess what? Wars aren't productive of good software, and are destructive to every combatant and even those within earshot. Fortunately, later I heard Ed Catmull, the co-founder of Pixar Animation Studios and president of Pixar and Disney animation, about managing creative people and his new book Creativity Inc: Overcoming The Unseen Forces That Stand In The Way Of True Inspiration. Catmull gives the credit for the success of Pixar to an open, nurturing work environment. I think we need to focus on this more in our community. It should be safe for anyone to talk to anybody. According to Catmull, at Pixar they assume that any movie is crap when they start out. But somewhere in the idea is some spark that can become great. He says,
I've spent nearly forty years thinking about how to help smart, ambitious people work effectively with one another. The way I see it, my job as a manager is to create a fertile environment, keep it healthy, and watch for the things that undermine it....The thesis of this book is that there are many blocks to creativity, but there are active steps we can take to protect the creative process....identifying these destructive forces isn't merely a philosophical exercise. It is a crucial, central mission.
He used a term I love, candor. He says that creating a safe space where people can fully express their thoughts and feelings is key to keeping creativity flowing. Of course I'm going to read this book! Here is the interview (11 minutes): kuow.org/post/president-pixar-and-disney-animation-fostering-creativity.

We already have the Team Health Check which can be found here: permalink.gmane.org/gmane.comp.kde.devel.plasma/19755. I'll use Catmull's book to look again at that team tool, and see if it can be improved.

For now, I hope that before any of us speaks or writes, we'll think about our choice of words. Candor is crucial. Remember though, that feedback can be framed as helpful information, or as an attack. You might mean your feedback as helpful, but can it be read as harsh criticism? If so, please edit before publishing. Developers, think about how to invite candor, by asking others for their honest feedback. Welcome reports of problems, bug reports, and respond in a collaborative way. If you need someone to triage bugs to keep sane, ask for that help! Everything you can do to lower the barriers to honest criticism, the better your work products will be.

Wednesday, April 3, 2013

Progress? It depends on your perspective

I had a disturbing discussion with a family member recently. There were no arguments over facts; we agree on the facts underlaying our discussion. Yet I was shocked at how discouraged he was by the state of the world, and the prospects for progress. No matter what examples I raised, he had more examples which convince him that we're moving backwards. Neither of us managed to convince the other to change their mind. That part wasn't unusual! But I'm unused to encountering this negative view of the universe. I live in the US, and I know that our politics is full of fail!

In the FOSS community, I rarely come across this depressed perspective. In fact, quite the opposite. So I've been thinking about why this is. Perhaps it is because we are involved in changing the world! After all, we aren't just building and distributing free software; we're showing the world that freedom and friendship work. We constantly demonstrate that we can cooperate; with team members, with up and downstreams, with for-profit companies and with non-profit groups, with government and educational groups, and on and on.

We promote freedom, we promote equality, we promote quality. We constantly develop new friendships, we pay attention to our users, and those users help us help them by filing bug reports, cooperating with quality initiatives, by testing, by donating money. We learn to promote our projects, learn to give talks, speeches and reports, learn to build websites, write documentation, learn to communicate in multiple venues, and even learn to recognize bad behavior by friends and team members, or maybe even burnout in our own lives. And of course, we learn what to do in those tough situations, along with dealing with bugs in our software, crochety hardware and processes, or outdated techniques.

I've been reading a book about increasing brain fitness, (bad title warning): Make Your Brain Smarter, by Sandra Bond Chapman which might shed some light. In the section about innovation and creativity, she says you:
incite innovation ... when you: ... broaden and revamp your perspectives... by reading different types of books, exposing yourself to different types of people.... Dismantle old linkages of information to allow new thoughts to brew, ponder free-flowing ideas, consciously ... convert ideas into deliberate change [and] reflect and learn from mistakes -- quickly. [p. 115]
This is what I see in Linuxchix, in the KDE and Kubuntu teams I work in, and on the lists, forums, planets, and in IRC. I hear new perspectives, hear about books, hear from new people, and different people, see new ideas, and old ideas blown up, and see how immediate feedback improves quality fast. Every day!

I think these experiences explain the difference between hope and despair between my family member and me. Not only do I see many groups in my country and around the world who are making a difference, I'm part of a great movement which is improving the world. Whether or not this is the "year of the linux desktop," we are making great software, software which we use, software we are proud to share with the world. We're not only having fun doing it; we're part of how you make the world a better place.

PS: We're getting smarter and healthier as we do so, I hope. By the way, I'm encouraging my family member to get involved in our projects. Here's hoping.