> 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-9-effective-legal-workplace.md).

# Session 9: Effective Legal Workplace

Thursday, November 20th, 2025

## About the Speakers:&#x20;

Robert Faußner, Leo Balk and Georg Anders from HEUSSEN.

## Abstract:&#x20;

We focused specifically on operations, i.e. the areas of non-legal work in law firms. We firmly believe that

* Process optimisation
* Employee training and motivation
* Use of AI tools&#x20;

offer special added value here in particular.&#x20;

This meeting was not about the future of the legal profession or billable hours, but rather practical about the support for assistants and back office staff. As a ‘warm-up’, Robert Faußner, Leo Balk and Georg Anders from HEUSSEN reported on the use of Microsoft Copilot in the “Protected Area”.&#x20;


---

# 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-9-effective-legal-workplace.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.
