guide
  • Introduction
  • Guiding Principles
    • Mission Statement
    • Conflict Resolution Process
  • Operating Model
    • Working Together
    • Holacracy
      • Meetings
      • Specific Roles
      • Terms and Definitions
      • Finer Points
      • Holacracy-Asana Key
    • Getting Things Done
      • Daily, Weekly, Monthly, and Annual Reviews
      • GTD-Asana Key
    • Transparency
    • Language
    • Budgeting
    • By Department
      • Engineering Operations
  • General Guidelines
  • Employment Policies
    • Equal Opportunity Employment
    • At-Will Employment
    • Code of Conduct in the Community
    • Complaint Policy
    • Drug and Alcohol Policy
    • Vacation, Holiday, and Paid Time Off (PTO) Policy
    • Supplemental Policies for Remote Employees and Contractors
    • Supplemental Policy for Bonus, Commissions, and other Performance-based Payments
    • Supplemental Policies for Hourly International Contractors or Workers
    • Supplemental Policies for Hourly International Contractors or Workers
    • Disputes and Arbitration
  • Benefits and Perks
    • Health Care
    • Vacation, Holiday and Paid Time Off (PTO) Policy
    • Holiday List
  • Hiring Documents
    • Acknowledgement of Receipt
    • Partner Proprietary Information and Inventions Agreement
  • Engineering Wiki
    • Code Snippets
      • Front End Code Snippets
    • Setup
      • 1: Overview of development using Audienti
      • 2: How to setup your dev environment on Docker
      • 2a: Setting up on our cloud your dev server
      • 3: Connect to Production using the VPN
      • 4: Import data into your development environment
    • Deployment
      • Docker based deployment of back end (manual)
    • Culture
      • How our development team works
      • Code Best Practices
    • Tips
      • Setting up a new development machine
      • Importing data to Development environment
      • GIT workflow and work tracking
      • Using Slack
      • Using Rubocop
      • Our Code Standards
      • General suggested best practices
      • Tracking your time
      • Naming Iterations
    • Migrations
      • Postgres
      • ElasticSearch
      • Redis
    • Database and System Maintenance
      • Redis Howtos
      • Elasticsearch HowTos
      • Postgres HowTos
      • Administration recipes
      • App maintenance crash course notes
    • Front End
      • 2016 Plan
      • Deploy
      • Assets
      • SearchLogic
      • How to create UI components
      • OMA Standard Tables
    • Monitoring and Alerting
      • Monitoring Systems
      • Monitoring individual controller actions
      • Get notified when a metric reaches a certain threshold
      • Instrumenting your models using Oma Stats
      • Configuring Graphite Charts
      • Tracking your results with StatsD
      • Logging Fields
      • Updating Kibana Filtering
    • Testing
      • Coverage
      • Elasticsearch mapping config synchronization
      • Testing Gotchas
      • Rspec Preloader
      • Test Best Practices
    • Models
      • Backlinks
    • Queueing and Worker System
      • Queueing and Job Overview
    • Processors
      • Rebuilding Spot Instances
      • Deploying processors
      • Running processors in development
      • Reverting to the previous build on a failed deployment
    • Processors / Opportunity Pipeline
      • Opportunity Pipeline
      • Diagram
    • Processors / Enrichment Pipeline
      • Diagram
      • Clustering
    • Processors / Backlink Pipeline
      • Diagram
      • Backlink Pipeline external APIs
      • Backlink pipeline logic
    • Processors / Automation Pipeline
      • Diagram
      • Automation Pipeline Overview
      • Agents
      • Running in development
    • Messaging and Social Accounts
      • Overview
    • API
      • Audienti API
    • Algorithms
    • Troubleshooting
      • Elasticsearch
    • Big Data Pipeline Stuff
      • Spark
    • Our Product
      • Feature synopsis of our product
    • Research
      • Backend framework comparison
      • Internet marketing Saas companies
    • Code snippets
      • Commonly Used
      • Not Used
    • Miscellaneous
      • Proxies and Bax
    • Legacy & Deprecated
      • Search criteria component
      • Classes list
      • Target Timeline
      • Twitter processor
      • Asset compilation
      • Test related information
      • Interface to EMR Hadoop jobs
      • Mongo Dex Indexes to be Built
      • Mongodb errors
      • Opportunity pipeline scoring
      • Graph Page
      • Lead scoring
      • Insights
      • Shard keys
      • Setting up OMA on local
      • Clone project to local machine
      • Getting around our servers in AWS
  • Acknowledgements
  • Documents That Receiving Your First Payment Triggers Acknowledgement and Acceptanace
Powered by GitBook
On this page
  • Formal Process
  • Resolution Phases
  • Clearing Coach
  • Third Party
  • Partners v.s. Non-Partners
  1. Guiding Principles

Conflict Resolution Process

At OMAlab, we address and resolve conflicts with these principles at front of mind:

  • It’s impossible to change other people. We can only change ourselves.

  • We take ownership for our thoughts, beliefs, words, and actions. We don’t spread rumors.

  • We don’t talk about another partner behind their back.

  • We resolve disagreements directly with those involved, and don't drag anyone else into the problem.

  • We don’t blame problems on others. When we feel like blaming, we take it as an invitation to reflect on how we might be part of the problem (and the solution).

Formal Process

Most interpersonal tensions can be resolved by sharing and being heard. If, however, your tension is work-related, or it isn't just resolved by being heard, you still need to address it directly with the person you have tension with using a more formal process.

Any formal conflict starts with a partner bringing a request directly to another partner. The request needs to be actionable, clear, present, and sufficient to resolve the conflict. Requests can be benign ("Please make a public commitment to our circle to arrive to meetings on time."), to more involved ("Please commit to engaging a professional coach that will help you with your writing style."), to the most extreme ("Please resign this particular role" or "Please resign from the Company").

At all stages, the partner receiving the request can say Yes, No, or negotiate for a different outcome. If there's a "Yes" or another outcome that's sufficient to both, then the conflict is resolved. If there's a "No" then the initiating partner has the choice of either escalating the conflict to the next phase, or dropping it.

Resolution Phases

  1. In the first phase, the two partners sit together and try to sort it out privately.

  2. If they can’t find a solution agreeable to both, they nominate another partner they both trust to act as a mediator. The mediator doesn’t impose a decision. Rather they support the participants in coming to their own solution. Again, a clear request is needed, and a Yes, No, or a compromise.

  3. If mediation fails, a panel of topic-relevant partners is convened. Again the panel does not impose a solution. They weigh in with what they think is fair, and it's up to the person receiving the request to decide.

  4. In an ultimate step, if a resolution is still not reached, the Conflict Resolver is called into the panel. Unlike the previous stages the Conflict Resolver can choose to impose a solution.

Clearing Coach

If you need coaching or support before clearing with someone, or before/during engaging in a formal resolution process, reach out to the Clearing Coach and set up a coaching session. The Clearing Coach will support you in resolving the conflict directly, and hold you accountable to closing the loop.

Third Party

Sometimes, a partner can sense a conflict between two people (or is caught in a triangulation between them). If that's the case, they can ask one (or both) parties to the perceived conflict whether or not there actually is one (reality check), and make a request that they address it and report back.

Partners v.s. Non-Partners

Our conflict resolution process is an agreement made by and between partners. It's important to remember and acknowledge that no other stakeholders are bound to the this process, or have agreed to it. When resolving conflicts with non partners, do your best to adhere to the spirit of our agreements within the confines of what's efficient/appropriate to the situation.

PreviousMission StatementNextOperating Model

Last updated 7 years ago