Lesson 8.1
What Is a Circle?
Distance, definition, and the equation hiding inside the Pythagorean theorem
The unit opens by asking students to do something they assume they already can: say what a circle is. The task is deliberately sparce. Using only a marker and a length of string, draw every point a fixed distance from a chosen center, then write a precise definition of the shape you drew. Producing the drawing takes a few minutes. Writing the definition is where the lesson actually lives. This is the moment to reach back to is the work we did at the very start of the year, when we established that a definition’s job is to categorize and differentiate. To draw a boundary that admits every circle and excludes everything that isn’t one.
That framing gives you something to push on. When a group writes “a round shape” or “a loop,” I sketch an ellipse or an infinity symbol next to their board and ask whether their definition lets those in. If it does, they go back to tighten it. The more revealing failure is the group that defines a circle using “radius” or “diameter.” Those words sound rigorous, but they presume the very thing being defined. You can’t say what a radius is without already knowing what a circle is. I ask those groups to define radius and diameter, and they hear the circularity themselves (the pun is unavoidable). A small moment, but it’s the same disciplined attention to hidden assumptions we’ve been building all year.
From a solid definition, the equation is a short walk: a point (x, y) lies on the circle exactly when its distance from the center equals the radius, and squaring the distance formula gives (x − h)² + (y − k)² = r². That chain is the whole point, students who derive it own it, students who are handed it confuse it with every other formula they’ve met. One change I’d make here: opening with a general center (h, k) and a general point (x, y) was too abstract for most groups. Next time I’d anchor it first with a concrete center and radius, get the equation for that specific circle, then generalize. The abstraction lands far better as a second step than as the starting line.
The honest weak point the first time through was flow. The extensions were good problems, but they behaved like finished problems once a group would solve one, got a clean answer, they sit waiting for what came next. The only way I can see avoiding this here is good use of the banner system that Liljedhal describes in BTC.
One smaller adjustment: before students make their notes, I’d work a couple of examples with the class so they know what the notes are for and what’s worth keeping.