How do you improve collaboration when everyone is remote

How do you improve collaboration when everyone is remote

Building trust, enhancing collaboration and establishing relationships is hard enough when teams work together in a physical office. Things become more challenging when teams are distributed. This issue doesn’t sound too challenging when one team is co-located and works with other teams that are at different locations or different time zones. Actually, ever since offshoring and outsourcing became mainstream, we have learned to live with the distributed nature of work. 

When do we collaborate?

We collaborate with others to achieve something of common interest. For example, entrepreneurs may collaborate to build and launch a new product. In corporate settings, different teams collaborate to build products and to deliver valuable outcomes for their customers.

Collaboration is successful when the level of trust is high among the people who work together.

However, the question remains.
How do we build and enhance collaboration and trusted relationships among team members?

There are hundreds of methods that help us do so. But we’re not going to list all of them here. Google is good for that sort of stuff. In this post, I’ll tell you what has worked for me and then you can tell me what has worked for you. Hence, don’t forget to add comments below.

Current challenge: 

When it comes to collaboration, the current pandemic has made the situation even more challenging. How? Now not just the teams, but every single person of a team is located remotely. That brings a different dynamic to the equation when we talk about collaboration and teamwork.

I’m going to share two techniques that I’ve found useful.

The first one is personal mapping.

Enhancing collaboration using personal mapping:

When team members know more about each other than just the work stuff, the bonding improves. It mostly happens that when we sit in the vicinity of others, communication begins. The generic, “hey, how was your weekend?” often becomes the icebreaker and increases the flow of communication. And it appears to me that this improved relationship also helps us deliver better outcomes. This might just be human nature. When our ancestors worked together, they survived and grew. 

Personal mapping technique is a simple mind mapping exercise where you tell your story through visualisation. Here’s my personal map.

Personal mapping

 

How to get your team’s started with personal mapping:

A good place to start is to use the technique as an icebreaker before workshops. Or, do it when New team members join. 

I often start with asking team members what they knew about me. One they respond, I share my personal map with them. I normally include details of education, work, hobbies, family, goals and values etc. The idea is to keep the session interesting. This often helps in making team members feel safe, relaxed and engaged.

After sharing my personal map, I encourage team members to pair with someone who they don’t know much about.

Team members talking of their colleague’s personal map:

When team members know that they will be introducing their colleague to others, they listen intently and they try to understand them better. 

How to do it remotely

Easy. If you’ve created your map on your computer and if you’re using a solution liked Google Meet, Microsoft teams or Zoom, you can share your screen. If you’ve created your map on paper, you can show it on camera.

Drawbacks of personal mapping:

My observation is that introverts can find this exercise a bit awkward. Some team members also do not want to share information about themselves for personal reasons. Each person is different and it’s better to familiarise the team with this exercise beforehand and find out whether it might make someone feel uncomfortable. You can work with them to adjust the exercise for them and make them feel safe for participation.

Using collaboration game Quinks for team bonding

I came across this interactive game when one of my friends invited me to join a free session with the game’s inventor, Viren.

The game is available online as well as a physical set and that makes it easier to either do it remotely or in person.

Quinks game

How to play:

Quinks is based on experiential learning techniques in which two players ask each other questions related to specific contexts by drawing cards. One person is assigned the role of Questioner, and the other the role of Answerer. The Questioner draws a Quinks card (a question card) and combines it with a Context card to create and ask a powerful question. These cards consist of powerful questions that Viren collected through his research and experience. 

Since the game limits conversations (responses of the contextual questions) to just 3 minutes, it compels team members to pay attention, learn to express themselves in a concise way, ask good questions, empathize and engage in deeper conversations.

Outcome:

I had fun playing the game even with total strangers in public sessions. It was interesting and surprising to realise that given a context and a relevant question, how you can bond with those who you’ve never met before. This was a great way to introduce people and build relationships.

Value map for further discussions: 

The game also lets players map various values of their partners based on their conversations. Once everyone completes the game, you see the value map that represents how others have perceived you through your responses. Through this process you learn about your blind spots and improve self awareness. 

 

A good reference regarding self awareness here is Johari Window. Have a look.

Personal mapping and Quinks can possibly be combined as one big workshop. I haven’t tried that yet. You may want to do that.

If you have used other collaboration techniques that gave you good results, let me know. Actually, even if your efforts didn’t succeed, we can learn from them. Why not share them here.

