Collaborative Team Quotes

To collaborative team members, completing one another is more important than competing with one another.

If you first take a minute, an hour or a month to let go of feeling annoyed, frustrated or critical of the person or situation that may be driving you crazy, you set yourself up for much greater leadership and personal success.

People are more likely to remember the great social interaction they had with a colleague than the great meeting they both attended.

I’d collaborate with my clones, because I’m a team player who wants all the credit.

As a leader, it's your job to get everyone to share what they know.

Collaboration allows teachers to capture each other's fund of collective intelligence.

Being the only woman on a nontechnical team, providing customer support to software developers, was like immersion therapy for internalized misogyny. I liked men—I had a brother. I had a boyfriend. But men were everywhere: the customers, my teammates, my boss, his boss. I was always fixing things for them, tiptoeing around their vanities, cheering them up. Affirming, dodging, confiding, collaborating. Advocating for their career advancement; ordering them pizza. My job had placed me, a self-identified feminist, in a position of ceaseless, professionalized deference to the male ego.

Central to the performance of any team is accountability to the people and to itself, for the course to which the team is responsible.

Synergy without strategy results to waste of energy.

Because meetings involve people, things can and will go wrong. Provide first aid when necessary.

First and foremost is that creativity is a collaborative process. Innovation comes from teams more often than from the lightbulb moments of lone geniuses. This was true of every era of creative ferment. The Scientific Revolution, the Enlightenment, and the Industrial Revolution all had their institutions for collaborative work and their networks for sharing ideas.

Genius starts individual brilliance. It requires singular vision. But executing it often entails working with others. Innovation is a team sport. Creativity is a collaborative endeavor.

Team Topologies provides four fundamental team types—stream-aligned, platform, enabling, and complicated-subsystem—and three core team interaction modes—collaboration, X-as-a-Service, and facilitating.

The same bias contributes to the common observation that many members of a collaborative team feel they have done more than their share and also feel that the others are not adequately grateful for their individual contributions.

Why three days? Because that’s the minim amount of time to reset a metabolic hormone. When you disrupt these seven hormones in three-day bursts, it takes you a total of twenty-one days to recreate a collaborative team of your metabolic hormones.

The key venue for freewheeling discourse was the Monday morning executive team gathering, which started at 9 and went for three or four hours. The focus was always on the future: What should each product do next? What new things should be developed? Jobs used the meeting to enforce a sense of shared mission at Apple. This served to centralize control, which made the company seem as tightly integrated as a good Apple product, and prevented the struggles between divisions that plagued decentralized companies.

Arbogast had then assembled a dream team of creative consultants and contractors to help make his bold claim a reality, luring some of the videogame industry’s brightest stars away from their own companies and projects, with the sole promise of collaborating on his groundbreaking new MMOs. That was how gaming legends like Chris Roberts, Richard Garriott, Hidetaka Miyazaki, Gabe Newell, and Shigeru Miyamoto had all wound up as consultants on both Terra Firma and Armada—along with several big Hollywood filmmakers, including James Cameron, who had contributed to the EDA’s realistic ship and mech designs, and Peter Jackson, whose Weta Workshop had rendered all of the in-game cinematics.

Color blindness has become a powerful weapon against progress for people of color, but as a denial mindset, it doesn’t do white people any favors, either. A person who avoids the realities of racism doesn’t build the crucial muscles for navigating cross-cultural tensions or recovering with grace from missteps. That person is less likely to listen deeply to unexpected ideas expressed by people from other cultures or to do the research on her own to learn about her blind spots. When that person then faces the inevitable uncomfortable racial reality—an offended co-worker, a presentation about racial disparity at a PTA meeting, her inadvertent use of a stereotype—she’s caught flat-footed. Denial leaves people ill-prepared to function or thrive in a diverse society. It makes people less effective at collaborating with colleagues, coaching kids’ sports teams, advocating for their neighborhoods, even chatting with acquaintances at social events.

The key to innovation—at Bell Labs and in the digital age in general—was realizing that there was no conflict between nurturing individual geniuses and promoting collaborative teamwork. It was not either-or. Indeed, throughout the digital age, the two approaches went together. Creative geniuses (John Mauchly, William Shockley, Steve Jobs) generated innovative ideas. Practical engineers (Presper Eckert, Walter Brattain, Steve Wozniak) partnered closely with them to turn concepts into contraptions. And collaborative teams of technicians and entrepreneurs worked to turn the invention into a practical product. When part of this ecosystem was lacking, such as for John Atanasoff at Iowa State or Charles Babbage in the shed behind his London home, great concepts ended up being consigned to history’s basement. And when great teams lacked passionate visionaries, such as Penn after Mauchly and Eckert left, Princeton after von Neumann, or Bell Labs after Shockley, innovation slowly withered.

The key insight behind Radical Candor is that command and control can hinder innovation and harm a team’s ability to improve the efficiency of routine work. Bosses and companies get better results when they voluntarily lay down unilateral power and encourage their teams and peers to hold them accountable, when they quit trying to control employees and focus instead on encouraging agency. The idea is that collaboration and innovation flourish when human relationships replace bullying and bureaucracy.

A strategy is multi-dimensional planning, multi-team collaboration, and multitasking action.

Lean UX advocates a team-based mentality. Rockstars, gurus, ninjas, and other elite experts of their craft break down team cohesion and eschew collaboration.

If you want to go fast, go alone. If you want to go far, go together. African Proverb

An individual can make a change but a team can make a revolution.

Uncertainty is where new value is created. Everything you want in life is on the other side of all your excuses for not trying.

Teamwork is not a game for the selfish. It is for those with the mindset that a win for one is a win for all.

To be full of love and enthusiasm for your work is a prerequisite for collaboration, a professional obligation;

High Performance Teams create cultures of caring, connection, commitment, collaboration and clear consistent communication

