Team operations

The Team Operations section defines our systems for work coordination, planning, and accountability. It also defines expectations for all team members across 2i2c.

• Workflow goals and strategy
  • Our goals
  • Have a single source of truth
  • If it’s not written it doesn’t exist
  • Broadcast updates in multiple places
  • Update early and often
  • Distributed-first operations
• Code of conduct
  • Unacceptable behavior
    • Abusive behavior
    • Unwelcoming behavior
  • Scope
  • Enforcement
    • CoC Report Response Protocol
      • Read the report to determine whether there has been a code of conduct violation
      • Follow up with the reporter
      • Follow up with the community member who violated our code of conduct
  • Reporting
    • Why should I report?
    • Where and how to report
    • Who responds to violation reports
    • Confidentiality
  • Social rules
    • Social Rules
      • No well-actually’s
      • No feigning surprise
      • No backseat driving
      • No subtle -isms
      • How do they work?
      • Code of conduct
  • How we developed the code of conduct
  • Other things that don’t fit in to the code of conduct
    • When to seek help immediately
    • Getting help
  • License
• Workflow for planning and delivery
  • Quarterly objectives
  • Initiatives
    • What is an initiative?
    • How we track initiatives on our initiatives board
    • Structure of an initiative
    • Initiatives cycle
  • Delivery boards
    • Operations board
    • Product and Services board
  • Asana project with CS&S
  • Retrospective boards
    • Product and Services retrospective policy
• Team Practices
  • Guide for Open, Honest Conversations
    • Assume Positive Intent
    • Create Psychological Safety
    • Seek to Understand, Not to Be Understood
    • Be Honest (Do Not Avoid Uncomfortable Topics)
    • Welcome Critical Feedback
    • Focus on Shared Interests, Not Positions
  • Decision making guide
    • Principles of decision making
      • Leave a paper trail
      • Provide context, a plan, and a rationale
      • Designate a decider
      • Timebox the discussion
      • Consult the right people
      • Iterate on the core ideas.
      • Make it safe to try.
      • Make it safe to fail.
      • Bias towards action.
      • Trust one another.
    • Learn about consent-based decision making
  • Expectations of all team members
    • Embody our values and team practices
    • Identify our most important problems and how to solve them
    • Collaborate across areas
    • Hold one another accountable
    • Delegate power and responsibility
    • Advocate for and seek resources
  • Giving and receiving Effective Feedback
    • Quick overview
      • What is Feedback
      • Why is it important
      • What isn’t considered feedback
      • Who benefits from feedback
      • When to give and receive feedback
      • Caveats to feedback (the fantasies)
      • When should you use this document
    • How to give feedback
    • How to receive feedback
    • Saying “No” to receiving feedback
      • Deferring feedback with “Not now”
    • Asking for feedback
    • Feedback in asynchronous teams
    • Opportunities to give/solicit feedback
    • Examples of “Good” vs “Bad” feedback
      • Example 1
      • Example 2
      • Example 3
      • Example 4
    • Common feedback mechanisms
      • Continue vs Consider
      • Impact Feedback
      • Radical Candor
      • REAP Model
      • RISE Model
    • Follow-up thoughts/article
    • Resources
  • Responsibile and accountable roles
    • Learn more
  • “Brown Bag” Tech Talks
    • Summary
    • Who…?
    • Where, When, and for How Long?
    • Topics
    • Tracking the sessions
    • Presentation formats
    • How do I sign up?!
• Getting started and onboarding
  • Get an onboarding champion
  • Get access to the right accounts
  • Our documentation structure
  • How our team compass is organized
  • Where to learn about our workflow
• Where to look for information
  • Documentation
  • Google Drive
  • Public GitHub Issues
  • Private GitHub Issues
• Meeting guidelines and policy
  • Guidelines
  • Roles
    • Meeting Facilitator
    • Meeting Recorder
  • Types of meetings
    • Asynchronous team syncs
    • Team retrospectives
    • Professional development
    • All-hands
• Communication channels
  • Communication guidelines
  • GitHub Issues and Projects
  • Slack
    • Public channels
    • Private channels
      • The #team-updates Slack channel
      • The #initiatives Slack channel
    • Conversations that should not be in Slack
  • Zoom
  • Personal e-mail
  • Shared e-mail via Google groups
• About the Team Compass
  • Why have a Team Compass?
  • How to update the Team Compass
  • What is a Source of Truth