What this game teaches: Systems thinking through automation and scale.

Welcome to Save Point, where we hit pause each week to examine one game in depth.

I’m coming out swinging with this title. If you’ve never heard of Factorio, have a seat. I called this Part I before I even started writing because this game has a rich and rewarding system worth multiple deep dives.

Factorio is, in my opinion, the ultimate supply chain, resource management, and automation simulator. Since it’s more simulator than traditional game, you can make it whatever you want. Some players race to escape the planet. Others build the largest base possible. Some maximize throughput and efficiency down to the belt. I can, and likely will, write extensively about this game. For now, I’ll stick to the fundamentals, which is still plenty.

The Moment It Clicked

I was connecting a double-track rail line to a uranium mine. Sulfuric acid needed to come in by train. Uranium ore needed to go out for refinement into Uranium-235 and Uranium-238. That refined uranium would eventually become Uranium fuel cells to power my nuclear reactor.

That’s when it hit me: This is a legitimate supply chain simulator, and I’m automating some genuinely complex systems.

Factorio is effortlessly complex in the best way.

What You’re Actually Playing

Factorio is an automation and base-building game with simple yet detailed graphics that keep your focus on system design rather than visual spectacle. When you start, the game presents your main objective clearly: build a rocket and escape this planet.

Problem is, you don’t have much to work with. Your ship is unsalvageable, only good for a few scrap pieces of metal. So you start Minecraft-style: whacking the ground with a pickaxe until you gather raw stone, copper, iron, and coal. This takes a couple minutes.

With these resources, you craft your first smelters and drills. Smelters turn raw ore into copper and iron plates. Those plates become conveyor belts, inserter arms, and assembly machines.

This is where the game truly begins.

The Scale of the Challenge

Your job is to research and construct the technologies needed to escape. Doing so requires producing items at a massive scale.

To launch just the rocket (not counting research or the factory infrastructure):

  • Iron Ore: ~75,000 units
  • Copper Ore: ~55,000 units
  • Coal: ~45,000 units
  • Crude Oil: ~10,000 units (for plastic and fuel)

This is an immense amount of resources. It doesn’t even include everything needed to build the factory that produces these outputs.

Consider this: if you have only one drill extracting iron ore, it would take over 80 hours just to pull the raw materials from the ground, assuming the patch doesn’t run out first. Most ore patches contain only a few thousand units. The one near your starting location? Maybe 1,800 iron ore before it’s depleted.

To construct a factory capable of launching a rocket, you need roughly half a million raw units of ore, coal, oil, and stone. Most players extract millions because they’re doing far more than chasing the main objective.

Doing this by hand would take years. With automation, you can do it in hours.

This is the core reward cycle of the game.

The Beautiful Complexity Loop

The cycle looks something like this:

You realize you need more Green Science to research batteries, which will help you move and build faster. Green Science requires one inserter and one transport belt per pack. Each of those requires iron plates and copper plates.

Then you realize your current copper ore patch is already being drained at maximum capacity. The next closest patch is very far away, requiring an unreasonable number of transport belts to bring in sufficient raw ore.

So you pivot. You start researching railways and begin smelting steel plates since you have excess iron ore capacity. Before you know it, you have a steady flow of steel coming out, which lets you automate rail production. You set up a small assembly hub to create engine units, and suddenly you have hundreds of rails, a couple locomotives, and some cargo wagons.

Now you can cover the roughly 4 million square kilometers the game offers with actual efficiency.

But extraction is only half the battle. You need to assemble components into useful products, and this is where structure matters most. In fact, this is probably the most debated part of the game:

  • How should I organize my belts, inserters, and assembly machines to scale with high throughput?
  • How should I organize train networks to avoid gridlock?
  • Do I build single-track railways now, or invest in double-track infrastructure from the start? Slowing initial expansion but ensuring future scalability?

The cycle repeats:

  1. Identify what needs to scale next
  2. Trace back all the resources required
  3. Organize those resources to produce even more useful outputs
  4. Repeat

What Factorio Actually Teaches

System Design

This game forces you to live with the results of your design decisions. Good systems reward you with rapid outputs and easy scalability. Poor systems punish you with bottlenecks and painful rework.

By testing different approaches, you quickly gain appreciation for principles that great software and systems engineers preach: modularity is paramount. Building for scalability rewards you later but demands heavy up-front investment, and sometimes doesn’t even scale well when newer technologies unlock.

