All use cases

A new colleague on the team

Day one on a new project, without documentation. We ask the map as an analyst and as a developer, and get two different answers, each backed by sources.

0:00 / 0:53

Transcript

Day one on a new project. The documentation is patchy, and nobody has time to answer questions. Here we ask the map, first as an analyst: what is this system for?

In a few seconds the chat puts the answer together from the whole map. It comes in business language: container rental and waste transport, three kinds of users, external identity and payment. Then we open a new thread and ask about the details as a developer: where do I start if I have to touch order handling?

This time the answer reads differently, through a developer's eyes, with technical detail: the largest service with its 459 lines, the duplicated filter conditions, and the scheduled jobs that also write the order status. Same map, two points of view, and a source behind every claim.

More use cases

Want to map your legacy system?

We only use your details to reply.