Teaching Plan It, Test It, Improve It in Grade 5: Oklahoma Standard 5.AP.PD.01

Teaching program planning in grade 5 does not have to be complicated. Picture an app studio running testing sessions and revising a prototype many times before launch. That kind of thinking is exactly what Oklahoma's grade 5 computer science standard 5.AP.PD.01 asks students to practice — and it is very teachable with the right materials. This post walks through what the standard means, the misconceptions students bring to it, and discussion starters you can use tomorrow, whether you teach in a classroom or at your kitchen table.

What Does Standard 5.AP.PD.01 Actually Ask?

Use an iterative process to plan the development of a program that includes others' perspectives and user preferences while solving simple problems. — Oklahoma Academic Standards for Computer Science (February 2023)

In plain language: Oklahoma's standard asks fifth graders to plan a program step by step using an iterative process, while including other people's points of view and the preferences of the people who will actually use it, to solve a simple problem.

In student-friendly terms, the learning target is: "I can use an iterative process to plan a program that solves a simple problem, including other people's perspectives and the preferences of the users I am building for."

What Students Should Be Able to Do

• I can write a clear plan that states the problem before I start coding.
• I can identify my audience and design for their perspective, not just my own.
• I can gather user preferences with a survey and use them in my plan.
• I can use feedback to revise a prototype and explain how testing makes my program better.

Along the way, students pick up the working vocabulary of the topic: revise, improve, design, feedback, survey, program, testing, prototype, preference, iterate, audience, plan.

Program Planning: Misconceptions to Watch For

These are the wrong turns students reliably take with this standard — knowing them ahead of time is half the lesson plan. Each correction strategy below comes straight from the unit's teacher guide (the paragraph and activity references point into the unit itself).

1. "A program should be designed for whoever writes the code."

Return to paragraph 3: programs are built for an audience. Have students name a design choice that is obvious to them but would confuse a kindergartner or an elderly user, then connect it to including others' perspectives.

2. "Planning first is a waste of time; it is faster to just start coding."

Use paragraph 2's builder-without-blueprints image. Ask students to estimate the time to fix a mistake on paper versus in finished code, reinforcing that planning saves time overall.

3. "Feedback that points out problems means the project failed."

Paragraphs 5-6 reframe feedback as a gift. Every problem a tester finds is one that can now be fixed before release. Watching users struggle is information, not failure.

4. "The first version of a program should already be perfect."

Use the bicycle-steering analogy in paragraph 7. Professionals iterate through many cycles; the goal is steady improvement through revision, not instant perfection.

Discussion Starters You Can Use Tomorrow

• Think of an app or game you use. What is one thing about it that feels designed for a different kind of user than you?
• Why might two different users prefer completely different settings in the same program? How could a developer satisfy both?
• Describe a time you improved something by trying it, getting a comment, and changing it. How was that an iterative process?

Bringing It Home

This topic is a natural one for families. One ten-minute activity to try: Pick a small family task that could work better, like a morning routine or a chore chart. Ask your child to 'plan it like a programmer': state the problem, ask each family member what they prefer, sketch a quick version, get everyone's feedback, and revise it once. The goal is to experience one full iterative cycle together.

Where This Leads

Students who can use an iterative process to plan a program that solves a simple problem, including other people's perspectives and the preferences of the users I am building for are building skills used every day in software development, user experience design, game design, product management, and engineering.

Part of the Complete Grade 5 Computer Science Curriculum

This lesson covers just one standard. It is part of a complete grade 5 computer science curriculum aligned to every Oklahoma OAS CS standard. See the full listing — every standard, organized by strand — here: Grade 5 Computer Science Curriculum: Every Oklahoma OAS CS Standard.

See the Unit in Action

Get the Complete 5.AP.PD.01 Unit

I built a complete, no-prep unit for this standard — Plan It, Test It, Improve It: Designing Programs for Real Users — covering 3-4 days of instruction across 40 pages:

• Teacher guide — day-by-day pacing, misconceptions to watch for, discussion questions, differentiation for support / ELL / extension, and a 4-point rubric
• Student learning target page — a kid-friendly "I can" statement with success criteria
• Full content lesson with 3 embedded "Check Your Understanding" checkpoints
• 12-question assessment (6 multiple choice, 4 true/false, 2 short answer) with a complete answer key, explanations, and exemplar responses
• Group activity — "Design It for Them: A User-Centered Planning Challenge" (25-30 minutes)
• Individual activity — "My Iteration Journal" (15-20 minutes)
• Crossword and word search built from all 12 vocabulary terms (with answer keys)
• Family connection letter — a plain-language page for parents, with dinner-table questions and a 10-minute home activity
• Certificate of achievement — ready to sign and send home
• Design Challenge Cards (separate printable, 2 pages)
• Iterative Planning Reference Sheet (separate printable, 2 pages)
• My Iteration Journal (separate printable, 1 page)

Get Plan It, Test It, Improve It on Teachers Pay Teachers →

Also aligned to CSTA 1B-AP-13: Use an iterative process to plan the development of a computational artifact, introducing planning, testing, and refinement.

Every Sooner Standards resource is built directly from the official Oklahoma Academic Standards for Computer Science (February 2023) — standard text verified, never paraphrased from memory.