References:

https://quinks.co/?variant=32701557342283

https://management30.com/practice/personal-maps/

https://en.wikipedia.org/wiki/Johari_window

 

The Curse of Knowledge bias: Why Stakeholders Don’t Understand Our Ideas

The Curse of Knowledge bias: Why Stakeholders Don’t Understand Our Ideas

I often play “tap and guess” with my son. In the game one player taps a song and the other one has to guess which song or poem it was. You can tap either a table or a box or the other player’s back or head.

If you’ve played this game, then you might have experienced that it is extremely hard to guess the song that your partner is tapping. My son always questions why I couldn’t guess the song which was so easy and obvious to guess. What he doesn’t realise is that while he is tapping, he is also singing the song in his mind. Actually, you cannot help singing or at least hearing the tune in your mind if you are the tapper. Try it, it’s really fun.

The game tap and guess

Let me be honest, I’ve had some good guesses at the songs that my son tapped. Why? Because he seems to be tapping only a few specific songs and rhymes including “Old McDonald had a farm,” (I know you’ve continued with an “E-I-E-I-O!”), “happy birthday to you..” and a couple more. However, he never ever guessed a song correctly that I tapped. Exactly like others who played this game with us.

It is very difficult to be a listener and a tapper. As a tapper you believe that what you’re tapping is obvious and it’s frustrating that your partner is unable to guess such an obvious thing. As a listener all you hear is random tapping on the table.

So why do tappers believe that what they were tapping was easy to guess? Because they already know the song. They have knowledge and they cannot imagine what it was like to not have it.

And this is where we learn about Curse of Knowledge bias.

What is Curse of Knowledge:

The curse of knowledge is a cognitive bias that occurs when an individual, communicating with other individuals, unknowingly assumes that the others have the background to understand. This bias is also called by some authors the curse of expertise, although that term is also used to refer to various other phenomena.

For example, in a classroom setting, teachers have difficulty teaching novices because they cannot put themselves in the position of the student. A brilliant professor might no longer remember the difficulties that a young student encounters when learning a new subject. This curse of knowledge also explains the danger behind thinking about student learning based on what appears best to faculty members, as opposed to what has been verified with students. – Wikipedia

(Chip and Dan Heath have explained Curse of Knowledge in their book Made to Stick through the same game but in a different context. In fact, it was this book that Made this concept popular. Their book is worth reading if you want your ideas to be more sticky.)

How does the Curse of Knowledge bias apply to our workplaces?

You might recognise the expressions below.

“It’s not that complicated, but they don’t get it. Everything I am trying to do is in their favour and will be beneficial to them, but still they are resisting it. What is wrong with these people?”

As a consultant I have heard it from people I have worked with and I often hear it from many others. Some of these people are senior management folks, others are managers, team members, people from business teams etc. Each of them have attempted to do something which was faced with resistance.

We know that change is hard. Yet sometimes we try to either push a change or hope that people will simply accept the ideas, our ideas, that will benefit them because there is merit in them.

One thing that we now know is that some of our ideas don’t get accepted because possibly we are the tappers and our audience are the listeners. What seems obvious to us, might just be random jargon to others.

What can we do about it and are there any solutions?

Dan and Chip Heath suggested two ways to beat the Curse of Knowledge in their book. One is not to learn anything. Two is take your ideas and transform them. I’d suggest that you read their book to learn more about their suggestions.

For the scope of this post, well not focused on their ideas. Instead we’ll look slightly deeper in the subject and explore what we can do.

Why don’t they get it?

There can be a number of reasons why people don’t understand your ideas. Some of them I have listed below:

  • You’re barking up the wrong tree: You haven’t clearly defined who your audience, stakeholders or customers are. Are you talking to the wrong people?

  • Your message is complex: Even though you have the right audience, your message is complex or complicated.

  • You are seen as an outsider: It is a normal tendency that we prefer listening to or paying attention to only those who we trust. In fact, a number of initiatives to improve health and well-being of communities failed because the initiatives involved external experts and volunteers. (Initial efforts to eradicate the Guinea worm disease from African countries failed because villagers often didn’t trust the experts).

  • Time crunch: Your suggestions can solve a big problem, but that might take a long time to be effective and they don’t have patience to wait that long.

  • Short term gains over long term benefits: The Stanford Marshmallows experiment suggested that there are benefits of delayed gratification. However, your customers might be focusing on the short term solution than a problem or benefit coming in long term.

