Behaviour and protocol

Code Code reviews Consulting 101 Feedback Good meetings practices How to facilitate team meetings Inclusive language Values


360 review Continuing education policy Engineering manager career ladder Roles Software engineer progression framework Technical skills sheet

Employee manual

Abtion's pomodoro Employee benefits Internal days & community Intro Parental leave policy Safety and security Schedule, time tracking & calendar Sickness & unplanned absence Travelling Vacation & planned time off Work from anywhere policy

Project management

Technical setup when starting a new project Client discontinuing hosting or sla Converting projects from development to maintenance mode Estimating Estimating project maintenance Go live checklist Handoffs Invoicing guidelines Procedure for traffic


Audio setup Create amazon bucket Database backup setup Gpg signing Pairing setup

Technical practices

Bug triaging Css How and why we do design research Kick off meeting Pair programming Tdd testdriven development Workflow



Tools and services

Access and permissions Purchasing licenses and memberships Sharing sensitive information Stack and services Wordpress

Behaviour and protocol


Values are pointless if not put into practice. Our values are reflected in the following behaviors.

Collective ownership

Collective ownership gives control of the entire project to all team members. “Your part” is the product. Either it’s a good product, or it is not.

Collective vision

  • Communicate openly. No privileged information. Everyone should have the same basis for decision making.
  • Cut the middle person. We put the team directly in front of the stakeholder.
  • Break knowledge silos. No one is “the expert” in an area.

Collective accountability

  • Work end-to-end. We need to be able to impact as much of the project as possible.
  • T-shape profiles. We still have roles, and they know about areas surrounding their expertise.
  • Integrated QA. The team takes direct responsibility for the work they’ve created.

Collective contribution

  • Pair up! Team members work simultaneously on the same tasks.
  • Keep it simple. We want people to be able to pitch in.

Guiding values

Inspired by Voluntās we have defined a set of virtues. These virtues are meant to be a guide on how to approach situations where our values are in conflict. They are set up as “X over Y” to make it clear that we value both, but aim to prioritize the first.


  • Team over individuals
  • Autonomy over control
  • Transparency over appearances


  • Quality over progress
  • Feedback over consideration
  • Proactivity over minimizing work


  • Simplicity over versatility
  • Lunch time over crunch time
  • Defaults over personal preference