The iPhone Test: Before You Add One More Thing to the Education System
A short guide to zooming out, before you sign off on more spending
October 26, 1985. A 36-year-old teacher stands in front of her class. A decade of experience is already behind her. The building she teaches in is a concrete box: classrooms with desks in rows, a corridor, and a yard for recess. No computer lab. No moving walls. No beanbag chairs for morning circles. No project-based learning, and no program called "My Heart Is Your Heart."
Jump forward forty years. That same teacher, now 76, looks at a contemporary school — the infrastructure, the technology, the curriculum — and smiles. Not with contempt. With curiosity. She's trying to work out what exactly the system was trying to fix.
Because out of that room, the concrete box with nothing in it, came people. Two of her students built groundbreaking technologies and sold them for hundreds of millions. One became the commander of the air force. Another became the minister of justice. And one built the country's largest support network for children from the periphery.
And this is where the nagging question begins. What exactly do we think she was missing — when it worked? Of everything we've added since, what actually made school better? And if the answer is embarrassing, maybe it's time for a new rule.
The iPhone Test
Just as the original iPhone was allowed a single button, every addition to the education system — a program, hardware, software, or physical infrastructure — has to justify itself in advance. The default is not to add. If the value isn't known and proven before the purchase, it doesn't go in.
What Was Actually in the 1985 Classroom
Let's be clear right away: this isn't nostalgia. Nobody misses the chalk, the corporal punishment, or classes of forty. That classroom lacked plenty, and we fixed some of it for good reason.
But it's worth pausing on what was there. A teacher who knew every student by name, not just by grade. Time — not time fractured between systems and notifications, but continuous time. Clear expectations: students knew what was asked of them, and why. And above all, a human relationship, one that wasn't mediated by a screen.
And above all of these stood one thing easy to miss, because it wasn't sitting on the desk — it was inside the students: the capacity to learn. Raw human capital. The ability to concentrate over time, to sit with frustration, to repeat something until it sticks, and to build knowledge layer on layer. That wasn't a feature of the school. It was what students brought with them, and the school only had to avoid ruining it.
And here is the heart of the matter. That capacity, which developed naturally in the children of 1985, is worn down and broken in many of today's children. Not because of a curriculum, and not because of a shortage of beanbag chairs — but because of a combination of factors that fed Israel's human-capital crisis over the past twenty years: digital fragmentation, the erosion of attention, the growing distance between adult and child, and the overload that turned learning into noise. The building stayed. What emptied out is what the student brings into it.
The great confusion in the education debate is between what was simple and what worked. The 1985 classroom was simple. Some of what happened in it worked. Those are two different things, and we shouldn't throw out the second just because we're tired of the first.
The Rule: One Button Only
It's called the iPhone Test because of one design decision by Steve Jobs. The original iPhone had a single physical button — the home button. That wasn't a technical limitation. It was a stance: the default is not to add. Every button, every feature, every addition had to prove it was essential — otherwise it simply didn't go in.
Notice who carries the burden of proof. It's not the one who wants to keep things simple who has to defend himself — it's the one who wants to add. Simplicity gets the automatic advantage. The addition has to earn its place.
Education systems operate in exactly the opposite way. With us, the default is to add. A new program comes out — we roll it out. A platform appears — we buy it. The neighbor renovated the teachers' lounge — so we renovate too. Procurement is driven by availability, not by proven need, and the burden of proof falls on whoever dares to ask, "Wait, what for?"
The iPhone Test flips the order back. First the question: what specific failure does this solve, and how do we know it works? And only then the purchase. If there's no answer to the first question, there's no addition. Like the button that didn't make it in: not because it was bad, but because it didn't prove it was essential.
Are We Just Doing More of the Same?
Here's the uncomfortable part. Much of what we add to the system isn't a solution to a problem — it's another layer on top of an existing layer that already doesn't work.
We didn't go back to check what broke. We just piled on top of it. A computer lab on top of a teaching method that never changed. An educational platform meant to cram more material into the head, instead of building capacity. A new beanbag chair in the corner of a classroom where the student still doesn't understand why he's there.
It looks like progress. Usually it's an expensive distraction. We buy the feeling that we're moving forward, without touching the root. And the higher the pile grows, the harder it is to see what's underneath, beneath all the layers.
Take one familiar example: life-skills lessons and educational sessions meant to shape behavior. They've been in the system for twenty years, and every year we try to refine them — another program, another model, another kit. But if twenty years of such sessions haven't produced real behavioral change, the right question isn't "how do we improve them?" but "why are we still trying to refine something that doesn't work?" That's exactly the reversal the iPhone Test demands.
The Wrong Metric
We have a habit of measuring investment by how much money went in. How much budget per student, how many screens in the classroom, how many programs listed in the brochure. But the amount invested in a student was never the metric. The metric is what was done with it.
And variety and shine aren't the metric either. A program isn't worth more because it's new, and a classroom isn't better because it's impressive to look at. The only metric that counts is measured proof: did using this addition actually build capacity in the student? If you can't show that, it's shine, not value.
And so the budgets have to go back to the one place where they're truly measured: the students themselves. Not the building, not the platform, not the kit. The person they are, and the person we owe them the path to become. Every shekel that doesn't go there has to justify itself anew.
What Wore Down and What Broke
So let's look back. Not to reminisce, but to identify. Of everything that worked in the classroom of old, what wore down along the way — not because we added something, but because of what we pushed out to make room for it?
Continuous time wore down in favor of fragmentation. Human attention, one-on-one, wore down in favor of technological mediation — mediation meant to instill knowledge in order to pass exams, not to serve the whole person and the independent learner. Clear expectations wore down in favor of a vagueness that sounds progressive. These aren't things that broke on their own. We pushed them out, layer after layer, without noticing.
And this is the point: most of what we lost cannot be bought back. No purchase manufactures relationships. So before adding more, it's very much worth identifying first what we've already lost along the way.
Back to Basics — Not Back in Time
And here's the most important distinction in this article, because it's very easy to miss. "Back to basics" is not "back to 1985."
Nobody is proposing we bring back the chalk and dismantle the computer lab. Back to basics isn't a retreat — it's a way of working. It means: research before you buy. Prove value before you roll out. Spend money only when there's a justification you can point to.
The 76-year-old teacher doesn't hold some magic secret. She simply had no budget to waste on what didn't work, so she was forced to focus on what did: the technical, social, and emotional capacity of her students. The ability to solve a problem, to work with others, to sit with frustration and not give up. In other words, she cultivated the core of human capital, not the things arranged around it. That discipline is something we can adopt again — not the old building, but the logic behind it.
💡 Summary
The most expensive addition to the education system isn't the one that costs the most money. It's the one we added without knowing exactly why. The iPhone Test is one simple rule: the default is not to add. If you can't point to the failure the addition solves, and to the proof that it works, it doesn't go in. Go back, identify the real failure points, and research. Don't spend money just because you can.
The iPhone was born with one button. Everything else had to prove itself.
Let's continue the conversation 💬
I'd love to hear your perspective — whether you see things differently or whether this connects to your own experience. If you're thinking about what to do now with these ideas, or wondering how they might play out in your specific situation, let's talk about it.
✉️ Write to me: [email protected]