What can we do?

  • Understand the context: it is vital that in order for others to understand us, we understand them and their context first. When we behave purely like tappers, we limit our ability to understand a context holistically. System mapping can help in learning about the context.

One of the aviation organisations I worked for, brought in an executive from a large financial institution to lead a transformation. This executive applied his learnings and solutions from the financial institution to this organisation. Since everything was different, from the culture, the country, the people, the processes, to the technology; the so-called tried and tested solutions that worked at the financial institution, didn’t work at the airline. There was tremendous waste of resources.

  • Don’t be an outsider: if you offer your ideas as an outsider, the chances are that they’ll not be accepted because you’re seen as an outsider and a trusted relationship is not established yet. Once you understand the context, find ways to build and establish a relationship of trust. Of course the scenario would be different if you’ve been invited to offer your opinion.

  • Find the ‘Early Adopters: (refer to Winston Royce’s Diffusion of Innovations theory). The early adopters are those who have understood your ideas and see the benefit of applying them. They’re often the opinion leaders who others not only trust, but also listen to their opinion. They have good influence over their people.

  • Avoid cookie-cutter approach: Take help from those who don’t impose an approach. While your organisation may not be unique, your context would be different than others, even though your industry or domain might be similar to others. Each organisation has its own dynamics. If you or the consultants you bring in don’t understand that specific dynamics, the solution they propose will fail.

In this post, I have discussed problems that we face at workplaces when our stakeholders or colleagues do not accept our ideas. Some of those ideas even benefit them. But they don’t understand the value of those ideas possibly because they don’t have the knowledge that we possess.. What should we do?

The text above has offered some suggestions too. These options have helped me in the past, both in dealing with my own curse of knowledge and also in having more empathy and patience while working with “listeners”.

Everyone comes from a different background. A little empathy goes a long way.

Are there other options or ideas that you have used as solutions that have opened doors for you or have solved problems for you in working with others? What are those options and what did you learn? Let me know.

How to use SIPOC for mapping Agile delivery process

How to use SIPOC for mapping Agile delivery process

There are many process mapping tools available and SIPOC is one of them that delivery leaders can use for their Agile initiatives. SIPOC traditionally has been used in Lean Six Sigma process improvement projects.

“But Lean Six Sigma isn’t Agile!”, You may exclaim.

Let’s not get into the debate of what is and what isn’t. As good Agile delivery leaders we want to have more than one tool in our toolbox and this might be one of those tools. For example, finding a right starting point for a new initiative can be hard for many delivery leaders and we could use SIPOC for that purpose. You can also use it early in the project to create alignment among your team and stakeholders.

Another important thing to remember is that we can learn tremendously from other disciplines. If you haven’t yet, then I strongly recommend that you read “Range: How Generalists Triumph in a Specialized World“.  The author, “David Epstein shows that the way to excel is by sampling widely, gaining a breadth of experiences, taking detours, experimenting relentlessly, juggling many interests – in other words, by developing range”.  (Excerpt in italics taken from the book introduction on Amazon.com).

By learning tools and techniques outside from our own craft, and sometimes outside from our profession, we learn more about ourselves.

Table of Contents: 

What is SIPOC?

Why use it?

Who should be involved in the process?

How to create it?

Benefits of using SIPOC

What is SIPOC:

Sipoc is a process mapping and definition tool. The letters stand for: Suppliers, Inputs, Process, Outputs, Customers. These are the heuristics that guide us for defining a process at the commencement of a project or an initiative. You can also use it for process improvement activities (continuous improvement must be an ongoing goal for you).

SIPOC is like a customer journey map because both define a process while keeping the customer in mind. SIPOC compels you to think through the whole journey of a product or a process, beginning from a supplier to the customer. Without thinking in terms of suppliers, their inputs to a process, the steps of your process, the outputs that your customers may get, you might miss important details.

A key difference between SIPOC and Journey mapping is that a journey map focuses entirely on a customer’s experience, while a SIPOC focuses on an end to end process. This may also appear like a drawback of SIPOC that it talks about the customer last.

Another concept that is quite close to SIPOC is Value Stream Mapping (VSM). Since VSM is a Lean concept, it is used more often by Agile teams than other concepts. However, as I previously suggested, there is nothing wrong in having another tool in your toolbox.

