I’m 64 and Building Something New. Here’s What Nobody Tells You.

It didn’t start as a project, you know, it started as a problem sitting in my classroom where I was watching students submit work that was technically correct but visually incoherent and broken, and I realized there was no automated way to give them specific scaffolded feedback before the next class rolled around. So I built a tool in six days to solve it, something quick and dirty that did what I needed it to do, and it worked better than expected, so I kept building, and what started as a classroom patch became something people started asking about, and then other people started asking, and before I understood what was happening I was looking at something that might actually matter.

Here’s the thing nobody tells you about starting something enormous late in life: you can see both sides of the equation at once, and that’s not how younger people see it. A 28-year-old starting a company sees the opportunity stretching out in front of them and assumes they have time to figure it out and fail and figure it out again. I see the opportunity and I also see how much runway I probably don’t have, and that gap between what I’m trying to build and the time I have to build it is almost physical some days. It’s not paralyzing because I’ve already lost everything once and came back from it, so the stakes feel different, but it’s there; it’s a frequency you can hear in the background of every decision you make.

I am a designer, not a programmer, and I’m learning technology from scratch while teaching full-time and running the creativity experiment and maintaining the blog and building these exercises that keep multiplying. New territory, scary territory, the kind of place where you don’t know what you don’t know and you stumble through and sometimes it works. What strikes me is how much of what I need to learn isn’t really about the technology itself but about the thinking that surrounds it, the discipline of building something that scales and the constraint of being a single person trying to move something that wants to be a team. I’m not going to pretend I’m not afraid of getting this wrong, but the fear isn’t an argument for stopping; it’s just part of the thing.

Twenty-five years of teaching, and I watched the same problem show up in every classroom: feedback that came too late to matter, feedback that was too vague to use, feedback delivered in a way that broke the student instead of building them. I’d build exercises to address it, scaffold the thinking differently, give them real-time specificity about what was working and what wasn’t. It helped, and I kept refining it, and after a couple of decades of small interventions I realized what I’d actually been building was a solution to a problem that almost every student in every design program faces. The product is the most ambitious version of what I’ve been doing in classrooms for a quarter century; it’s just finally got a container around it.

When you start something at 64, you inherit the strange advantage of pattern recognition that younger people don’t have yet. I’ve watched businesses fail, including my own. I’ve watched education systems refuse to change and then suddenly have to. I’ve watched technology promise everything and deliver half of it and then deliver the other half sideways. I’m not under any illusions about how hard this is or how many things could go wrong, but I’m also not naive about how much good this could do if I can get it right.

The fear of time is real and it’s different from other fears; it’s not fear of failure but fear of running out of time to fail productively. You know what I mean? Some of my best learning came from failures that took months to process and years to extract the lesson from. I don’t have unlimited months, so I have to be ruthless about what I’m spending time on and what I’m letting go. The work becomes a different kind of treadmill, and I’m running on it the same way I run on the physical one every day, pushing to the edge of what I can sustain and trying to find the creative state on the other side of the grind.

What drives me back to the work isn’t the money and it isn’t the title and it isn’t the promise of success; it’s the problem itself and the fact that I know how to solve it because I’ve been solving it in smaller ways for 25 years. That’s earned me something that money can’t buy at my age: the permission to try something this ambitious because I’ve already proven to myself that I can rebuild when things collapse. That doesn’t make this less scary; it just makes the scariness a thing I can carry instead of something that carries me.

Starting this late means I’m racing something, but I’m also racing toward something, and the toward part is stronger most days. You know what I mean; there’s work that matters and there’s work that just fills time, and I finally know the difference because I’ve done both. The time I have left isn’t infinite, so every hour I spend on something that doesn’t matter is an hour I can’t spend on something that does. That clarity is worth more than the fear, so I keep building.