Intrinsically we humans want to be happy, and happiness derives from having purpose, pursuit towards interesting and challenging ‘something’ that is greater than oneself.

Collaboration begins with focusing on the collective good rather than personal gain.

It’s also a narrative of how they collaborated and why their ability to work as teams made them even more creative.

Replace cyber-bullying with cyber-believing. Let us build eachother up instead of bringing others down. BELIEVE & BUILD

This book is about the difference between a self-focused inward mindset and an others-inclusive outward mindset. It will help you become more outward in your work, your leadership, and your life. It will guide you in building more innovative and collaborative teams and organizations. And it will help you see why you like many of the people you do and what you can do to become more like them.

In professional networks that acted as fertile soil for successful groups, individuals moved easily among teams, crossing organizational and disciplinary boundaries and finding new collaborators. Networks that spawned unsuccessful teams, conversely, were broken into small, isolated clusters in which the same people collaborated over and over. Efficient and comfortable, perhaps, but apparently not a creative engine.

A maxim in the theater tells us this: On time is already late (Devin 2009). That is, if we arrive at work on time with our bodies only, having not groomed our minds to collaborate, we are simply late. Unprepared.

To figure out what students were carrying with them from kindergarten into adulthood, Chetty’s team turned to another possible explanation. In fourth and eighth grade, the students were rated by their teachers on some other qualities. Here’s a sample: Proactive: How often did they take initiative to ask questions, volunteer answers, seek information from books, and engage the teacher to learn outside class? Prosocial: How well did they get along and collaborate with peers? Disciplined: How effectively did they pay attention—and resist the impulse to disrupt the class? Determined: How consistently did they take on challenging problems, do more than the assigned work, and persist in the face of obstacles? When students were taught by more experienced kindergarten teachers, their fourth-grade teachers rated them higher on all four of these attributes. So did their eighth-grade teachers. The capacities to be proactive, prosocial, disciplined, and determined stayed with students longer—and ultimately proved more powerful—than early math and reading skills.

The way forward, I’m suggesting, is not to stop collaborating face-to-face, but to refine the way we do it. For one thing, we should actively seek out symbiotic introvert-extrovert relationships, in which leadership and other tasks are divided according to people’s natural strengths and temperaments. The most effective teams are composed of a healthy mix of introverts and extroverts, studies show, and so are many leadership structures.

His goal was to be vigilant against " the bozo explosion" that leads to a company's being larded with second rate talent: For most things in life, the range between best and average is 30% or so. The best airplane flight, the best meal, they may be 30% better than your average one. What I saw with Woz was somebody who was fifty times better than the average engineer. He could have meetings in his head. The Mac team was an attempt to build a whole team like that, A players. People said they wouldn't get along, they'd hate working with each other. But I realized that A players like to work with A players, they just didn't like working with C players. At Pixar, it was a whole company of A players. When I got back to Apple, that's what I decided to try to do. You need to have a collaborative hiring process. When we hire someone, even if they're going to be in marketing, I will have them talk to the design folks and the engineers. My role model was J. Robert Oppenheimer. I read about the type of people he sought for the atom bomb project. I wasn't nearly as good as he was, but that's what I aspired to do.

in the scramble to survive, founders often hire to solve immediate needs and simultaneously create long-term problems. This mistake is common enough that Bob Sutton wrote a book, The No-Asshole Rule, to help executives recognize the damage these hires cause to culture.5 No matter how many golden lectures a leader gives imploring people to “Be collaborative” or “Work as a team,” if the people hired have destructive habits, the lecture will lose.

Design thinking has been associated with massive team collaboration, which in turn, fosters employee engagement and maximizes productivity. Hence, it is a tool that should be emulated and implemented for the success of any business.

I began looking for these four: Smart. It doesn’t mean high IQ (although that’s great), it means disposed toward learning. If there’s a best practice anywhere, adopt it. We want to turn as much as possible into a routine so we can focus on the few things that require human intelligence and creativity. A good interview question for this is: “Tell me about the last significant thing you learned about how to do your job better.” Or you might ask a candidate: “What’s something that you’ve automated? What’s a process you’ve had to tear down at a company?” Humble. I don’t mean meek or unambitious, I mean being humble in the way that Steph Curry is humble. If you’re humble, people want you to succeed. If you’re selfish, they want you to fail. It also gives you the capacity for self-awareness, so you can actually learn and be smart. Humility is foundational like that. It is also essential for the kind of collaboration we want at Slack. Hardworking. It does not mean long hours. You can go home and take care of your family, but when you’re here, you’re disciplined, professional, and focused. You should also be competitive, determined, resourceful, resilient, and gritty. Take this job as an opportunity to do the best work of your life. Collaborative. It’s not submissive, not deferential—in fact it’s kind of the opposite. In our culture, being collaborative means providing leadership from everywhere. I’m taking responsibility for the health of this meeting. If there’s a lack of trust, I’m going to address that. If the goals are unclear, I’m going to deal with that. We’re all interested in getting better and everyone should take responsibility for that. If everyone’s collaborative in that sense, the responsibility for team performance is shared. Collaborative people know that success is limited by the worst performers, so they are either going to elevate them or have a serious conversation. This one is easy to corroborate with references, and in an interview you can ask, “Tell me about a situation in your last company where something was substandard and you helped to fix it.

Programming is the immediate act of producing code. Software engineering is the set of policies, practices, and tools that are necessary to make that code useful for as long as it needs to be used and allowing collaboration across a team.

