# Focal Distance > Learn when to work close to a detail and when to pull back to the whole. **Curriculum phase:** Foundation **Lesson:** 03 **In this lesson:** - How scope works like a camera lens — zoom in for clarity, zoom out for context - What breaks when focal distance drifts - How to recover and hold the right focal distance - The spectrum from too short to too wide Presence is about your state. Focal distance is about your scope — how much you and the AI are trying to hold at once. --- ## The Photography Principle In photography, focal distance is where the lens is sharpest. Wide focal distance: you see everything, but nothing is perfectly clear. The landscape is visible but soft. Details blur. Short focal distance: one thing is crystal clear, every detail visible. But you lose the surrounding context. You can't have both at once. As one thing gets sharper, its surroundings get softer. **Working with AI behaves exactly the same way.** --- ## Focal Distance in the Loop For the loop to work, you and the AI need to be looking at the same thing, at the same scale, with the same clarity. **Short focal distance:** you're both focused on one small, specific thing. - The code is readable; the intent is explicit - You see exactly what's wrong - You know how to steer - The loop tightens. Progress is rapid. **Wide focal distance:** you're both zoomed out, trying to hold a massive vision at once. - Details blur; the model gets lost between what you meant and what you said - You can't see the cracks - The loop stretches and breaks. Progress stalls. --- ## When Focal Distance Breaks Focal distance doesn't stay fixed. It drifts. Here's how: **The project grows.** What started small becomes complex, but you're still trying to see it all at once. Details blur. **You lose presence.** You stop paying attention to specifics, and the focal distance widens on its own. **You get vague.** "Make it better" instead of "change the button color." Wide input produces wide output. **Clarity gets sacrificed.** Code gets messy, documentation gets sparse, architecture tangles. Now you can't see clearly even when you want to. You know focal distance is broken when: - "I don't know why this works, but it does" - The output is technically correct but feels wrong - Each cycle moves further from your vision, not closer - You're looping faster but learning less --- ## Recovering Focal Distance When you notice it's broken: **Zoom in.** Pick one small thing. Ignore everything else. Get that one thing crystal clear. **Sharpen your description.** Instead of "make this section better," say "change the button from 'Submit' to 'Send' and move it left." **Demand clarity from the AI.** If you can't understand the output, it isn't clear enough. Ask the AI to explain it. **Document as you go.** Write down decisions and trade-offs. It keeps the thinking visible. **Slow down.** Speed feels like progress, but often it's just noise. Slow cycles with focal distance beat fast cycles without it. --- ## The Spectrum Focal distance isn't binary. It's a spectrum you learn to modulate: **Too short:** you're so zoomed in that you miss how things connect. You optimize one detail and break something else. **Just right:** you can see the immediate context and how it relates to adjacent things. Your decisions work locally and globally. **Too wide:** you're trying to hold the entire system in your head at once. Everything is approximate. Nothing is quite right. The skill is knowing when to zoom in and when to zoom out — feeling when the distance is right for the work in front of you. That isn't learned from explanation. It's learned through cycles. --- ## Exercise 1: Recognizing Focal Distance **Time: 30 minutes** Look at something you've built recently — a document, code, a project, anything. Ask yourself: 1. Can I see what I was trying to do? 2. Would someone else understand it? 3. Is it so detailed it's confusing, or so vague it's useless? 4. What's the focal distance? (too short / just right / too wide) Write a paragraph describing the focal distance and whether it works for the purpose. --- ## Exercise 2: Maintaining Focal Distance in the Loop **Time: 3–5 cycles over a few days** Run five cycles on a project. Between cycles, ask yourself: "Is my focal distance the same as the AI's?" If yes, note what's working. If no, note how it diverged and what you'll do next cycle to realign. Keep a simple record: ``` Cycle 1: Aligned? No → I'll be more specific about _____ Cycle 2: Aligned? Yes → Output was much better Cycle 3: ... ``` --- You know the loop. You know what presence demands. You know how to manage scope. Now: what are you and the AI actually working within? The environment matters more than you think.