Lesson Plan: The Business Fixer - Solving Real-World Problems with Computational Thinking

Materials Needed:

• Large whiteboard or several large sheets of paper
• Markers or pens in different colors
• A pack of sticky notes
• A stopwatch or phone timer app
• Computer with internet access for brief research (optional)

1. Learning Objectives (The Goal)

By the end of this 90-minute lesson, the student will be able to:

• Deconstruct a complex business process into its smaller, component parts.
• Identify patterns and inefficiencies within that process.
• Abstract away irrelevant details to focus on the core problem.
• Design a clear, step-by-step algorithm (a new process) to solve the identified problem.
• Communicate their proposed solution in a clear and persuasive manner, like a business consultant.

2. Alignment with Standards

This lesson aligns with key concepts from the Computer Science Teachers Association (CSTA) Standards for grades 9-12, particularly in the "Algorithms & Programming" and "Computing Systems" domains. It also connects directly to principles of Business Management and Entrepreneurship by focusing on process optimization and problem-solving.

3. The Lesson Scenario: The Coffee Shop Chaos (5 minutes)

Your Mission: You are a highly-paid business consultant. A popular local coffee shop, "The Daily Grind," has hired you. They have a problem: their coffee is great, but their morning rush (7:30 AM - 9:00 AM) is a total disaster. Customers wait too long, orders get mixed up, and the staff is stressed.

The owner has told you: "We're losing customers because our process is broken. Please, fix it!"

Your goal is to use your "Computational Thinking Toolkit" to analyze their process and design a better one.

4. Instructional Activities (The "How-To")

Part 1: Decomposition - "Breaking Down the Mess" (15 minutes)

Goal: To see all the moving parts of the problem.

1. On the whiteboard, write "Morning Rush Process" in the center.
2. Ask the student: "If we were filming a documentary about a single customer's journey from the moment they walk in to the moment they leave with their coffee, what are all the individual steps that have to happen?"
3. Have the student write each distinct step on its own sticky note. Encourage them to be as specific as possible.
   • Examples: Greet customer, Customer decides, Take order, Take payment, Write name on cup, Pass cup to barista, Grind beans, Steam milk, Pull espresso shot, Combine ingredients, Call out name, Customer picks up order, Add sugar/lid, Customer leaves.
4. Arrange the sticky notes in a rough chronological flow on the whiteboard. This visual map is the "decomposed" process.

Part 2: Pattern Recognition - "Finding the Bottlenecks" (20 minutes)

Goal: To find the weak points by looking for patterns of delay or repeated effort.

1. Look at the sticky note map. Ask probing questions:
   • "Which of these steps seems like it would take the longest?"
   • "Where could a mistake happen that would force steps to be repeated?" (e.g., wrong order taken).
   • "Are there any patterns here? For example, is there one person (the cashier) who is a bottleneck because too many steps depend on them?"
   • "Think about tasks that can happen at the same time. This is called 'parallel processing'. Could the barista start steaming milk while the customer is paying? Is that happening now?"
2. Let's simulate! Use the stopwatch. "Let's guess how long each step takes. Taking an order: 30 seconds. Paying: 45 seconds. Making a latte: 2 minutes." Time a few of the key steps to see how a single order could take over 3-4 minutes. Now, what happens when there are 10 people in line? This reveals the pattern of cascading delays.
3. Have the student use a red marker to circle the 2-3 steps on the board that they identify as the biggest "bottlenecks" or problem areas.

Part 3: Abstraction - "Ignoring the Noise" (10 minutes)

Goal: To simplify the problem by focusing only on what's essential for a solution.

1. Point to the board and say: "To solve the wait time, do we need to worry about the brand of coffee beans they use? The color of the walls? The music playing?" (The answer is no).
2. "This is abstraction—we are ignoring irrelevant details to focus on the core structure of the problem. Our core problem is the sequence of tasks and the allocation of staff."
3. Ask the student to state the problem in a single, abstracted sentence.
   • Example: "The linear, single-threaded process for taking and making orders is too slow to handle the volume of customers during the morning rush."

Part 4: Algorithm Design - "Creating the Perfect Workflow" (25 minutes)

Goal: To build a new, efficient process (an algorithm) that solves the problem.

1. Clear a new space on the whiteboard. Title it "The New & Improved Rush Hour Algorithm."
2. Challenge the student: "You have two employees: a Cashier and a Barista. Design a new step-by-step process. Your goal is to serve customers as fast as possible. Think about how the two employees can work in parallel."
3. Have the student use sticky notes again, but this time create two columns: "Cashier's Tasks" and "Barista's Tasks."
4. Guide them to build a workflow where tasks are happening simultaneously.
   • Example: While the Cashier is taking Customer #2's order, the Barista is already making Customer #1's drink. The cashier can take the payment for Customer #2 while also passing the cup for their order to the Barista to get it in the queue.
5. Encourage creative solutions: What if there's a separate station for simple drip coffee so customers can self-serve? What if they take payments via a mobile app to speed up the line?
6. The final result should be a clear, visual diagram of the new, more efficient algorithm.

5. Assessment & Synthesis (The Consultant's Pitch) (15 minutes)

Goal: To synthesize and communicate the solution effectively.

• The student will prepare a 3-minute verbal "pitch" to you (acting as the coffee shop owner).
• The pitch must include:
  1. A clear statement of the problem they identified (using their abstraction sentence).
  2. A brief explanation of the key bottlenecks they found (pattern recognition).
  3. A walkthrough of their new, improved algorithm, explaining why it's better (e.g., "by having the cashier focus only on orders and payment, and the barista work on a queue of drinks, we can reduce the average customer wait time by an estimated 40%").
• Feedback: Provide feedback based on the clarity of the explanation and the logic of the proposed solution. Was the new algorithm easy to understand? Did it logically solve the identified problem?

6. Differentiation and Extension

• For extra support: Provide a pre-filled list of the decomposed steps and focus more time on the pattern recognition and algorithm design phases. Work together to map out the first version of the new algorithm.
• For an advanced challenge: Introduce a new variable, like "a new, untrained employee starts today," and ask how the algorithm would need to change. Or, ask them to calculate the potential financial benefit of their new algorithm (e.g., "If we can serve 20 more customers an hour at an average of $5 per order, what's the increase in revenue?"). Have them apply the same four CT steps to another business problem, such as "improving an online store's checkout process" or "optimizing a pizza delivery route."