McKusick's belief in this paradigm-the focus on disability rather than abnormalcy-was actualized in the treatment of patients in his clinic. Patients with dwarfism, for instance, were treated by an interdisciplinary team of genetic counselors, neurologists, orthopedic surgeons, nurses, and psychiatrists trained to focus on specific disabilities of persons with short stature. Surgical interventions were reserved to correct specific deformities as they arose. The goal was not to restore "normalcy"-but vitality, joy, and function. McKusic had rediscovered the founding principles of modern genetics in the realm of human pathology. In humans as in wild flies, genetic variations abounded. Here too genetic variants, environments, and gene-environment interactions ultimately collaborated to cause phenotypes-except in this case, the "phenotype" in question was disease. Here too some genes had partial penetrance and widely variable expressivity. One gene could cause many diseases, and one disease could be caused by many genes. And here too "fitness" could not be judged in absolutes. Rather the lack of fitness-illness [italicized, sic] in colloquial terms- was defined by the relative mismatch between an organism and environment.

Instead he had a trait that was just as useful in promoting collaborative creativity and managing a team: he was decisive. More important, his decisiveness was based not on emotion or personal favoritism but rather on a rational and precise analysis of options.

at Microsoft, we concluded that success has always required that people master four skills: learning about new topics and fields; analyzing and solving new problems; communicating ideas and sharing information with others; and collaborating effectively as part of a team.

Change before you have to.—Jack Welch Wisdom is the reward for a lifetime of listening when you would have preferred to talk.—Doug Larson Communication creates collaboration. Big ears are better than big egos. When you’re not listening, ask good questions.—Bill Walsh The

Leaders with high emotional intelligence create a culture of trust, respect, and collaboration, where everyone feels valued and heard. They build teams that are not just efficient, but also empowered and fulfilled. Emotional intelligence is not just a nice-to-have for leaders, it's a must-have.

One of the best-known studies of availability suggests that awareness of your own biases can contribute to peace in marriages, and probably in other joint projects. In a famous study, spouses were asked, “How large was your personal contribution to keeping the place tidy, in percentages?” They also answered similar questions about “taking out the garbage,” “initiating social engagements,” etc. Would the self-estimated contributions add up to 100%, or more, or less? As expected, the self-assessed contributions added up to more than 100%. The explanation is a simple availability bias: both spouses remember their own individual efforts and contributions much more clearly than those of the other, and the difference in availability leads to a difference in judged frequency. The bias is not necessarily self-serving: spouses also overestimated their contribution to causing quarrels, although to a smaller contribution to causing quarrels, although to a smaller extent than their contributions to more desirable outcomes. The same bias contributes to the common observation that many members of a collaborative team feel they have done more than their share and also feel that the others are not adequately grateful for their individual contributions

Only experience can refine a leader's art. High-uncertainty projects are full of anxiety, change, and ambiguity that the team must deal with. It takes a different style of project management, a different pattern of team operation, and a different type of project leader. I've labeled this type of management leadership-collaboration.

We wanted to get rid of anything other than what was absolutely essential,” he said. “To do so required total collaboration between the designers, the product developers, the engineers, and the manufacturing team. We kept going back to the beginning, again and again. Do we need that part? Can we get it to perform the function of the other four parts?

Every change that is made to an application’s configuration, source code, environment, or data, triggers the creation of a new instance of the pipeline. One of the first steps in the pipeline is to create binaries and installers. The rest of the pipeline runs a series of tests on the binaries to prove that they can be released. Each test that the release candidate passes gives us more confidence that this particular combination of binary code, configuration information, environment, and data will work. If the release candidate passes all the tests, it can be released. The deployment pipeline has its foundations in the process of continuous integration and is in essence the principle of continuous integration taken to its logical conclusion. The aim of the deployment pipeline is threefold. First, it makes every part of the process of building, deploying, testing, and releasing software visible to everybody involved, aiding collaboration. Second, it improves feedback so that problems are identified, and so resolved, as early in the process as possible. Finally, it enables teams to deploy and release any version of their software to any environment at will through a fully automated process.

The capability of self-organizing teams lies in collaboration. When two engineers scratch out a design on a whiteboard, they are collaborating. When team members meet to brainstorm a design, they are collaborating. When team leaders meet to decide whether a product is ready to ship, they are collaborating. The result of any collaboration can be categorized as a tangible deliverable, a decision, or shared knowledge.

launch the team well, and only then to help members take the greatest possible advantage of their favorable performance circumstances. Indeed, my best estimate is that 60 percent of the variation in team effectiveness depends on the degree to which the six enabling conditions are in place, 30 percent on the quality of a team’s launch, and just 10 percent on the leader’s hands-on, real-time coaching (see the “60-30-10 rule” in Chapter 10).

The transformation of a business-as-usual culture into one focused on innovation and driven by design involves activities, decisions, and attitudes. Workshops help expose people to design thinking as a new approach. Pilot projects help market the benefits of design thinking within the organization. Leadership focuses the program of change and gives people permission to learn and experiment. Assembling interdisciplinary teams ensures that the effort is broadly based. Dedicated spaces such as the P&G Innovation Gym provide a resource for longer-term thinking and ensure that the effort will be sustained. Measurement of impacts, both quantitative and qualitative, helps make the business case and ensures that resources are appropriately allocated. It may make sense to establish incentives for business units to collaborate in new ways so that younger talent sees innovation as a path to success rather than as a career risk.

The key to innovation-at Bell Labs and in the digital age in general-was realizing that there was no conflict between nurturing individual geniuses and promoting collaborative teamwork. It was not either-or. Indeed, throughout the digital age, the two approaches went together. Creative geniuses (John Mauchly, William Shockley, Steve Jobs) generated innovative ideas. Practical engineers (Presper Eckert, Walter Brattain, Steve Wozniak) partnered closely with them to turn concepts into contraptions. And collaborative teams of technicians and entrepreneurs worked to turn the invention into a practical product. When part of this ecosystem was lacking, such as for John Atanasoff at Iowa State or Charles Babbage in the shed behind his London home, great concepts ended up being consigned to history's basement. And when great teams lacked passionate visionaries, such as Penn after Mauchly and Eckert left, Princeton after von Neumann, or Bell Labs after Shockley, innovation slowly withered.

