Hi, this is Ray.

I want to start with a specific realization I had that took me embarrassingly long to articulate clearly. For years, I used the words "system" and "routine" interchangeably when talking about my learning practices. If I had a consistent morning study block, I called that my system. If I had a specific technique I applied regularly, I called that my system. The words felt synonymous. But I noticed that some of my "systems" were producing much better learning outcomes than others despite being similarly consistent, and I couldn't quite explain why.

What I eventually understood is that systems and routines aren't the same thing. A routine is a specific sequence of actions performed consistently. A system is a coordinated set of interconnected components designed to produce specific outcomes with the ability to adapt when conditions change. Both are useful. But they produce categorically different results, and understanding the difference lets you deliberately build what actually produces the outcomes you want rather than settling for what feels similar but doesn't.

I've written before in this newsletter about the value of consistency, discipline, and various learning practices. Those articles were true. But there's an important distinction I didn't fully address: consistency in a routine produces one kind of outcome. A coordinated adaptive system produces a categorically different kind of outcome. The learner who builds routines becomes reliably competent at whatever those routines produce. The learner who builds systems develops adaptive expertise that transfers across contexts and situations. Both are valuable. But they're not the same, and treating them as if they were leads you to build the smaller thing when you could have built the larger one.

Today's newsletter is about that. What the research actually shows about the specific difference between routine and adaptive expertise, why systems produce different learning outcomes than routines, and how to actually build systems rather than just routines for your learning. This is one of those distinctions that changes how you think about the structural work of learning across your life. Let's get into it.

From our partners at Jobstream:

Upgrade your daily content with fresh career opportunities curated for your community. Whether it is a "Day in the Life" or a weekly roundup, Jobstream™ lets you share real jobs, help your audience earn, and get paid when they apply. Join Jobstream™ and apply to become part of the Career Creator Network™.

Request Your Invite

Let me start with what the science actually shows, because the distinction between routine and adaptive expertise is more concrete than most learners realize.

According to research from the AAA Lab at Stanford, Figure 1 presents a framework for considering experiences that drive trajectories toward routine and adaptive expertise. Trajectory (R) proposes that students who begin instruction on an efficiency trajectory will have difficulty escaping the pull toward routine expertise. Trajectory (A) proposes that the path to adaptive expertise can begin with innovation efforts followed by the delivery and practice of efficient solutions and theories. Read this carefully. The specific finding: how you begin learning determines what kind of expertise you develop. Starting with pure efficiency (learning specific procedures to execute reliably) tends to trap you in routine expertise. Starting with innovation and exploration before efficiency tends to develop adaptive expertise. The trajectory matters. This has direct implications for how you design your learning practices.

The research on teacher development provides more detail. According to a 2025 study of 35,000 teachers, conceptual stages were developed to illustrate teacher progression from routine to adaptive expertise, measured on a four-point scale. The scale is introduced as a resource to support the integration of policy initiatives into actionable practices and professional learning. Read this. Progression from routine to adaptive expertise isn't automatic… it requires specific practices and specific development stages. Not every experienced practitioner develops adaptive expertise. Some remain at routine expertise indefinitely, executing what they know how to do without developing the capacity to handle novel situations. This is precisely the difference between having a routine and having a system.

The specific research on how routinization can undermine learning is worth understanding. According to a 2026 study on sustainable learning habituation, the framework offers actionable design implications, suggesting that e-learning environments for ESD should incorporate reflective prompts, task variability, learning analytics indicators, and metacognitive feedback mechanisms to prevent excessive routinization and support deeper sustainability-oriented engagement. Read this carefully. Excessive routinization actively prevents deeper learning. Pure routine execution (even of consistent good practices) can trap you in surface-level engagement without developing the adaptive capacity that genuine expertise requires. Learning systems need specific features that prevent routinization from becoming a ceiling on your development.

The research on adaptive learning systems in education provides one more useful framework. According to research on this, the framework distinguishes between three different methods. First, learner-controlled adaptive learning mechanisms allow the learner to apply the adaptation that is only suggested by an adaptive learning mechanism. Second, program-controlled adaptive learning mechanisms apply the adaptation automatically. Third, shared controlled adaptive learning mechanisms allow the learner to choose from a restricted set of options. Read this. The specific feature that distinguishes adaptive systems from mere routines is the presence of feedback and adjustment mechanisms. Systems adapt. Routines just repeat. Whether the adaptation comes from you, from external structures, or from a combination, the presence of adaptation is what makes something a system rather than a routine.

