"Tell me about a time you worked with a team." It is a common interview question, one many of us have heard before. If you're like me, a flood of past teams comes cascading into your brain, some good and others not so good. There is the team where you had to the do all ...
How do great teams make history? Looking at the track records of great teams like the original Apple I team, the 1969 Miracle Mets, and NASA's Space Task Group, it's obvious they went above and beyond the average achievement level typical of a group working together. But how did they get there?
Most teams go through the storming stage in some form or another because discord is inevitable. The key value to emphasize in the team is positive intent.
A little conflict is needed to bring upfront weak spots in projects and to bring new valid arguments to the table. But constant storming leads to the destruction of productivity, projects, and ultimately, the team itself.
Welcome to the next installment of Designer Confidential: a new column sharing practical advice on solving your toughest challenges like transforming your organization, creating a better-connected workflow between designers and developers, and building a great team. Submit your questions via this form, email us at email@example.com, or tweet at us at @InVisionApp.
The foundation of a good culture is clearly stating the purpose - why something is (or isn't) taking place.
While it is important to share the importance of a project, we should not forget to identify the part is can play in our team's personal development. So, for each project, establish the main goal of the team and identify what everyone hopes to get out of the project.
Clearly defining roles & responsibilities can help foster good communication. Then people can know exactly what they are accountable for and what not. They will also be able to identify whom to ask their questions when they appear.