> For the complete documentation index, see [llms.txt](https://handbook.sixpivot.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.sixpivot.com.au/our-culture/connecting.md).

# Connecting

Being a remote first team it's important we build in some habits and ceremonies to foster connectivity, here's a few:

<details>

<summary>👋 1-on-1s</summary>

Every few weeks with key people you're working with (or sometimes more, we'll work out what you need).

*Intention: to remove blockers, support wellbeing and personal development.*

</details>

<details>

<summary>🍩 Donuts</summary>

Every three weeks, connections to have a virtual "[donut](https://www.donut.com)" with a random team member in the channel.

*Intention: for team to get to know each other and build rapport.*

</details>

<details>

<summary>🌱 Sixers</summary>

Monthly all hands for what's happening at SixPivot.

*Intention: keep everyone informed and updated with a bit of banter.*

</details>

<details>

<summary>🧑‍💻 Dev huddles</summary>

Once a month for a quarter. Devs share interesting learnings or things they're working on, almost like a code club.

*Intention: for devs to get together and build rapport.*

</details>

<details>

<summary>🍔 Lunch and learns</summary>

Initiated on the fly by individuals (open to anyone on the team) e.g., Quinten did a session about milling lumber, Newt did a NRL fantasy hobby project, Dylan did a Kubernetes session etc.

*Intention: sharing, learning, building rapport and having fun.*

</details>

<details>

<summary>📕 Book club</summary>

Every other month. Team opt-in by joining #pd-books where they pick a book to read and discuss. \
\
*Intention: learning and sharing together.*

</details>

<details>

<summary>🏔️ Summit</summary>

In person once a year (around July/August) all hands conference. The entire company are flown in to talk shop.&#x20;

*Intention: deep dive into the business, radical transparency on what's happening and the year ahead.*

</details>

<details>

<summary>🌴 Retreat</summary>

In person occasional retreat (generally around November/December) whole company (plus family invited) paid weekend getaway at a resort.

*Intention: for team to relax, have fun and get to know each other + family better. No work, social only.*

</details>

<details>

<summary>💼 Going to the office</summary>

Access to The Hub in each city, more info [here](/how-we-work/office-details.md)

*Intention: a physical place for people to meet or place to go to get out of the house.*

</details>

<details>

<summary>🎙 External speakers</summary>

Once a quarter with internal breakout rooms after, topics include (unconscious bias, accessibility, financial education, LGBTQIA+, neurodiversity, mindfulness talks)

*Intention: learning together and building rapport.*

</details>

<details>

<summary>🙋 PPP (Pivots, Pivots, Pivots)</summary>

In person, by state, [DDD conference ](https://www.dddbrisbane.com)style internal presentations.

*Intention: creating an internal sense of community and learning.*

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://handbook.sixpivot.com.au/our-culture/connecting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.