Let me name the distinction clearly, because it's the key insight of this whole newsletter.

A routine is a specific sequence of actions performed consistently. You do X, then Y, then Z. Same actions. Same order. Same frequency. Routines are valuable because they reduce decision fatigue, build automatic behaviors, and produce reliable execution. But routines don't inherently include mechanisms for evaluating whether they're working or adapting when they aren't. A routine that's not working continues being a routine until you deliberately change it… but nothing about the routine itself tells you when to change.

A system is a coordinated set of interconnected components designed to produce specific outcomes with adaptation mechanisms. A system includes the actions (like a routine) but also includes: specific goals the actions are designed to serve, feedback mechanisms that tell you whether they're serving those goals, evaluation processes that periodically check what's working, and adjustment protocols for when things need to change. Systems are designed to remain effective even as conditions change, because they include the specific machinery for adapting.

Same actions can be part of either a routine or a system depending on what surrounds them. Studying for 30 minutes every morning at 7 AM is a routine. Studying for 30 minutes every morning at 7 AM, tracking specific outcomes weekly, evaluating what's producing progress monthly, and adjusting the specific content or approach based on evidence is a system. The daily actions look similar. The larger structure around them is what makes one a routine and the other a system.

In Chrono Trigger, the party doesn't succeed through pure routine execution of the same tactics against every enemy. Each character has specific abilities that work in specific situations. Combining them requires understanding what specific combinations work against specific enemies. Adjusting mid-battle based on what's happening. The party's effectiveness comes from having the specific system of characters, abilities, and situational awareness… not from executing the same tactic reliably against everything. Your learning system works similarly. The specific coordinated components that let you adapt are what distinguish system from routine.

Let me name the specific ways systems and routines produce different outcomes.

Systems evolve with your development; routines don't. As you develop capability, what supports your growth changes. What worked when you were a beginner isn't what's optimal at intermediate levels. What's optimal at intermediate levels isn't what accelerates advanced development. Routines that stay the same across your development produce diminishing returns. Systems that adapt as you develop continue producing growth.

Systems catch problems early; routines don't. If your routine isn't producing results, you often don't discover this until significant time has passed. Systems include feedback mechanisms that surface problems while there's still time to adjust. This is one of the specific advantages of systems… they don't just execute; they check whether the execution is producing what was intended.

Systems handle context changes; routines fail with them. Life changes. Circumstances shift. What worked in your previous situation may not work in your current one. Routines built for specific conditions often collapse when those conditions change. Systems that include adaptation mechanisms can accommodate the changes and continue producing results.

Systems produce adaptive expertise; routines produce routine expertise. As the research showed, these are categorically different capabilities. Adaptive expertise transfers across contexts, handles novel situations, and continues developing across your life. Routine expertise handles what you've specifically been trained for and struggles with anything else. Which one you develop depends substantially on whether you're using routines or systems.

Systems compound across time; routines plateau. Because systems evolve and improve, they produce compounding benefits across long time periods. Each iteration builds on what previous iterations learned. Routines that stay the same eventually reach whatever ceiling they're capable of producing, and additional time in the routine produces limited additional benefit.

Systems integrate across domains; routines don't. A system for learning includes components that interact… your study practices, your reflection habits, your feedback mechanisms, your rest and recovery, your social engagement. These interact to produce learning outcomes. Routines tend to be siloed… one specific practice performed consistently in isolation from other practices.

Okay, the practical part. Here's how to actually build learning systems that adapt rather than just routines that repeat.

Start with the specific outcomes you want. Systems are designed to produce specific outcomes. Without clarity about what you're trying to produce, you can't design the system that produces it. What specifically do you want your learning to accomplish? Not vague topic mastery. Specific capabilities you want to develop. This clarity is the foundation the system builds on.

Include feedback mechanisms. Your system needs specific ways to know whether it's producing what you want. Weekly check-ins on progress. Specific measurable outcomes. External evaluation from people who can assess your capability. Without feedback, you can execute your routine indefinitely without knowing whether it's working.