In a famous study, spouses were asked, “How large was your personal contribution to keeping the place tidy, in percentages?” They also answered similar questions about “taking out the garbage,” “initiating social engagements,” etc. Would the self-estimated contributions add up to 100%, or more, or less? As expected, the self-assessed contributions added up to more than 100%. The explanation is a simple availability bias: both spouses remember their own individual efforts and contributions much more clearly than those of the other, and the difference in availability leads to a difference in judged frequency. The bias is not necessarily self-serving: spouses also overestimated their contribution to causing quarrels, although to a smaller extent than their contributions to more desirable outcomes. The same bias contributes to the common observation that many members of a collaborative team feel they have done more than their share and also feel that the others are not adequately grateful for their individual contributions.

Synergy refers to the interaction of elements that when combined produce a total effect that is greater than the sum of the individual elements. In the context of your business, consider how a team can put forth a collaborative effort that exceeds an individual’s output. Now on task, you may begin to share the key parts of your plan with the pillars of your business or family. Embrace the opportunity and be enthusiastic as you are assigning responsibilities. Everyone needs to have a “paddle in the canoe” and work in synchronicity to achieve the desired outcome.

raving maniacs, half paralysed with hunger and fear’. In collaboration with an UNRRA team, the soldiers took over a former Napola School at Feldafing, drafted many of its German staff, including cooks and medical personnel, and turned it into a refugee camp, with a nearby hotel requisitioned as hospital accommodation. The number of inmates rapidly grew to some 4,000. By the end of May 1945, the camp had experienced its first survivor wedding and those in the hospital – now moved to a former monastery – had been treated to a concert by the Kovno Ghetto orchestra, dressed in their striped concentration-camp pyjamas.

Spacewar highlighted three aspects of the hacker culture that became themes of the digital age. First, it was created collaboratively. “We were able to build it together, working as a team, which is how we liked to do things,” Russell said. Second, it was free and open-source software. “People asked for copies of the source code, and of course we gave them out.” Of course—that was in a time and place when software yearned to be free. Third, it was based on the belief that computers should be personal and interactive. “It allowed us to get our hands on a computer and make it respond to us in real time,” said Russell.10

A lot of the credit, too, should go to Turing, for developing the concept of a universal computer and then being part of a hands-on team at Bletchley Park. How you rank the historic contributions of the others depends partly on the criteria you value. If you are enticed by the romance of lone inventors and care less about who most influenced the progress of the field, you might put Atanasoff and Zuse high. But the main lesson to draw from the birth of computers is that innovation is usually a group effort, involving collaboration between visionaries and engineers, and that creativity comes from drawing on many sources.

Idea in Brief Are you an ethical manager? Most would probably say, “Of course!” The truth is, most of us are not. Most of us believe that we’re ethical and unbiased. We assume that we objectively size up job candidates or venture deals and reach fair and rational conclusions that are in our organization’s best interests. But the truth is, we harbor many unconscious—and unethical—biases that derail our decisions and undermine our work as managers. Hidden biases prevent us from recognizing high-potential workers and retaining talented managers. They stop us from collaborating effectively with partners. They erode our teams’ performance. They can also lead to costly lawsuits.

Using velocity as a productivity metric has several flaws. First, velocity is a relative and team-dependent measure, not an absolute one. Teams usually have significantly different contexts which render their velocities incommensurable. Second, when velocity is used as a productivity measure, teams inevitably work to game their velocity. They inflate their estimates and focus on completing as many stories as possible at the expense of collaboration with other teams (which might decrease their velocity and increase the other team’s velocity, making them look bad). Not only does this destroy the utility of velocity for its intended purpose, it also inhibits collaboration between teams.

I've always believed that culture is defined and created from the top down, but it comes to life from the bottom up. This meant that I had to build our culture by working with the leadership group (i.e., the owner, general manager, and executives), the coaching staff, and the football team. To strengthen the culture among the leadership group, it was important to reiterate to the owner, team president, and general manager the shared beliefs, values, and expectations that we had discussed in depth when I was interviewing for the head coaching position. It was important to have collaborative conversations on a regular basis to discuss the changes we were making and why we were making them.

then “man-computer symbiosis,” as Licklider called it, will remain triumphant. Artificial intelligence need not be the holy grail of computing. The goal instead could be to find ways to optimize the collaboration between human and machine capabilities—to forge a partnership in which we let the machines do what they do best, and they let us do what we do best. SOME LESSONS FROM THE JOURNEY Like all historical narratives, the story of the innovations that created the digital age has many strands. So what lessons, in addition to the power of human-machine symbiosis just discussed, might be drawn from the tale? First and foremost is that creativity is a collaborative process. Innovation comes from teams more often than from the lightbulb moments of lone geniuses.

Improve performance through process improvements introduced with minimal resistance. Deliver with high quality. Deliver a predictable lead time by controlling the quantity of work-in-progress. Give team members a better life through an improved work/life balance. Provide slack in the system by balancing demand against throughput. Provide a simple prioritization mechanism that delays commitment and keeps options open. Provide a transparent scheme for seeing improvement opportunities, thereby enabling change to a more collaborative culture that encourages continuous improvement. Strive for a process that enables predictable results, business agility, good governance, and the development of what the Software Engineering Institute calls a high-maturity organization.

There are other star players in the field of gene editing. Most of them deserve to be the focus of biographies or perhaps even movies. (The elevator pitch: A Beautiful Mind meets Jurassic Park.) They play important roles in this book, because I want to show that science is a team sport. But I also want to show the impact that a persistent, sharply inquisitive, stubborn, and edgily competitive player can have. With a smile that sometimes (but not always) masks the wariness in her eyes, Jennifer Doudna turned out to be a great central character. She has the instincts to be collaborative, as any scientist must, but ingrained in her character is a competitive streak, which most great innovators have. With her emotions usually carefully controlled, she wears her star status lightly.

