Teamwork – Conflict Doesn’t Have to Mean Confrontation

Teamwork – Conflict Doesn’t Have to Mean Confrontation

Royd Brayshay
15th November 2017

Home Insights Teamwork – Conflict Doesn’t Have to Mean Confrontation

Great products are built by teams not individuals and creating teams that work well together takes a lot of work and effort from everyone involved.

At the very root of every person are their core values and beliefs. It is the teams who coalesce around some of these shared values that often start to perform well. Of course, that doesn’t mean disagreement doesn’t creep in,  but with appropriate behaviour it doesn’t have to come with huge confrontation or conflict.

Adrian Frost and Ian Franklin are experts in this space and lead a discussion on the subject at Agile Yorkshire that triggered some great dialogue and learning for the group.

Share Article

Insights.

Taking a look at Dagger
Taking a look at Dagger

Solomon Hykes is probably most famous for being the founder and former CTO of Docker. Docker revolutionised the way we package, run and distribute server applications, so when Hykes starts a new venture, it's worth checking out.

Discover More
Running Terraform in a Lambda Function
Running Terraform in a Lambda Function

I recently set up a Terraform project which I wanted to run on a regular schedule. There are a number of ways to achieve this, but I decided to package the project as a Lambda function and schedule it with… 

Discover More
Setting up AWS SSO with Google Workspace
Setting up AWS SSO with Google Workspace

I recently configured Single Sign On (SSO) from our Google accounts to AWS. AWS SSO is the recommended way to configure SSO across multiple AWS accounts, yet Google is not a supported identity provider. However, this simply meant that there… 

Discover More