I’ve been trying to work on developing a instructional routine that I can pass on to the other instructors in our introductory college physics course. The instructional routine pertains to getting students engaged in problem-solving, and is intended to give them an alternative process to our Department’s typical routine.

So what’s our typical routine? Our typical routine, which certainly isn’t horrible, is “Example Problem –> Whiteboard Problem”. That is, the instructor poses a word problem, models how to solve the word problem, and then students are posed a similar word problem and are asked to solve it collaboratively on whiteboards, following the general process. This can go pretty well or pretty so-so depending on a lot of the details, but one of the biggest pitfalls can be this:

• The process can put students into “Monkey see, Monkey do” mode, where they expect to mindless follow the algorithm their teacher teaches them.

So here’s the basic routine I’ve been working on (for which there are many variants),

First: Posing the Qualitative Scenario (with or without a question)

An example might be, “If we go outside and throw a ball as hard as we can, will it go high enough to get on top of the roof?”

Second: Making the Scenario a Problem

The qualitative scenario begs the question, “It depends”, so in the routine you typically ask students to think about what it depends on. It helps me to explicitly ask, “What information would we want to know about the situation to help decide?”

For the situation with throwing the ball above, I have gotten the following:

• How tall the building is?
• How tall the person is?
• How fast the person throws the ball?
• What the weather conditions are?
• What type of ball is being thrown?

The instructor’s job is to “catch every contribution” and to either press the student connect it to disciplinary constructs or to offer a connection. One can ask follow ups, such as “Can you tell us why you think the height of the person matters?”, or weigh in yourself (e.g., “Yeah, that makes sense, a taller person might have an easier time getting).  In the above scenario, we had just talked about the conditions for free-fall, so I helped to offer the last two as information that would help us to know whether the conditions were or were not consistent with free-fall assumption. Depending on how much scaffolding you want at this time, you might connect each of those to constructs you’ve talked about like, “initial velocity”, “initial position”, but you might not.

The next task is to decide how that information will be gathered. I suggest one of three things can be done (or even some combination)

• Estimating (e.g, how fast does a car go on a typical highway)
• Measuring (e.g., using photogate to measure launch velocity.”
• Researching (e.g., what are typical car braking accelerations.)

For the example above, I asked students to estimate the building height, person height, and initial velocity, and to also come up with a specific ball / weather that they think would be fairly consistent with free-fall. This is a good exercise in estimating but also in understanding the assumptions that go behind a particular model.

Students in my class, did a mix of estimate and measure. They measured the height of our room and used knowledge of how many floors to estimate the building height. Other groups used knowledge of baseball pitching speeds in mph to come up with a reasonable “normal person vertical speed.”, but others looked up information for “how fast can humans throw stuff.”

If students are to work the problem, the instructor can choose to have the class all work the same problem (get consensus on good estimates), or let groups work with different estimates. This day, we did a consensus problem:  1meter tall person, 20 meter tall building, 25 m/s throw, a baseball (not a ping pong ball), and no wind / no rain. I chose this day to do the unit converting for them from their speed estimate which was in mph, but I wouldn’t always do this. I also directed us to the specific question of, “How high above or below the roof height does the ball get?” so that it wasn’t just “yes or no”.

The truth is the whole setup process can be fairly quick (or stretched out) depending on needs. Even just giving students a 1-2 minutes to chat in groups, collecting their ideas at the board and quickly connecting it to disciplinary constructs, goes a long way for students to orient to the situation and understand the relevance of the information. You might quickly take measurements for students, or involve them in a process of measuring that information that takes significant time. It all depends. The point is to spend sometime turning the situation and question into a problem, and along the way practice some other skills such as estimation, measurement, making assumptions, etc. It need not be everything.

Solving the Problem: Creating and Using a Model

In my mind, the above steps play out well whether you are going to model how to solve a problem or have students solve the problem. In my class, students had already solved 1D acceleration problems, and we had just finished activities and discussion about free fall, so students were ready to jump into problem solving. In my class, they have to make motion diagrams, both qualitative position and velocity diagram, and then either write equations that describe those graphs, or use slope/area ideas.

There can be some advantages to all doing the same numbers, especially for a more novice instructor. You can more readily scan the room and compare students’ progress, and students can more readily compare their answers.

There are also good advantages to having different numbers out there. For example, if students choose different speeds, then you might be able to discuss how the speed seemed to effect the maximum height reached.

You can also deliberately seed some good comparisons — two groups both do 1m and 2m tall persons with the same speed, or 10 m/s, 20 m/s, 30 m/s throwing speeds.

Evaluating and Re-Posing

At the end, we want students to evaluate the reasonableness of their answer. This can be done in variety of ways. Depending on the type of scenario you are posing, you might be able to compare to experiment. One trick for doing this can be to ask students early on, maybe even before even posing the situation, “What do you think is highest height a ball can be thrown up to? What’s a height you know is too high? What’a a height you know is too low?” That way they can compare their final answer to the bounds they previously set as reasonable.

This last step also gives quick students more and more places to go while other groups finish up. I also have one of my quick groups write simulations in desmos, as part of their modeling process.

Summary of the Routine:

Certainly, you could choose to invest a lot of time in having students fully engage in all the steps, but that’s not necessary. The point is to always engage the whole process, but students can carry more of the responsibility for some parts, you can carry more the responsibility for other parts. But here are the four main parts I see.

1. Interest Making
2. Problem Making
3. Modeling Making
4. Sense Making

I say the first one is “interest making” is because showing students actual situations or qualitative situations should be done in a manner as to possibly cultivate an inkling of engagement and curiosity about the situation. I’m not saying it needs to be magical.

The second one is “problem making”, because it’s about turning that situation into a problem by discerning relevant information, relating it to physics concepts. This is the core of the practice that I want students to get more practice with, and is the one that word problems are the worst at skipping.

The third one is to modeling making, because everyone is to develop and apply a model that can be used to solve the problem. This is what we typically think of as problem-solving, and this is going to look different in different classrooms, curricula, etc.

The last one is sense-making about returning to think about the outcome, the model, rethink the situation, and even new situations. In a sense, the end process puts you back at the beginning of posing situations and asking questions, so you come full circle. There are lots of different ways of sense-making, but it needs to be an explicit part of the process, and it needs to be more than, “Does your answer make sense?”

Challenge: Make it Simple, Imaginable, and Flexible:

The issue I see with any instructional routine is having it crafted as simple enough for an instructor to get started with it. They need to be able to not just follow the steps, but have a feel for the purpose of each step, and probably have a good image / sense of what it can look like. You don’t want to get bogged down in all the possible variations at first, but have it possible that flexibility will open up through practice. I got to figure out what’s the a good “touchstone” example for this routine is.

Sorry for the ramble, just getting down my thoughts.

## 2 thoughts on “Instructional Routine: Problem Solving”

1. Andy "SuperFly" Rundquist says:

First, don’t apologize for rambling, this stuff is gold!