---
title: "Bilingual knowledge base after a merger | Getaround case study"
url: https://warrenperez.com/en/case-studies/getaround/
description: "One reliable knowledge base, in English and French, for every team: how car-sharing platform Getaround structured its company knowledge after its merger."
language: en
---
Car-sharing platform

# Car sharing: a reliable, bilingual knowledge base to bring teams together after a merger

Getaround is an international car-sharing platform. During its merger, I worked [as an advisor to its VP Product](https://warrenperez.com/en/) to design its knowledge base: a bilingual source of reliable information for every team.

- 200+ people
- International
- English · French

## 1 · Context

Getaround is an international car-sharing platform, with teams spread across several countries.

After the merger, the company needed to bring different teams, practices and cultures together around shared knowledge. The VP Product was leading this initiative internally and wanted an outside perspective to secure its design.

## 2 · Challenge

The brief at a glance

- Establish a common reference after the merger
- Guarantee reliable information for all
- Serve two languages without duplicating
- Harmonize documentation practices
- Make the team autonomous

The challenge was not to produce documentation, but to establish a common reference in an organization being reshaped: company knowledge that is accessible to all, reliable, and available in both English and French.

That meant deciding what belongs at the global level and what belongs to each team, harmonizing disparate documentation practices and keeping the architecture simple enough to be maintained in-house.

## 3 · Roadmap

1. 1 Current-state assessmentA map of existing spaces, usage and team expectations, as the basis for every decision.
2. 2 Knowledge base architectureA clear structure between the global level and the team level, designed to be maintained in-house.
3. 3 Templates and shared rulesPage templates and shared writing guidelines, for consistent documentation in both languages.
4. 4 Oversight and mentoringSupport for the VP Product throughout the project, until the team was autonomous.

## 4 · The transformation

Before

- Teams from the merger, each with its own references.
- Disparate documentation practices.
- Information to make accessible in both English and French.

After

- A single, bilingual knowledge base, in English and French.
- Reliable information, shared by every team.
- A simple architecture, owned and maintained in-house by the VP Product and their team.

## Let’s talk about your project.

Tell me a little about what you’re working on. I’ll get back to you personally to discuss the next steps.

## More case studies

- Fintech scale-up [Confidential client : +80% reliability for internal AI](https://warrenperez.com/en/case-studies/scale-up-fintech/)and half as many questions to HR Confidential 300 peopleNotion, Dust
- Industrial group [DC Groupe : 61 steps launched in one click for each product](https://warrenperez.com/en/case-studies/dc-design-conception/)100% of exchanges recorded on the project 350 peopleNotion
- 360° digital agency [Nematis : 5 min instead of 45 to 60 per quote](https://warrenperez.com/en/case-studies/nematis/)project created automatically at signing 30 peopleNotion, HubSpot