Why use it?

Like any other mapping tool, the strength of SIPOC lies in its visualisation and simplicity. If a process is written in a thick, multi-page document, the chances are no one would read that and the creator will not receive any feedback. Since SIPOC can be created on an online tool like Whiteboardfox, or in-person using an A3 page or using sticky notes, it is far easier to get feedback.

Another reason for starting with a SIPOC instead of jumping straight into a process mapping exercise is that it enables teams to think beyond the process. When you use it, you have very little chance of missing on high-level process steps and the scope inclusions and exclusions.

Moreover, SIPOC provides a structured and simple way to convey and brainstorm a process.

Who should be involved in the process?

Ideally, the team members that will support your initiative and work on it should be involved in the process mapping exercise. Any stakeholders that have interest in your initiative should also participate in this process. That is, you should ensure that the process does not miss inputs from key people.

How to create a SIPOC diagram?

SIPOC is an easy to use tool. It is often presented in a tabular or diagrammatic form. Your starting point is to draw five items which are Suppliers, Inputs, Process, Outputs and Customers.

Supplier: Make a list of everyone or everything that might provide an input in your process.

A supplier can be those people or groups that provide inputs into the process. For example, a supplier can be a stakeholder or a sponsor of an initiative. A supplier can also be an upstream system or a process and a customer might be a downstream process or system. Think from provider- receiver or cause-effect point of view.

Process: Begin with a starting point of a process. Your process might depend on the inputs provided by the suppliers. Once you have a starting point, describe the key steps till the end. With having clear starting and end points, it would be easier for you to complete the full chart.

Output: An output is what we produce or deliver as information, service or a product that our customer uses.

Customer: People / groups that receive and use the output of the process. A customer benefits from the process.

Benefits of using SIPOC: 

A SIPOC diagram is easier to create. It allows collaboration between various groups and helps us create a shared-understanding. Since many people provide their inputs, they also feel ownership. Of the initiative.

Some of the other benefits of SIPOC are:

– it provides a high level overview of the process

– it helps us define the stakeholders (suppliers and customers)

– it define and clarifies the scope and boundaries of a process, and most importantly

– it helps a team to understand how their process serve the customer

So, you now have another tool in your toolbox. Let me know if you find a use of this tool.

Additional Reading:

For familiarising youtrself on such topics, Wikipedia is always a good starting point. But don’t stop there. Continue exploring more if you find a topic useful.

https://en.wikipedia.org/wiki/SIPOC

SIPOC definition on ASQ

Using Kudos Cards to Recognise and Motivate Your Colleagues

Using Kudos Cards to Recognise and Motivate Your Colleagues

We’re living in a world where economy has been constantly affected due to one thing after another. There have been natural calamities such as floods, Bush fires, typhoons, earthquakes and as if those things weren’t enough, we are now dealing with a virus that doesn’t seem to stop creating havoc. 

A suffering economy means that people’s livelihoods have been affected. Mostly in an unfavourable way unfortunately. That also means that our motivations have taken a hit too.

Those who are still working might be dealing with anxiety, stress and panic and they may not even know about it. In such circumstances where people are dealing with heightened emotions, keeping their motivation high becomes difficult and even more important. 

What can we do so that we can help our colleagues, peers and friends motivated?

The Factory School of Thinking for Reward and Recognition:

Traditionally, organisations have been using monetary awards for rewarding or recognising employees. The old school thinking has been that if someone has demonstrated good behaviour, or has done some good work, offer them some money and they will be happy. The management also believed that if one person got a reward, that would motivate others as well.

Contrarily, the monetary awards often made a situation worse. That created a rift among employees. It seldom happens that everyone celebrates one person’s success. In some cases, one person’s win is also seen as everyone else’s loss.

We humans have tendencies to laugh at others’ misery. Don’t believe me? Remember the last time you laughed at someone who slipped and fell. That might even be in a TV show. Schadenfreude is a real thing unfortunately.

What Should Companies Do? 

Motivating employees and keeping their morals high is not an employers job only. Since we are all in these troubled times together, each one of us has to do our bit to improve our work practices, keep our work enjoyable and keep our colleagues in high spirits. 

How do we do that?

There is a simple and effective way of doing that and that is called Kudos cards! These are also known as Hero cards but let’s stick to ‘Kudos’.

Paraphrasing Management 3.0, Kudos cards are a written and public expression of appreciation and recognition of a team member for something that has contributed to the team.

