Cursor pour les nuls — adoption at scale

Real usage from the portal — not vanity metrics. People came back, asked questions, and teams invited me to present.

Cursor was powerful, but adoption was uneven. Engineers didn't know where to start, which internal APIs to wire in, or how to configure MCP servers for their stack. Knowledge was scattered — Confluence here, Slack threads there, no single place to learn and ask.

The gap wasn't the tool — it was the onboarding path. People needed a hub, a guide, and someone to unblock them on real use cases.

Cursor pour les nuls — an internal portal combining a structured knowledge base, a RAG assistant trained on internal docs, and a collaborative forum. One place to find the right APIs, discover internal tools, and learn how to set up MCP so Cursor works in enterprise conditions.

The embedded AI assistant answered practical questions directly on the portal — how to connect to internal services, which APIs to use, workflow patterns that worked for other teams. Over 100 questions were asked, turning the site from a static wiki into an active support layer.

No public URL — internal tooling built for Nokia engineers in my sector, with content scoped to what they actually need day to day.

I ran presentations and hands-on sessions across 4 different teams in my sector — not generic slides, but hooks tied to their actual workflows. The goal: convince people to try Cursor, show concrete use cases, and point them to the portal when they needed APIs, internal tools, or MCP configuration.

Each session ended with a clear next step — a use case to try, a doc to read, or a follow-up pairing session.

Beyond the portal and demos, I spent a lot of time helping colleagues one by one — unblocking specific use cases, pairing on tricky integrations, brainstorming the best approach when the first idea didn't land. That's where adoption actually stuck: when someone ships their first real feature with Cursor instead of giving up after day one.

The pattern was always the same: understand the blocker, map it to the right internal API or MCP setup, then pair until it works in their repo.

Creator, lead, and adoption champion. I designed and shipped the portal, built the RAG integration, ran the team demos, and stayed available for guided coaching. This is the human side of DevEx — not just documentation, but momentum.