◢◢ Expectations

Introduction

This document outlines the core expectations for the JA Product team to ensure effective communication, understanding, updates, and continuous improvement. Clear adherence to these expectations will help keep our small team running smoothly.

Four Expectations

1. Communicate

• We primarily rely on asynchronous communication, emphasising written communication. Ensure your messages are clear and provide the necessary context.
• Utilise various forms of communication when appropriate, such as Loom, presentations, or Miro boards.
• When writing documentation or pull request descriptions, make sure reviewers understand your changes and how to facilitate their deployment, including testing requirements and known limitations.

2. Understand

• Thoroughly read, watch, or consume any communications sent your way, whether it's a Slack message, Asana ticket, or company presentation.
• If you have any doubts or uncertainties, don't hesitate to ask questions. Clarity around goals and tasks is essential, and we're here to support each other.

3. Update

• Due to our asynchronous culture, regular updates are vital. Share updates with your product team colleagues and, when necessary, with the wider business.
• Business-wide communication is typically handled by ADP and Annette, but you may be asked to provide a company-wide update if you've worked on something specific. Advance notice will be given where possible.
• Maintain Asana tickets, ensuring they are up to date, relevant, and in the appropriate status.
  • Please update tickets assigned to you at least once per day so team members outside of the tech team can see the status and state of a given piece of work.
  • Please add contextual information to tickets (links to PRs, architecture diagrams and documentation etc.)
  • If you have waited more than half a day for any kind of unblocker, post a message on Slack #devs (or #product) making note of what you’re waiting for and from whom. Also update the Asana task. The content of the update can be the same across both Slack and Asana for this.

4. Improve

• Strive to leave the codebase in better condition than you found it. While we acknowledge the complexity of our project and codebase, daily small improvements and refactors will lead to overall improvements over time.
• Log improvements that you cannot action now to the “Tech debt” board.

Ownership and Accountability

• Each team member is responsible for adhering to these expectations and seeking guidance or clarification as needed.
• ADP is the primary point of contact for any questions or concerns related to these expectations.

Feedback and Review

• These expectations will be regularly reviewed and updated to reflect the evolving needs of the team.
• Open communication regarding these expectations and their effectiveness is encouraged. Team members can seek feedback and provide input to improve this framework.

By following these expectations, we can maintain a productive, cohesive and enjoyable place to work. Your commitment to these principles is crucial for our success. Thanks!