Trade-Off Evaluation and Prioritization

What may be less obvious is a critical skill: weighing trade-offs and deciding priorities.

Do I build more smelters for copper or iron? You can’t do both simultaneously. Which helps speed production more in the short run? Which pays off long-term? Do I design something small now and tear it down later, or do I start with scale in mind from the beginning?

These decisions shape your success. Games like Factorio build intuition for product development. You gain a visceral sense of how well (or poorly) decisions scale, and the cost of building for scale from day one.

Agile Development Thinking

After a couple restarts, you learn to balance future scale with current capabilities. You discover that it’s often better to build entire V1 systems, then completely destroy them for V2 when new technology unlocks. With experience, you find creative ways to keep V1 running while you build and integrate V2.

This perfectly mirrors agile product development:

  1. Understand the need
  2. Build for the need quickly
  3. Observe what works well
  4. Try to understand why or why not, then scale
  5. Monitor the solution and seek to understand new needs
  6. Repeat

By playing games like Factorio with purpose, you’re building mental muscles and learning frameworks for constructing and iterating on complex systems.

Age Rating & Where to Find It

Official ESRB Rating: E10+ (Everyone 10+)

John Rating: 8+ — No blood, no language, no concerning content. Genuinely kid-friendly and educational. One of the best games for teaching systems thinking to younger players.

Steam Link: Factorio on Steam

Skill Snapshot

  • Core Skill: System Design
  • Also Builds: Trade-Off Evaluation, Prioritization, Resource Flow Analysis
  • Mental Models: Agile Development, Constraint Theory, Modular Architecture
  • Fastest Learning: Automation workflows and bottleneck identification
  • Deepest Learning: Different scalable frameworks for different constraints

The Scorecard

Category Score
Fun 10/10
Educational Value 10/10
Learning Curve 5/10 (higher is easier)
Replayability 9/10
Skill Transfer 10/10
Time Investment 6/10
Total 50/60

Addictive. My friends who downloaded it all have hundreds of hours now. Teaches system design, resource management, and strategic thinking through direct feedback. Simpler than it sounds, but still complex. Easy to start, years to master. Different objectives and the sheer scale possibilities bring players back repeatedly. You literally build supply chain systems that adapt to changing needs. Directly applicable to product and operations work. Early on you can play in short bursts, but after 5–10 hours you’ll want 2–3 hour sessions minimum.

Optional Bonus — Team Learning: +8/10 Multiplayer is exceptional (I’ll cover this in another article).

JOHN SCORE: 58/60 — Excellent game, time well spent.

What This Builds In You

Factorio trains you to spot bottlenecks before they happen. You learn to trace resource flows backward, identify the limiting constraint, and redesign systems for throughput.

In product development, this shows up as the ability to spot where teams will collide, where technical debt will compound, and where a small architectural choice will either enable or block everything downstream.

You start seeing the world as interconnected systems with inputs, throughput constraints, and outputs. You develop an instinct for where leverage points exist, where a small change creates disproportionate impact.

Verdict

Play this if you want to:

  • Learn how to think in systems and scale
  • Build better products and processes faster
  • Understand supply chain dynamics viscerally
  • Play with trains

Skip this if:

  • You don’t have time for longer gaming sessions (30-minute bursts won’t get you far)
  • You want to learn physics, history, or narrative-driven content
  • You prefer action-oriented gameplay over strategic thinking

Best Played:

  • Solo: When starting out, everyone should grasp core mechanics before multiplayer
  • Co-op/Team: When everyone can commit to a schedule for building a mega base (and eventually exploring the solar system in the DLC). Think: “Every Tuesday 7–9 PM.”

Recommended session length: 1–4 hours

Final Thought

The best games don’t just kill time. They compress years of pattern recognition into hours of deliberate play.

Factorio does this better than almost any game I’ve encountered. You’re not just playing. You’re training your brain to see systems, identify constraints, and build solutions that scale.

If you’ve been on the fence about trying it, now’s the time. Fire up Steam, grab the demo, and give yourself permission to disappear into factory optimization for a weekend. Your future self, the one managing complex projects and building scalable systems, will thank you.

See you in Part II, where we’ll dive into Rail Systems, Logic Circuits, and the multiplayer.

Until then, keep building.

— John

Next in this series: Apex Legends Builds Teamwork & Communication

Subscribe to Gaming Is Good if you want to learn which games actually make you smarter.