Skip to main content

Week 2: The Computer Control Room

Computers as Systems (Inputs, Actions, Windows, Apps)

Last week we explored the internet as a giant network of people and information.

This week we turn our attention to the computer itself.

The big idea for this week:

Computers respond to inputs.

When we:

  • click
  • type
  • drag
  • press keys

the computer reacts.

This week helps the student begin thinking about computers as systems that respond to actions, rather than mysterious machines.

Facilitator Snapshot
  • You do not need to teach every bullet on the page. Use the learning goal and one or two activities for the session you are teaching today.
  • If time is short, teach one guided session well and leave the rest for later. The lessons are designed to stretch across the week.
  • The independent session works best after the learner has already explored the main idea with you once.
Quick Navigation

Facilitator Preparation​

Before You Begin
  • Time needed: ~30–40 minutes per guided session, ~30 minutes for the independent session.
  • Devices needed: One computer (desktop or laptop) with a mouse or trackpad.
  • Accounts needed: None. All activities use built-in apps.
  • Ensure a few simple apps are easily accessible:
    • Calculator
    • Paint or Paint 3D (Mac: Preview's markup tools or Paintbrush; Chromebook: Chrome Canvas or any free drawing app)
    • Notepad or a simple text editor (Mac: TextEdit, Chromebook: any text app or Google Docs)
  • Prepare a quick explanation of inputs and outputs.
  • Be ready to demonstrate opening and moving windows.
  • Have paper or a whiteboard available for quick diagrams.
  • Set up a visual timer for sessions.
Teaching Mindset

The goal is not memorizing buttons.

The goal is helping the student notice cause and effect:

"When I do this… the computer does that."

Week at a Glance​

Learner Goal​

I can make the computer do something on purpose and explain which input caused the result.

Materials​

  • computer with mouse or trackpad
  • two or three simple built-in apps
  • paper or whiteboard for quick input/output diagrams

Quick Formative Check​

Before opening apps, ask: "What do you think will happen if I click here, drag this window, or press this key?" Then test one prediction together.

What Success Looks Like​

  • The learner can describe a simple input and the computer's response.
  • The learner can open, move, or close an app with growing confidence.

Low-Tech / Offline Option​

Act out a "human computer" game where one person gives inputs and the other person must respond exactly as instructed.

Guided Session 1​

Inputs and Reactions​

Learning Goal​

By the end of this session, the student can:

  • analyze the cause-and-effect relationship between an input and a computer's response
  • predict and test how changing an input changes the result
  • design a small input experiment to show how people control computers

Activities​

1. What Makes a Computer Do Something?

Ask the student:

“How do you make a computer do something?”

Let them experiment.

Try things like:

  • moving the mouse
  • clicking
  • pressing keys
  • opening the start menu

Explain that these are inputs.

Draw a simple diagram together:

Input → Computer → Result

Examples:

  • Click icon → App opens
  • Type letter → Letter appears
  • Press Enter → New line appears

Explain that computers are very fast at following instructions.

2. The Computer Control Room Idea

Explain:

“Using a computer is like being in a control room with lots of buttons.”

Each button, click, or key press tells the computer what to do next.

Encourage the student to try different inputs:

  • Single-click an icon (selects it)
  • Double-click an icon (opens it)
  • Right-click something (a menu appears with options)
  • Drag an icon from one place to another
  • Scroll using the mouse wheel or trackpad (the page moves up and down)
  • Open the start menu
  • Press different keys
  • Move windows around

Observe together what happens.

Name each action as you do it so the student builds vocabulary for what they are doing.

3. Small Input Experiments

Try a few playful experiments:

Examples:

  • What happens if you press Enter in Notepad?
  • What happens if you press Backspace?
  • What happens if you drag an icon?
  • What happens if you scroll on a long web page?
  • What happens if you double-click a word in Notepad? (It selects the word!)

Ask the student to predict the result before trying it.

This builds early computational thinking.

4. When Something Goes Wrong: The Troubleshooting Mindset

During experiments, something may not work as expected. Use that moment to introduce a simple idea:

"When something doesn't work, we don't panic. We stop, think about what happened, and try one small thing."

This is the beginning of a troubleshooting habit that will grow throughout the curriculum. For a printable step-by-step routine, see the Troubleshooting Routine.

Reflection Questions​

  • “Which input led to the biggest change on the computer, and why?”
  • “How could you explain the cause-and-effect pattern you noticed today?”
  • “What new input experiment would you design if you wanted to test the computer again?”

Sentence starters for younger learners:

  • “When I clicked on…, the computer…”
  • “I was surprised that pressing… made…”

Guided Session 2​

Windows and Apps​

Learning Goal​

By the end of this session, the student can:

  • evaluate which app is the best tool for a specific job
  • organize multiple windows to create an effective workspace
  • justify how their choice of apps and window arrangement supports a task

Activities​

1. What Is an App?

Explain that apps are tools for different jobs.

Examples:

  • Calculator → math tool
  • Paint → drawing tool
  • Notepad → writing tool
  • Browser → exploring the internet

Ask the student:

“What kind of tool do you think each app is?”

2. Window Exploration

Open two apps together, for example:

  • Calculator
  • Paint 3D

Point out the window parts:

  • title bar
  • minimize
  • maximize
  • close

Then experiment:

  • move windows
  • resize them
  • minimize one
  • bring it back

Explain that windows are like workspaces on a desk.

You can move them around to make room.

3. Window Puzzle Game

Open three different apps.

Ask the student to:

  • arrange them side-by-side
  • move one behind another
  • bring one to the front

This builds intuitive understanding of multitasking.

Reflection Questions​

  • “How did you decide which app was the best tool for a job?”
  • “What window arrangement helped you work most effectively, and why?”
  • “If someone else needed to multitask, what advice would you give them about using windows?”

Sentence starters for younger learners:

  • “The best app for that job would be… because…”
  • “I arranged my windows by…”

Independent Session​

Control Room Explorer​

Instruction​

Spend time exploring the computer like a control room operator with a plan.

Open three different apps and compare them.

As you explore, ask yourself:

  • What job does this app seem designed to do?
  • Which inputs make the biggest changes?
  • How is this app different from the others?

Then choose one app and create a short explanation, drawing, or demonstration that shows:

  • what the app is for
  • which controls mattered most
  • one thing you discovered by experimenting

Skills Reinforced​

  • analyzing how different inputs change computer behavior
  • evaluating apps as tools for different tasks
  • organizing windows to support a task or workflow
  • reasoning about cause and effect in digital systems

Setup​

  • Start menu accessible
  • a few apps easy to find
  • visual timer

🔄 Simplify or Extend​

To simplify:

  • Limit exploration to just two apps (e.g., Calculator and Paint) instead of three.
  • Focus on single-click and drag actions before introducing right-click or window management.

To extend:

  • Challenge the learner to arrange three windows so they can see all of them at once and explain their layout choice.
  • Ask the learner to write a short “instruction manual” entry for one app, describing what it does and how to use it.

💾 Save This Week’s Artifact​

Take a screenshot of the learner’s desktop with their arranged windows or a drawing/diagram they made showing the input → computer → result pattern. Save it to the learner’s portfolio folder. This will become part of their collection of work that builds toward the final project.

Check for Understanding​

By the end of this week, look for whether the learner can:

  • Use a mouse or trackpad to single-click, double-click, drag, right-click, and scroll with growing comfort
  • Open and close at least two different apps on their own
  • Move, resize, minimize, and restore windows without step-by-step help
  • Explain in their own words that computers respond to inputs and produce results
  • Predict what will happen before trying a new input (e.g., "I think clicking this will…")
  • Identify which app is the right tool for a given task (e.g., "I'd use Paint to draw")
  • Respond to a small problem by pausing and trying one thing before asking for help
Vocabulary This Week

Input • Output • App (application) • Window • Single-click • Double-click • Right-click • Drag • Scroll • Minimize / Maximize / Close
See the Glossary for definitions.

Preview of Next Week​

Next week, students discover how computers store their work as files organized into folders — learning to save, rename, and find their own digital creations so nothing ever gets lost.