Values constitute your personal “bottom line.” They serve as guides to action. They inform the priorities you set and the decisions you make. They tell you when to say yes and when to say no. They also help you explain the choices you make and why you made them. If you believe, for instance, that diversity enriches innovation and service, then you should know what to do if people with differing views keep getting cut off when they offer fresh ideas. If you value collaboration over individualistic achievement, then you’ll know what to do when your best salesperson skips team meetings and refuses to share information with colleagues. If you value independence and initiative over conformity and obedience, you’ll be more likely to challenge something your manager says if you think it’s wrong.

My studio team and I approached the creation of this series with enthusiasm, wit, sincerity and sometimes more than a dash of humour. Is the result just another foray into the clichés of Orientalism? I think not. For the most part the people photographed became co-conspirators in our elaborate game of recreating reality. They enjoyed chai with us and a morning samosa (we most always shoot in the early morning since it is the best time to utilize available light). Our models were indeed “posed and paid”, but they cooperated by suggesting so many things themselves… eagerly grasping the process we were undertaking and joining in the creation of what generally became more than just a photo shoot. Each session in the studio became an “event”…an episode of manufactured expression in which all participated and all remembered.

an important point, throughout this book, whenever I describe work done by Jane Doe or Joe Smith, I actually mean “work done by Doe and a team of her postdocs, technicians, grad students, and collaborators spread far and wide over the years.” I’ll be referring solely to Doe or Smith for brevity, not to imply that they did all the work on their own—science is utterly a team process. In addition, as long as we’re at it, another point: At endless junctures throughout the book, I’ll be reporting the results of a study, along the lines of, “And when you do whatever to this or that brain region/neurotransmitter/hormone/gene/etc., X happens.” What I mean is that on the average X happens, and at a statistically reliable rate. There is always lots of variability, including individuals in whom nothing happens or even the opposite of X occurs.

It truly is a team sport, and we have the best team in town. But it’s my relationship with Ilana that I cherish most. We have such a strong partnership and have learned how we work most efficiently: I need coffee, she needs tea. When we’re stressed, I pace around and use a weird neck massager I bought online that everyone makes fun of me for, and she knits. When we’re writing together she types, because she’s faster and better at grammar. We actually FaceTime when we’re not in the same city and are constantly texting each other ideas for jokes or observations to potentially use (I recently texted her from Asheville: girl with flip-flops tucked into one strap of tank top). Looking back now at over ten years of doing comedy and running a business with her I can see how our collaboration has expanded and contracted. But it’s the problem-solving aspect of this industry, the producing, the strategy, the realizing that we could put our heads together and figure out the best solution, that has made our relationship and friendship what it is. Because that spills into everything. We both have individual careers now, but those other projects have only been motivating and inspiring to each other and the show. We bring back what we’ve learned on the other sets, in the other negotiations, in the other writers’ rooms or press situations. I’m very lucky to have jumped into this with Ilana Rose Glazer, the ballsy, curly-haired, openhearted, nineteen-year-old girl that cracked me up that night at the corner of the bar at McManus. So many wonderful things have happened since we began working together, but there are a lot of confusing, life-altering things in there too, and it’s such a relief to have someone who completely understands the good and the bad.

For most things in life, the range between best and average is 30% or so. The best airplane flight, the best meal, they may be 30% better than your average one. What I saw with Woz was somebody who was fifty times better than the average engineer. He could have meetings in his head. The Mac team was an attempt to build a whole team like that, A players. People said they wouldn’t get along, they’d hate working with each other. But I realized that A players like to work with A players, they just didn’t like working with C players. At Pixar, it was a whole company of A players. When I got back to Apple, that’s what I decided to try to do. You need to have a collaborative hiring process. When we hire someone, even if they’re going to be in marketing, I will have them talk to the design folks and the engineers. My role model was J. Robert Oppenheimer. I read about the type of people he sought for the atom bomb project. I wasn’t nearly as good as he was, but that’s what I aspired to do.

Dostum offered this exoneration as evidence of his loyalty to the Americans. But his conviction that the Americans were by his side during the incident raised another set of difficult questions about whether the Special Forces and CIA personnel witnessed any of the communications between Dostum and his commanders about the murders, and failed to either stop them, or report them after the fact. Nutsch told me he knew of no abuses. “My team has been investigated multiple times over this,” he said. “We did not witness, nor observe, anything.” Just as Dostum considered the American special forces blood brothers, the camaraderie was apparent on Nutsch’s side. “I saw him as a charismatic leader. Led from the front. Took care of his guys,” he added. In a celebratory Hollywood rendition of 595’s collaboration with Dostum called 12 Strong, Nutsch was portrayed, with exaggerated brawn and smolder, by Chris Hemsworth, the actor who played the superhero Thor. Nutsch grew testy when I asked a series of questions about the more complicated realities of the story. “Dostum’s enemies are the ones accusing him of these things,” he said. When I told him Dostum had admitted the killings may have occurred, and suggested two of his commanders may have been involved, Nutsch paused, then replied, “I don’t have a reaction to that.

When that happens, when you make 'eye contact', it kills you. It kills you and it kills anybody who thinks like you. Physical distance doesn't matter, it's about mental proximity. Anybody with the same ideas, anybody in the same head space. It kills your collaborators, your whole research team. It kills your parents; it kills your children. You become absent humans, human-shaped shells surrounding holes in reality. And when it's done, your project is a hole in the ground, and nobody knows what SCP-3125 is anymore. It is a black hole in antimemetic science, consuming unwary researchers and yielding no information, only detectable through indirect observation. A true description of what SCP-3125 is, or even an allusion to what it is, constitutes a containment breach and a lethal indirect cognitohazard. Do you see? It's a defense mechanism. This information-swallowing behaviour is just the outer layer, the poison coating. It protects the entity from discovery while it infests our reality. And as years pass, the manifestations will continue, growing denser and knitting together… until the whole world is drowning in them, and everybody will be screaming 'Why did nobody realise what was happening?' And nobody will answer, because everybody who realised was killed, by this system… Do you see it, Marion? See it now.

