> For the complete documentation index, see [llms.txt](https://www.lawfirm-operations.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lawfirm-operations.org/roundtables-and-exchange/session-2-working-roundtable.md).

# Session 2: Working Roundtable

Thursday, 19th December 2024

## About the Speaker

Due to the fact that this Roundtable took place shortly before Christmas, this session followed a slightly different approach.&#x20;

Several speakers shared insight on their topics of expertise.&#x20;

## Abstract

The goal of this session was to develop a common understanding of what Law Firm Operations at the LLI entails.

We talked about the following topics:

* Tools & Technology (Julius Burgermeister - [Linkedin](https://www.linkedin.com/in/julius-burgemeister-5ab593255/))
* People (Bernhard Waltl - [Linkedin](https://www.linkedin.com/in/bwaltl/))
* Processes (Valéri Pollentzke - [Linkedin](https://www.linkedin.com/in/pollentzke/))
* Acquisition (Georg Anders - [Linkedin](https://www.linkedin.com/in/dr-georg-anders-a6398935/))


---

# 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://www.lawfirm-operations.org/roundtables-and-exchange/session-2-working-roundtable.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.