Build in evaluation cycles. Periodically (weekly, monthly, quarterly), step back and evaluate what's actually happening. What's producing progress? What isn't? What should change? This evaluation isn't optional in a system. It's what makes the difference between a routine that keeps executing and a system that continues developing.

Design for adjustment. When your evaluation reveals something isn't working, you need protocols for adjusting. Not just noticing the problem… actually changing what you're doing. The specific mechanisms by which your practice can change over time are what make it a system rather than a routine.

Interconnect components. Your learning practices shouldn't exist in isolation. Your study practices connect to your reflection practices. Your reflection connects to your goal-setting. Your goal-setting connects to your practice design. The connections between components are what make it a system.

Include diversity of activity. As the research showed, task variability is one of the specific features that prevents excessive routinization. Your system should include some diversity (different types of practice, different contexts, different applications) not just the same routine repeated endlessly.

Design for your development stage. Your system should evolve as you develop. What's appropriate for a beginner isn't appropriate for an intermediate learner. Design the current version for where you are now, with the understanding that you'll redesign as you develop.

Include both efficiency and innovation. According to the research on adaptive expertise, systems that develop adaptive capability include both efficiency (learning to execute well) and innovation (learning to handle novel situations). Pure efficiency traps you in routine expertise. Pure innovation prevents you from developing reliable execution. Both are needed.

Build in maintenance. Systems degrade over time without maintenance. Regular attention to keeping the system functioning (not just executing within it) is what keeps it working across the years. This meta-level attention to the system itself is often what distinguishes learners with good systems from learners who once had systems that gradually decayed into routines.

Some honest caveats about what building a system doesn't require.

Systems don't require complexity. A good system can be simple. What makes it a system rather than a routine isn't complexity… it's the presence of feedback, evaluation, and adjustment mechanisms. Simple systems with these features outperform complex routines without them.

Systems don't require perfect execution. The point of a system isn't that you never miss a session or that every component works flawlessly. It's that the system as a whole continues producing results because it can absorb some execution failures and adapt.

Systems don't require sophisticated tools. You don't need special software or elaborate frameworks. A notebook with weekly evaluations can be part of a genuine system. Elaborate productivity apps can be dressed-up routines. The tools matter less than the underlying structure.

Systems don't work instantly. Building a system that actually functions takes time… usually weeks to months. Early versions won't have all the right components or the right adjustments. This is normal. The system develops through use, not just through initial design.

Not everyone needs elaborate systems. For some learning goals, simple routines are genuinely sufficient. The system approach matters most for long-term learning projects across years, complex skill development, or ambitious goals. For simple short-term learning, elaborate systems may be overkill.

Here's what I want you to take from all this. The word "system" gets used loosely in a lot of productivity and learning content. Sometimes people mean routine when they say system. But there's a specific difference between the two, and the difference determines what kind of expertise you develop, how long your practices continue producing growth, and how well you handle the inevitable changes in your circumstances.

If you've been building what you call systems that are actually routines, please consider that the missing features are what would make them systems. Adding feedback mechanisms, evaluation cycles, adjustment protocols, and interconnections between components transforms routines into genuine systems. The transformation isn't dramatic. It just requires adding specific structural features that most routines lack.

The specific practical move I'd suggest: audit your current learning practices honestly. Which are genuinely systems (with feedback, evaluation, and adjustment mechanisms) and which are routines without those features? For your most important learning project, add one specific system feature that's currently missing. Regular evaluation. Feedback mechanism. Adjustment protocol. Just one addition. Notice over the following month how it changes what your practice produces.

In The Matrix, Neo doesn't defeat Agent Smith by executing the same routine reliably. He develops the capacity to adapt in real-time to what Smith is doing, drawing on his training to respond to novel situations rather than executing predetermined sequences. This is the specific difference between routine and adaptive expertise. Neo's training was routine at first… learning specific moves. But eventually it became a system he could deploy adaptively, drawing on different components based on what the situation required. Your learning can work the same way. Start with routines. Evolve them into systems. The systems compound into capability that pure routine could never produce.

Keep learning (and keep building systems, not just routines),

Ray