These include: 1.Do the Right Thing—the principle of integrity. We see in George Marshall the endless determination to tell the truth and never to curry favor by thought, word, or deed. Every one of General Marshall’s actions was grounded in the highest sense of integrity, honesty, and fair play. 2.Master the Situation—the principle of action. Here we see the classic “know your stuff and take appropriate action” principle of leadership coupled with a determination to drive events and not be driven by them. Marshall knew that given the enormous challenges of World War II followed by the turbulent postwar era, action would be the heart of his remit. And he was right. 3.Serve the Greater Good—the principle of selflessness. In George Marshall we see a leader who always asked himself, “What is the morally correct course of action that does the greatest good for the greatest number?” as opposed to the careerist leader who asks “What’s in it for me?” and shades recommendations in a way that creates self-benefit. 4.Speak Your Mind—the principle of candor. Always happiest when speaking simple truth to power, General and Secretary Marshall never sugarcoated the message to the global leaders he served so well. 5.Lay the Groundwork—the principle of preparation. As is often said at the nation’s service academies, know the six Ps: Prior Preparation Prevents Particularly Poor Performance. 6.Share Knowledge—the principle of learning and teaching. Like Larry Bird on a basketball court, George Marshall made everyone on his team look better by collaborating and sharing information. 7.Choose and Reward the Right People—the principle of fairness. Unbiased, color- and religion-blind, George Marshall simply picked the very best people. 8.Focus on the Big Picture—the principle of vision. Marshall always kept himself at the strategic level, content to delegate to subordinates when necessary. 9.Support the Troops—the principle of caring. Deeply involved in ensuring that the men and women under his command prospered, General and Secretary Marshall taught that if we are loyal down the chain of command, that loyalty will be repaid not only in kind but in operational outcomes as well.

Even though the Internet provided a tool for virtual and distant collaborations, another lesson of digital-age innovation is that, now as in the past, physical proximity is beneficial. There is something special, as evidenced at Bell Labs, about meetings in the flesh, which cannot be replicated digitally. The founders of Intel created a sprawling, team-oriented open workspace where employees from Noyce on down all rubbed against one another. It was a model that became common in Silicon Valley. Predictions that digital tools would allow workers to telecommute were never fully realized. One of Marissa Mayer’s first acts as CEO of Yahoo! was to discourage the practice of working from home, rightly pointing out that “people are more collaborative and innovative when they’re together.” When Steve Jobs designed a new headquarters for Pixar, he obsessed over ways to structure the atrium, and even where to locate the bathrooms, so that serendipitous personal encounters would occur. Among his last creations was the plan for Apple’s new signature headquarters, a circle with rings of open workspaces surrounding a central courtyard. Throughout history the best leadership has come from teams that combined people with complementary styles. That was the case with the founding of the United States. The leaders included an icon of rectitude, George Washington; brilliant thinkers such as Thomas Jefferson and James Madison; men of vision and passion, including Samuel and John Adams; and a sage conciliator, Benjamin Franklin. Likewise, the founders of the ARPANET included visionaries such as Licklider, crisp decision-making engineers such as Larry Roberts, politically adroit people handlers such as Bob Taylor, and collaborative oarsmen such as Steve Crocker and Vint Cerf. Another key to fielding a great team is pairing visionaries, who can generate ideas, with operating managers, who can execute them. Visions without execution are hallucinations.31 Robert Noyce and Gordon Moore were both visionaries, which is why it was important that their first hire at Intel was Andy Grove, who knew how to impose crisp management procedures, force people to focus, and get things done. Visionaries who lack such teams around them often go down in history as merely footnotes.

recalled Stephen Crocker, a graduate student on the UCLA team who had driven up with his best friend and colleague, Vint Cerf. So they decided to meet regularly, rotating among their sites. The polite and deferential Crocker, with his big face and bigger smile, had just the right personality to be the coordinator of what became one of the digital age’s archetypical collaborative processes. Unlike Kleinrock, Crocker rarely used the pronoun I; he was more interested in distributing credit than claiming it. His sensitivity toward others gave him an intuitive feel for how to coordinate a group without trying to centralize control or authority, which was well suited to the network model they were trying to invent. Months passed, and the graduate students kept meeting and sharing ideas while they waited for some Powerful Official to descend upon them and give them marching orders. They assumed that at some point the authorities from the East Coast would appear with the rules and regulations and protocols engraved on tablets to be obeyed by the mere managers of the host computer sites. “We were nothing more than a self-appointed bunch of graduate students, and I was convinced that a corps of authority figures or grownups from Washington or Cambridge would descend at any moment and tell us what the rules were,” Crocker recalled. But this was a new age. The network was supposed to be distributed, and so was the authority over it. Its invention and rules would be user-generated. The process would be open. Though it was funded partly to facilitate military command and control, it would do so by being resistant to centralized command and control. The colonels had ceded authority to the hackers and academics. So after an especially fun gathering in Utah in early April 1967, this gaggle of graduate students, having named itself the Network Working Group, decided that it would be useful to write down some of what they had conjured up.95 And Crocker, who with his polite lack of pretense could charm a herd of hackers into consensus, was tapped for the task. He was anxious to find an approach that did not seem presumptuous. “I realized that the mere act of writing down what we were talking about could be seen as a presumption of authority and someone was going to come and yell at us—presumably some adult out of the east.

Humans are better equipped for sight than for smell. We process visual input ten times faster than olfactory. Visual and cognitive cues handily trump olfactory ones, a fact famously demonstrated in a 2001 collaboration between a sensory scientist and a team of oenologists (wine scientists) at the University of Bordeaux in Talence, France.

