---
title: Meetings
description: How we run meetings at Langfuse.
---

# Meetings

We have a small number of regular meetings. Generally, standing meetings are an anti-pattern and most things are better resolved adhoc/async.

![Meetings](/images/handbook/maker-schedule.png)

## Weekly Meetings

### Monday: Team Sync

- "What is your focus of the week?"
- Team-specific, e.g. one meeting per GTM, Marketing, Engineering
- Duration: 30 minutes
- Goal:
  - Help everyone with accountability/focus for the week
  - Identify dependencies
  - Create opportunities for others to make quick suggestions/share context

### Tuesday (Biweekly): ClickHouse All-Hands

- Company-wide updates, metrics, and open Q&A with the leadership team

### Wednesday: Langfuse All-Hands

- Company-wide updates, metrics, and other topics relevant to everyone
- Goal:
  - share context across the company
  - look at metrics
  - discuss company-wide topics

### Friday: Demo All-Hands

- "What did you ship this week?"
- Full team, 60 minutes
- Everyone has 2-4 minutes
- Usually this involves screen sharing, but can also be a verbal summary.
- Not a proof of work meeting, sometimes you don't have anything to show
- Goal:
  - celebrate wins
  - share context of what is going on
  - share learnings

We recorded a weekly demo for you, just see for yourself:

<iframe
  width="100%"
  className="aspect-video rounded mt-5"
  src="https://www.youtube-nocookie.com/embed/Dmia1EK9JaI?rel=0"
  title="YouTube video player"
  frameBorder="0"
  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
  referrerPolicy="strict-origin-when-cross-origin"
  allowFullScreen
></iframe>

## Bi-monthly

**Team Retro (1h, full team, often during lunch/dinner)**

- Goal: increase our effectiveness as a team
- Everyone prepares 0-3 start/continue/stop items; Figjam board shared ahead of the session in `#team-async`
- Meeting:
  1. Read through everyone's notes, add comments when something is unclear, add 3 dot-votes to notes that are most relevant to you
  2. Resolve open comments
  3. Discuss the highest-ranked notes based on dot votes
  4. Commit to changes that we want to make as a team

## Quarterly

- [Roadmap Planning](/handbook/product-engineering/how-we-work/roadmapping)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/handbook/how-we-work/meetings.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.