# Adopting EventCatalog in your organization

Copy as Markdown[View as Markdown](/docs/development/getting-started/adopting-eventcatalog.md)

***

Most organizations adopt EventCatalog step by step. This is the pattern we see most often.

1**Start with a champion**

A personorA team

2**Solve one pain point**

“Where are our event schemas?”OrderCreatedPaymentTaken

3**Share it and get feedback**

Can we add our services too?Who owns this event?

4**Grow it over time**

DomainsSystemsServicesMessagesFlowsTeams

The value of your catalog grows as you add to it

## 1. Start with a champion[​](#1-start-with-a-champion "Direct link to 1. Start with a champion")

A champion drives EventCatalog in your organization. It can be one person or a team. They set up the first catalog, and help other teams start using it.

## 2. Solve one pain point[​](#2-solve-one-pain-point "Direct link to 2. Solve one pain point")

The champion picks one workflow or pain point, and documents around it. For example, teams can't find the schemas for your events, so the first catalog documents your events and their schemas.

Starting small means the catalog is useful from day one, and you learn what your organization needs from it.

## 3. Share it and get feedback[​](#3-share-it-and-get-feedback "Direct link to 3. Share it and get feedback")

Once the pain point is solved, share the catalog with other teams and ask for feedback. Teams will tell you what they want to see next, and some will start contributing.

## 4. Grow your catalog over time[​](#4-grow-your-catalog-over-time "Direct link to 4. Grow your catalog over time")

Build the catalog up over time: add [domains](/docs/development/guides/domains/introduction.md), [systems](/docs/development/guides/systems/introduction.md), services, [flows](/docs/development/guides/resources/flows/introduction.md) and owners. The more you add, the more your catalog connects, and the more valuable it becomes.

To keep it up to date as it grows, generate parts of it from your [specifications and schema registries](/integrations.md), and keep it in sync with your code with [EventCatalog Agents](/docs/development/agents/set-up-code-to-docs.md).

## One catalog, or many[​](#one-catalog-or-many "Direct link to One catalog, or many")

You can have one catalog for your whole organization, or a catalog per team combined with [Federation](/docs/federation/overview.md). With Federation, each team controls its own documentation, and you still get one view of your whole architecture.

One catalog for the organization

orders-servicepayments-serviceinventory-service

![](/img/eventcatalog-cat-book-black.svg)acme/catalog

A catalog per team, with Federation

orders-servicefulfilment-service

![](/img/eventcatalog-cat-book-black.svg)orders

payments-servicefraud-service

![](/img/eventcatalog-cat-book-black.svg)payments

![](/img/eventcatalog-cat-book-black.svg)Organization

Most organizations start with one central catalog and a couple of champions, then roll it out to more teams.

## Talk to us[​](#talk-to-us "Direct link to Talk to us")

If you want to discuss how to roll out EventCatalog in your organization, [contact us at hello@eventcatalog.dev](mailto:hello@eventcatalog.dev). We're happy to walk you through the options and advise you.