I read Ultralearning expecting a productivity book.
And it is one, sort of.
Scott Young is methodical, practical, and hard to ignore. He gives you nine principles and shows you how to apply them. He also makes a convincing case that most people learn far below their potential, because they rely on passive or low-intensity methods: rereading, highlighting, watching lectures, absorbing, nodding along.
I found the case convincing enough to try to do something with it.
Arbor, the personal AI system I’ve been building since late 2025, is partly the result of that. Not a perfect implementation of Young’s framework. But shaped by it. The book informed the build.
For context, Arbor is part of my digital garden setup. It helps gather and organise the messy stuff: voice notes from the school run, reading notes, half-formed ideas, bits of theology, bits of work, things I notice and know I’ll lose if I don’t put them somewhere.
Around that I’ve built a small team of AI agents, each with a job to do. One helps with journaling. One helps with turning rough notes into drafts. Others help with research or organising material. The point is not for them to author for me. It’s more like having something that butlers the information, gets things into the right place, and gives me enough shape that I can then create properly.
Which sounds grand. Mostly it means I’m trying not to lose things I thought of while making tea.
The principle I reached for most consciously is Directness. Young’s argument is that the most underrated move in learning is to do the actual target activity, in conditions close to real use. Not to study the thing and then apply it later. To put yourself in the situation where the learning has to happen.
That’s what building Arbor has been. I didn’t spend months researching agentic AI before starting. I built a real system, for a real purpose, in my own life. The learning happened inside the project. The project was the environment.
Feedback worked the way Young describes, even when I wasn’t deliberately invoking it. Errors surfaced and I fixed them. Patterns repeated and eventually I tracked them properly, built process controls, developed an audit mechanism. My background in process engineering was doing work here without me consciously invoking it. I was applying what I already knew about systems, controls, and governance to a new domain.
Part of why Arbor has not become boring is that it still needs course correcting. There is always another function to extend, another process to streamline, another slightly annoying thing to fix.
But it is also useful enough that the work does not feel abstract. It helps me make something I actually need. And importantly, it keeps me out of the quagmire of coding and low-level detail. That is not really where my energy is.
The interest for me is in the design layer. How the parts fit together. Where the process breaks. Why an agent confidently does the wrong thing. How the whole thing can become more useful without becoming more complicated.
Where the implementation has been weaker is Retrieval. Most of the learning happened inside live problem-solving. That’s effective in its own way, but it means I haven’t always tested whether I could rebuild the deeper principles away from the immediate problem. The understanding may be shallower than it feels. Young would say: test it. Close the book and see what you actually know.
I haven’t always done that.
But here’s where the book opened something it didn’t quite answer.
Young’s framework is coherent on its own terms. Right design plus sufficient effort equals outcome. That is true within its domain. And there’s a parable that runs in almost exactly the same direction: the servant who buries his talent is not commended for his caution. Capacities given are capacities to be developed. Stewardship logic and ultralearning logic both say: take what you have and do something with it.
The difference is who the reckoning is with.
The parable is centred on God, not the self. The servants return to the master. The question isn’t “what did you achieve?” in the abstract, but “what did you do with what you were given?” Ultralearning is self-directed and self-accountable. It asks you to be ambitious, disciplined, and effective. It does not ask: for whom?
Stewardship without a master is just self-development.
And I do not mean that self-development is bad. It clearly is not. Learning, improving, building skill, becoming more capable … these are good things. But without a larger purpose they can become activity for activity’s sake. Painting coal. Making something look more finished without asking whether it is actually being put to use.
Young’s book is a tool without a telos. It tells you how to learn hard things. It does not tell you whether those are the right things, or what they are for.
There’s a question I kept circling back to while reading, and it hasn’t gone away.
Am I learning because I’m afraid of being insufficient, or because I’ve been given something worth stewarding?
I don’t think those two things always look different on the outside. In both cases you can be disciplined, motivated, doing the work. The distinction is internal. And honest self-examination is slippery here.
There’s a version of self-improvement that becomes control. If I can just learn enough, organise enough, optimise enough … I can manage the uncertainty. That’s not the same as striving for approval from others. It’s subtler. It’s the belief that competence will protect me.
I notice it when I look at Arbor. It is intricate, absorbing, intellectually satisfying. It gives me a legitimate reason to disappear into my own head. I can tell myself I’m building capacity, clarifying ideas, preparing better. All of that may be true. But it can still be a way of being alone without quite admitting I’m choosing solitude.
The ongoing test isn’t “is Arbor useful?” It clearly is.
The test is what it’s making easier: withdrawal or connection.
A very ordinary example is written communication. Spelling and grammar have never been my strongest suit, and that can make even a simple message feel heavier than it needs to. A WhatsApp to the youth team. An email asking for feedback. A note that should take five minutes but somehow starts to sprawl.
Arbor takes some of the hesitation out of that. It gets me to a first draft quicker, tidies the rough edges, and gives me something I can then shape in my own voice. Not perfect. Not finished. Just enough to get me moving.
That matters. Because if Arbor helps me communicate more clearly, prepare faster, and spend less time stuck in the awkward gap between having an idea and knowing how to say it, then it is serving connection. It is helping me come back to people.
But I’d know it had become sophisticated solitude if I kept refining the system without sharing the fruit. If I spent more time designing support systems than actually serving. If the workshop became more interesting than the people it was meant to help.
That is not a question to answer once.
What I’m taking from this book is less about the nine principles than about the frame around them.
The principles are good. Directness, Feedback, Retrieval … they describe real things about how learning works. I want to apply them more consciously. I already am, in some respects.
But I want to apply them inside a different logic than Young’s. Not maximum output. Not aggressive self-directed achievement for its own sake.
I have a lot in my life already. Family, work, church, youth work, writing. Not everything can be an ultralearning project. And some of the learning I’m most drawn to, theology especially, needs to stay rooted in response rather than achievement.
Since coming to faith later in life, theology has felt less like achievement and more like response. Grace has stopped being just a word I understood in theory and has started becoming the ground I stand on.
So the desire to learn is partly gratitude. Partly a need for roots. Partly honesty about the hard questions of life. And partly wanting to help others get to where I have found myself.
I do not want a faith that only works because it avoids difficult questions. That feels too fragile. Too dependent on keeping the lights low.
A faithful version of Young’s framework asks not how much more I can fit in, but what I can build or practise that helps me be more present for what I am actually called to. Arbor began partly as an attempt to put these ideas into practice. I’d like it to keep earning its place by what it returns to people, not just what it helps me do.
So the test for Arbor, and maybe for any learning system I build now, is not whether it helps me do more. I can always do more. That is part of the problem.
The point is whether it creates enough space to do the right things with more care. To be more available to family, church, youth work, writing, and the ordinary people in front of me. To return from the workshop with something useful in my hands, rather than simply finding a better reason to stay there.
I do not have this fully worked out.
I am still learning the difference between ambition and faithfulness.
But that feels like the right question to keep asking.
