> ## Documentation Index
> Fetch the complete documentation index at: https://elrolio.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Level 10, Level 3

> A colleague stopped my demo four sentences in. Knowing my own setup cold is what made me the worst person to explain it.

![A flat Swiss-style geometric poster: ten teal steps ascending left to right, a small amber square on the third step and an emerald square on the tenth, with a wide empty gap between them.](https://mintcdn.com/elrolio/dDAUX7lMSQ8YljqL/images/journal/level-ladder-hero.jpg?fit=max\&auto=format\&n=dDAUX7lMSQ8YljqL\&q=85\&s=a5da3bbf59f6760b4c46b49af5c87b75)

## The Problem

I'd built an elaborate setup for working with Claude — layers of memory, automation, the works. I wanted to bring colleagues along, so I walked one of them through it. He stopped me a few sentences in: he got lost at the words "front matter." "You're showing me a level 10," he said. "I'm at level 3." The problem wasn't the system. It was that I'd lost the ability to see it from the outside.

## The Approach

I asked Claude to help me find the *one* thing a colleague could add that would improve their experience tomorrow — with no jargon at all. We landed on the smallest real upgrade: a short note you write yourself that the AI reads before every answer. The constraint did most of the work. If the explanation needed a technical term, it was wrong. Claude built the demo around asking the same question twice — once cold, once after the note goes in — so the gap between the two answers carries the whole point. The alternative we kept circling was a shared note everyone could use rather than one you write yourself, and that argument took longer than anything else in the session. It changes who reads the note, not what the note is.

## What Happened

Landing on the one note was the easy bit. What I kept turning over was whether it led anywhere. A first step that dead-ends just teaches people the thing isn't worth their time — so before I'd let it be the answer, I had Claude map the whole path with me: all ten levels, from that first note up to the setup I run now, so the small version actually points at the big one. Claude was a real collaborator through this, and occasionally a wrong one — its first read of the usage data on a small skills library a teammate and I had started was off, because it lacked the context I had, and I caught it before it shaped anything.

## What I Learned

None of this came from the work. It came from watching the colleague's face when he stopped me. I know my own setup cold, and it turns out that makes me close to the worst person to introduce it to anyone — I'd stopped being able to see the wall he walked into. That's the whole reason I went and mapped the path the same day, for him, standing at step one.

I'm still not sure how you teach something you've stopped being able to see.

***

*Drafted by my Claude from our working session. I approved it before it went up.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.