As an employer, what you can do is either buy a deck of cards for your teams or provide them with a virtual or online version of Kudos cards. That would be a very little expense for a large gain. 

Kudos Cards: An Effective Way to Increase Intrinsic Motivation:

Jurgen Appelo is the creator of Management 3.0 methodology, which is a way of modern management thinking. This is what Management3.0 says about Kudos cards

Kudo Cards are simple cards that play the role of a physical token of appreciation. The cards can be placed in a box, and every now and then the Kudo Box is emptied and the workers celebrate those who had received a card.

Kudos cards are simple notes that focus on one and only one attribute. For example, they may show “Well Done”, “Thank You”, “Great Job”, “Congratulations”, “You’re Awesome” etc. Who wouldn’t love being recognised as a badass by their colleagues?

In their physical form, they look like this:

If you and your colleagues work remotely, consider using an online version of these cards. These cards are available for free download from the Management 3.0 website. There are several other websites that allow you to do it for free or for a small fee, for example Kudoboard (https://www.kudoboard.com/).

If you use Trello, Microsoft teams or Slack, they can also be very effective tools for Kudos.

One of my teams created a separate channel in Slack for Kudos and another one used Microsoft Teams Planner for that purpose. In fact, I found that using Slack was a fantastic idea considering that it was constantly in use. 

You can also create your own card in PowerPoint or other drawing tools. The idea is that since the receiver feels appreciated, it is highly likely that they would prefer keeping the card as a memoir. In one of my teams, we used to stick the physical cards to the wall (please see the photo). However, some people decided to take them home because they were proud of their achievements and wanted to show the cards to their friends and family. Isn’t that nice?

Why use Kudos cards: 

I have been using kudos cards for a while now and what I have experienced is that when team members do recognition of each other, the feeling is much more stronger and the positivity lasts longer. It is completely opposite to what I have observed with management rewarding employees on special occasions.

When team members recognise each other, they feel appreciated. They believe that the recognition is honest because that is based on the work or the deed they have done. It is all fact based. Another good thing about mutual recognition is that they don’t have to wait for a ceremony. There is no need for a quarterly or annual function. Employees take care of their own happiness.

Some observations about when to use Kudos Cards:

First of all a word of caution. Don’t use Kudos cards too much because then they’ll lose effectiveness. Also, you should only give a kudos card to someone who has done something right in terms of contribution and you really want to recognise their effort. These cards are for genuine and honest recognition. Without honestly they are worthless.

What I have experienced is that each team creates their own timeline, space and frequency for recognising each other’s work. 

In one of my teams, they used Scrum events like Sprint Review and retrospectives for recognising their colleagues. Another one decided to use every possible opportunity to use them. It totally depends on the team.

Luis Goncalves has written a post about how Agile teams can use the cards in Retrospectives. Read it here.

What might be useful for a team is add something about Kudos cards or regularly recognising team members in their social contract. If you do not know how to create a social contact or a working agreement, visit this page. Since teams do or should refer to their social contract frequently, that should remind them of using the cards regularly.

In conclusion, I believe that Kudos cards are a very effective way of appreciating your colleagues. These cards help improve team bonding, generate positivity, enhance collaboration and peer to peer relationship. There’s no rule for not using them for recognising your boss or an employee through them, but you’re the best judge for their usage and your context. In difficult times, we have a responsibility to support our colleagues and peers. Why not use Kudos cards for that.

If you have used Kudos cards effectively, let me know by adding a comment. 

How to create a social contract that works

How to create a social contract that works

Good Agile teams are self- organising where all ideas matter, everyone contributes and everyone is heard! 

For becoming a high-performing and self-organised team, a lot depends on how team members work together and how good of a shared understanding they share. In complex Agile working environments, it is not easy to rely only on technical skills and attention should be paid on creating cohesion. This is where social contract comes into picture.

 A social contract (also known as working agreement) allows Agile teams to define and agree on the acceptable and non-negotiable behaviours.

 In this post, we’ll look at following points:

  • What is a social contract or a working agreement?
  • Why do you need a social contract?
  • Who creates the Social contract?
  • How and when to create a Social contract? 

What is a social contract or a working agreement

A social contract is not a legally binding agreement. Instead, it’s a socially binding one. What that means is that each person in a team agrees and adheres to certain behaviours that the team mutually creates. Social contracts are unique to a team because each team has people with different personalities, idiosyncrasies and objectives.

Below is an example of a social contract: 

 You can also add other, more specific topics in your social contract. One of our contracts included these:

  • No open laptops in meetings
  • Meetings are not scheduled between 3-5 PM
  • No mobile phone in meetings or team discussions
  • Update cards daily on the wall (later we edited that to include MS Teams and Jira)

An important point to note is that social contracts should not be created and used as a box ticking exercise. Instead, they should be adhered to and revisited as often as required. If you’re a physically co-located team, place the agreement somewhere where it is visible to everyone. If you’re all working remotely, make it a part of your shared area where it is easily accessible and visible.

Why do you need a social contract

 Long time ago, we had a developer in our team who used to disappear during the mid-day when most of the teams were on lunch break and used to return after nearly an hour and half. Not only that, he used to leave early to pick-up his child from the day care centre. It was a concern for most because there was enough dependency on this developer and his unavailability was affecting others.

What would you do if you were being affected in this team?

Our team decided to use the social contract to remind everyone of their commitments.  In one informal meeting (it’s important to note that such discussions are more effective when not done in a formal setting), while chatting with each other team members asked him about this developer’s long breaks. It turned out that he was utilising his lunch break for visiting a gym and wasn’t aware that others were being impacted by his absence.

Because of a social contract where all were free to respectfully share their views, we were able to avoid what could be a difficult discussion.

What I have experienced is that social contracts help build psychological safety, openness, shared understanding, trust, congruence and a sense of accountability.

Who creates a Social contract?

Many teams have their social contracts created by someone in the management or the human resource (I guess calling it People & Culture is better) teams. Well, that’s not how a team contract should be created.

 For a team to become self-organising in a real sense, it is important that they define their own ways of working and guidelines. When the team creates their own standards, they will own it and will be committed to it. Creating and owning something collectively also helps teams establish better relationships with others.

  

How and when to create a Social contract?

A team should create a social contract when it is forming. However, many teams constantly grow and there may not be a single, common beginning for all team members. In that case, the core team or the group of people who join the team in the beginning should create a social contract. This core team should also ensure that every time a new team member joins them, they are given a walkthrough of this contract by other team members. They should also feel safe in reviewing and contributing to this contract. If that happens, the social contract will work in favour of the team.

 

Tips on how to create a social contract:

  • Get together as a team. If teams are located remotely, ensure people are able to turn their videos on. For such an important discussion, it is vital if team members can see each other.
  • Collectively choose someone who can facilitate the discussion. Social contract discussion can generate debates and having a good facilitator will help everyone stay on track. A facilitator will also help in ensuring that all get a chance to speak up. The facilitator does not have to be a delivery leader, a scrum master or a coach.
  • You may ask each team member to write what they expect from everyone in the team
  • If the team is located remotely, use a tool like Whiteboard Fox or Miro to collect ideas.
  • As a team, decide what common behaviours the team accepts as a minimum. 
  • Agree on what are non-negotiable behaviors.

Social contracts are mutual agreements and they should be enforced by the team. They are not pretty posters that teams use to appear Agile. These agreements are to build trust and to reinforce the feeling that a team is empowered and is in control. They also show that the team does not need to be controlled or commanded by someone in the organisational hierarchy.

It is also worth noting that these agreements do not replace organisational policies. Those policies are the boundaries within which teams function. Instead, working agreements are there to enhance the cultural aspects of an entity.

Do you have a social contract with your team? What is your experience from using it? 

Additional reading: 

If you are curious about the term Social contract and where it came from, a good starting point is Wikipedia. It is quite interesting too.

Although not directly related to Agile delivery, the text on Wikipedia speaks about the social contract theory or model as defined in moral and political philosophy.  One can argue that the statement below indirectly applies to how we behave in teams: 

“Social contract arguments typically posit that individuals have consented, either explicitly or tacitly, to surrender some of their freedoms and submit to the authority (of the ruler, or to the decision of a majority) in exchange for protection of their remaining rights or maintenance of the social order.” 

To learn more about the Social Contract Theory, visit these links:

https://www.iep.utm.edu/soc-cont

https://politicalsciencelessons.com/social-contract-theory-by-thomas-hobbes/

https://www.reference.com/world-view/thomas-hobbes-social-contract-theory-1c0d40a2e08398e2