Manage Your Team’s Collective Time Time management is a group endeavor. The payoff goes far beyond morale and retention. ILLUSTRATION: JAMES JOYCE by Leslie Perlow | 1461 words Most professionals approach time management the wrong way. People who fall behind at work are seen to be personally failing—just as people who give up on diet or exercise plans are seen to be lacking self-control or discipline. In response, countless time management experts focus on individual habits, much as self-help coaches do. They offer advice about such things as keeping better to-do lists, not checking e-mail incessantly, and not procrastinating. Of course, we could all do a better job managing our time. But in the modern workplace, with its emphasis on connectivity and collaboration, the real problem is not how individuals manage their own time. It’s how we manage our collective time—how we work together to get the job done. Here is where the true opportunity for productivity gains lies. Nearly a decade ago I began working with a team at the Boston Consulting Group to implement what may sound like a modest innovation: persuading each member to designate and spend one weeknight out of the office and completely unplugged from work. The intervention was aimed at improving quality of life in an industry that’s notorious for long hours and a 24/7 culture. The early returns were positive; the initiative was expanded to four teams of consultants, and then to 10. The results, which I described in a 2009 HBR article, “Making Time Off Predictable—and Required,” and in a 2012 book, Sleeping with Your Smartphone , were profound. Consultants on teams with mandatory time off had higher job satisfaction and a better work/life balance, and they felt they were learning more on the job. It’s no surprise, then, that BCG has continued to expand the program: As of this spring, it has been implemented on thousands of teams in 77 offices in 40 countries. During the five years since I first reported on this work, I have introduced similar time-based interventions at a range of companies—and I have come to appreciate the true power of those interventions. They put the ownership of how a team works into the hands of team members, who are empowered and incentivized to optimize their collective time. As a result, teams collaborate better. They streamline their work. They meet deadlines. They are more productive and efficient. Teams that set a goal of structured time off—and, crucially, meet regularly to discuss how they’ll work together to ensure that every member takes it—have more open dialogue, engage in more experimentation and innovation, and ultimately function better. CREATING “ENHANCED PRODUCTIVITY” DAYS One of the insights driving this work is the realization that many teams stick to tried-and-true processes that, although familiar, are often inefficient. Even companies that create innovative products rarely innovate when it comes to process. This realization came to the fore when I studied three teams of software engineers working for the same company in different cultural contexts. The teams had the same assignments and produced the same amount of work, but they used very different methods. One, in Shenzen, had a hub-and-spokes org chart—a project manager maintained control and assigned the work. Another, in Bangalore, was self-managed and specialized, and it assigned work according to technical expertise. The third, in Budapest, had the strongest sense of being a team; its members were the most versatile and interchangeable. Although, as noted, the end products were the same, the teams’ varying approaches yielded different results. For example, the hub-and-spokes team worked fewer hours than the others, while the most versatile team had much greater flexibility and control over its schedule. The teams were completely unaware that their counterparts elsewhere in the world were managing their work differently. My research provide

Collaboration is about “team work.” It’s not a cliché, it’s a practical reality.

LEADERSHIP ABILITIES Some competencies are relevant (though not sufficient) when evaluating senior manager candidates. While each job and organization is different, the best leaders have, in some measure, eight abilities. 1 STRATEGIC ORIENTATION The capacity to engage in broad, complex analytical and conceptual thinking 2 MARKET INSIGHT A strong understanding of the market and how it affects the business 3 RESULTS ORIENTATION A commitment to demonstrably improving key business metrics 4 CUSTOMER IMPACT A passion for serving the customer 5 COLLABORATION AND INFLUENCE An ability to work effectively with peers or partners, including those not in the line of command 6 ORGANIZATIONAL DEVELOPMENT A drive to improve the company by attracting and developing top talent 7 TEAM LEADERSHIP Success in focusing, aligning, and building effective groups 8 CHANGE LEADERSHIP The capacity to transform and align an organization around a new goal You should assess these abilities through interviews and reference checks, in the same way you would evaluate potential, aiming to confirm that the candidate has displayed them in the past, under similar circumstances.

Having a team of people united by one purpose—to bring Christ to that city—is key for the emotional stability of all decision makers.

At 37signals, we’ve found that we need a good four hours of overlap to avoid collaboration delays and feel like a team.

Company Team Buildingis a tool that can help inside inspiring a team for that satisfaction associated with organizational objectives. Today?azines multi-cultural society calls for working in a harmonious relationship with assorted personas, particularly in global as well as multi-location companies. Business team building events strategies is a way by which team members tend to be met towards the requirements of the firm. They help achieve objectives together instead of working on their particular. Which are the benefits of company team building events? Team building events methods enhance conversation among co-workers. The huge benefits include improved upon morality as well as management skills, capacity to handle difficulties, and much better understanding of work environment. Additional positive aspects would be the improvements inside conversation, concentration, decision making, party problem-solving, and also reducing stress. What are the usual signs that reveal the need for team building? The common signs consist of discord or even hostility between people, elevated competitors organizations between staff, lack of function involvement, poor decision making abilities, lowered efficiency, as well as poor quality associated with customer care. Describe different methods of business team development? Company team development experts as well as person programs on ?working collaboratively? can supply different ways of business team building. An important method of business team building is actually enjoyment routines that want communication between the members. The favored activities are fly-fishing, sailing regattas, highway rallies, snow boarding, interactive workshops, polls, puzzle game titles, and so forth. Each one of these routines would help workers be competitive and hone their own side considering abilities. Just what services are offered by the team building events trainers? The majority of the coaches offer you enjoyable functions, coming from accommodation to be able to dishes and much more. The actual packages include holiday packages, rope courses, on-going business office video games, and also ice-breakers. Coaching fees would depend on location, number of downline, classes, and sophistication periods. Special discounts are available for long-term deals of course, if the quantity of associates will be higher. Name some well-known corporate team development event providers within the U.Utes. Several well-liked companies are Accel-Team, Encounter Based Studying Inc, Performance Supervision Organization, Team development Productions, The education Haven Incorporated, Enterprise Upwards, Group Contractors In addition, and Team development USA.If you want to find out more details, make sure you Clicking Here

