Google has recently released the results of years of research; that working nicer is a better way of getting along.
It may seem obvious, but the team charged with studying the secrets of successful teamwork admitted they were “dead wrong” about their assumptions.
Known as Project Aristotle, Google’s research team interviewed hundreds of employees and analysed data from 100+ teams in the company. Researchers were initially looking for a perfect combination of people to make the perfect team. However, Project Aristotle discovered they were on the wrong track. Good teamwork isn’t about putting the right people together, it’s about fostering an environment where people feel safe to interact with others.
Respect, mutual contribution, allowing people to voice their ideas and opinions, and encouraging genuine interaction were the main ingredients of a happy and productive team
These factors have been summed up as “psychological safety”. Encouraging such an environment allows people to open up and interact with each other in a more respectful way. It also allows team members to speak up, share ideas, and ask questions without concern of the embarrassment which can occur in a less welcoming environment.
After years of intensive analysis, Google discovers the key to good teamwork is being nice
While it may be tempting to adopt the latest style, there are things to consider before embracing a trend. Jumping on every device, meme or design layout can be exhausting and pointless if badly considered. Taking a step back from the bandwagons and asking a few simple questions can save you from making a change for change’s sake.
We’re all familiar with the concept of Clients from Hell, but how do you avoid being a web designer from hell? We’ve compiled some advice to bear in mind to avoid client relations going sour.
Really know what the client wants
Obviously, your client will want a website, and may have a picture in their mind of how they want their site to look. Unless you’re very lucky, chances are that your client won’t speak web developer, so it’s your job to use initial meetings to translate their ideas into practical results. These meetings also provide a good chance to sound out your client and see how your personalities and work styles fit together (more on that later). Good ways to solidify your client’s vision and your role are to consider the following:
- What does the client want the site to achieve?
- What content does the client want the site to host?
- What are the functionality requirements of the site?
- Does the client have any examples of other sites in terms of what they would like to emulate or avoid?
- What is the budget and the deadline?
Remember, there can be no mutual mind reading, so use the planning stage to foster a good working relationship and make a realistic plan. Never be afraid to ask a question or ask it again if it will make your life – and therefore the client’s experience – easier.
Continuing from last week’s article, here we finish explaining how to understand and cater for the fears and motivations of the specific stakeholder viewing your website.
If you can provide indicative costs – DO SO. Many businesses are afraid to do this as they don’t want their competitors knowing their business or to lose bargaining power with clients, but they forget that most important of all is for clients to use their services.
This article was written By David Sime – David lectures in marketing in Glasgow and has had over 15 years’ experience in the field, having owned and directed two companies, worked with national and international B2B/B2C vendors as well as working within and directing several marketing agencies.
In my experience, what business to business websites fail to do online is to understand their target market.
This is something that B2C (Business to consumer) sites do very well, but for some reason it is overlooked within the B2B market.