Aldus Barnes, a structural engineer by training and member of the Advanced Geometry Unit (AGU) at Arup, has formed many successful collaborations and earned a prominent place for himself in architecture by adopting the language and skills of architects. "Talk in terms of texture and density, instead of torsion and shear. That way they don't think you are just another nerd," Barnes advises the young members of his team.

We say submarining is a team sport, but in practice it often amounts to a bunch of individuals, each working in his own shell, rather than a rich collaboration.

According to the findings, the most effective team building practices in creation of virtual networks of practice are: ‘(1) recruitment and selection; (2) training and development; (3) rewards and recognition; (4) supervisory support; (5) rules regarding knowledge disclosure; (6) time pressure; and (7) collaborative programs and projects (Jolinka and Dankbaar

In all, the American military, the C.I.A., the F.B.I. and other agencies used at least 1,000 ex-Nazis and collaborators as spies and informants after the war, according to Richard Breitman, a Holocaust scholar at American University who was on a government-appointed team that declassified war-crime records.

LEADERSHIP | Intuit’s CEO on Building a Design-Driven Company Brad Smith | 222 words Although 46 similar products were on the market when Intuit launched Quicken, in 1983, it immediately became the market leader in personal finance software and has held that position for three decades. That’s because Quicken was so well designed that using it is intuitive. But by the time Smith became CEO, in 2008, the company had become overly focused on adding incremental features that delivered ease of use but not delight. What was missing was an emotional connection with customers. He and his team set out to integrate design thinking into every part of Intuit. They changed the layout of the office, reduced the number of cubes, and added more collaboration spaces and places for impromptu work. They increased the number of designers by nearly 600% and now hold quarterly design conferences. They bring in people who have created exceptionally designed products, such as the Nest thermostat and the Kayak travel website, to share insights with Intuit employees. The company acquired one start-up, called Mint, and collaborates with another, called ZenPayroll, to improve customer experience. Although most people don’t think of financial software as a category driven by emotion or design, Smith writes, Intuit’s D4D (“design for delight”) program has paid off. For example, its SnapTax app, inspired by consumers’ migration to smartphones, led one user to write, “I want this app to have my babies.

Compared to other generations, millennials tend to be more collaborative, are accustomed to working in teams & have a passion for pressure.

the school leadership team should specifically: • Build consensus for the school’s mission of collective responsibility • Create a master schedule that provides sufficient time for team collaboration, core instruction, supplemental interventions, and intensive interventions • Coordinate schoolwide human resources to best support core instruction and interventions, including the site counselor, psychologist, speech and language pathologist, special education teacher, librarian, health services, subject specialists, instructional aides, and other classified staff • Allocate the school’s fiscal resources to best support core instruction and interventions, including school categorical funding • Assist with articulating essential learning outcomes across grade levels and subjects • Lead the school’s universal screening efforts to identify students in need of Tier 3 intensive interventions before they fail • Lead the school’s efforts at Tier 1 for schoolwide behavior expectations, including attendance policies and awards and recognitions (the team may create a separate behavior team to oversee these behavioral policies) • Ensure that all students have access to grade-level core instruction • Ensure that sufficient, effective resources are available to provide Tier 2 interventions for students in need of supplemental support in motivation, attendance, and behavior • Ensure that sufficient, effective resources are available to provide Tier 3 interventions for students in need of intensive support in the universal skills of reading, writing, number sense, English language, motivation, attendance, and behavior • Continually monitor schoolwide evidence of student learning

Collaboration by invitation rarely works. Considering that the professional learning communities process is endorsed by virtually every national teacher professional association, it is difficult to understand why a teaching professional would desire or expect the right to work in isolation. More importantly, if a teacher is allowed to opt out of team collaboration, then that teacher’s students will not benefit from the collective skills and expertise of the entire team. If the purpose of collective responsibility is to ensure that all students learn at high levels, then allowing any teacher to work in isolation would be unacceptable.

every collaborative teacher team ask and answer the following four questions: What is it we want our students to learn? How will we know if each student is learning each of the essential skills, concepts, knowledge, and dispositions that we have deemed most essential? How will we respond when some of our students do not learn? How will we enrich and extend the learning for students who are already proficient? (DuFour et al., 2010)

Collaborative teams of grade-level or course-alike teachers should discuss, debate, and dialogue about which standards are essential, using all of the resources and criteria just mentioned.

collaborative teacher teams should build assessments to assess narrow learning targets rather than the entire standard.

Collaborative teacher teams are teams of educators whose classes share essential student learning outcomes; these teachers work collaboratively to ensure that their students master these critical standards. The structure for teacher teams could include grade-level, subject/course-specific, vertical, and/or interdisciplinary teams.

A school will get much better results if it spends less time searching for the Holy Grail and more time working in collaborative teacher teams to find the most effective teaching practices for its students.

Collaborative teams of teachers need to have laser-like clarity about where they are going. They need to filter out all distractions and focus on each individual student’s mastery of what has been determined to be essential. Once developed by the team, the essential learnings should be shared with students in order to engage them in their own learning as much as possible.

True collaboration is only possible in an atmosphere of trust. And that atmosphere is always set by a leader who has earned his team members’ trust and who trusts them in return.

at Pixar, Steve couldn’t shape the culture. He wasn’t the founder, and even as owner, he could not change the company to reflect his image and sensibilities. It already had a culture. It already had a leader. Its cohesive and collaborative team knew exactly what it wanted to do.

Scrum’s team-level velocity measure is not all that meaningful outside of the context of a particular team. Managers should never attempt to compare velocities of different teams or aggregate estimates across teams. Unfortunately, we have seen team velocity used as a measure to compare productivity between teams, a task for which it is neither designed nor suited. Such an approach may lead teams to “game” the metric, and even to stop collaborating effectively with each other.