Robotics Activities

Apply your knowledge through hands-on maker projects, design challenges, and real-world case study analysis

🛠️ Individual Maker Projects

Hands-on projects to build your robotics skills. Progress from paper prototypes to working robots.

1

Paper Robot Prototype

Design and build a robot prototype using paper, cardboard, and simple mechanisms. Focus on form, movement, and interaction without electronics.

Objectives:

  • Form Design: Create compelling robot appearance and personality
  • Movement Planning: Design mechanical movement patterns
  • Interaction: Consider how humans will interact with this robot
  • Documentation: Record design rationale and iteration

Materials Needed:

  • Cardboard, paper, foam core
  • Scissors, glue, tape
  • Markers for decoration
  • Brass fasteners for movable joints
  • String or elastic for simple mechanisms

Step-by-Step Guide:

  • Define Purpose: What will your robot do? (deliver objects, greet people, clean, etc.)
  • Sketch Ideas: Draw 3-5 different robot forms from different angles
  • Choose Design: Select one design and refine it
  • Build Structure: Create main body using cardboard
  • Add Movement: Use brass fasteners for rotating joints, test range of motion
  • Add Personality: Details like eyes, color, shape convey character
  • Test Interaction: Have someone interact with your robot, observe what works
  • Iterate: Make improvements based on testing
  • Document: Photo and describe your design decisions

Reflection Questions:

  • How does your robot's form communicate its function?
  • What personality does your robot have? How is it conveyed?
  • What movements are most important for your robot's task?
  • If you were to add electronics, which sensors and actuators would you need?
2

Build an Arduino Line-Following Robot

Step-by-step guided project to build your first working robot using Arduino. Learn sensors, motors, and basic programming.

What You'll Learn:

  • Component Assembly: Connecting sensors, motors, and microcontroller
  • Sensor Reading: Using infrared sensors to detect lines
  • Motor Control: Programming differential drive for steering
  • Logic Programming: If-then rules for robot behavior

Required Components:

  • Arduino Uno board
  • Motor driver shield (L293D or similar)
  • 2x DC motors with wheels
  • 2x IR line sensors
  • Robot chassis (or build from cardboard)
  • Battery pack (6V or 9V)
  • Jumper wires

Build Instructions:

  • Assemble Chassis: Attach motors to robot base
  • Mount Arduino: Secure Arduino and motor driver to chassis
  • Wire Motors: Connect motors to motor driver outputs
  • Attach Sensors: Mount IR sensors at front, facing down
  • Connect Sensors: Wire sensors to Arduino digital pins
  • Add Power: Connect battery pack to motor driver
  • Upload Code: Program basic line-following logic
  • Create Track: Use black tape on white surface to make a path
  • Test & Tune: Adjust sensor position and code for best performance

Basic Code Logic:

  • Read left and right IR sensors
  • If both sensors see the line → go forward
  • If left sensor sees line, right doesn't → turn left
  • If right sensor sees line, left doesn't → turn right
  • If neither sensor sees line → stop or search

Customization Ideas:

  • Add speed control to make smoother turns
  • Implement more sophisticated search behavior when line is lost
  • Add LEDs to indicate robot state
  • Create obstacle detection with ultrasonic sensor

Resources: Tutorial code and wiring diagrams available at Arduino.cc project hub.

3

Robot Context Design

Design a robot for a specific context or use case. Create concept sketches, specifications, and interaction scenarios.

Choose Your Context:

  • Hospital patient care robot
  • Museum guide and information robot
  • Classroom teaching assistant robot
  • Retail customer service robot
  • Home elderly companion robot
  • Or define your own specific context

Design Process:

  • Research Context: Understand the environment, users, and needs
  • Define Requirements: What must the robot do? What constraints exist?
  • Design Form: Sketch robot appearance considering context expectations
  • Plan Behaviors: What actions and reactions should the robot have?
  • Select Components: Which sensors and actuators are needed?
  • Map Interactions: How will people interact with this robot?
  • Consider Ethics: What could go wrong? Privacy, safety, job displacement concerns?
  • Create Specification: Document your complete robot design

Deliverables:

  • Concept Sketches: Multiple views of robot design
  • Interaction Scenarios: 3-5 use cases with illustrations
  • Technical Specification: Sensors, actuators, capabilities list
  • Behavior Description: How robot responds to different situations
  • Ethics Assessment: Potential concerns and mitigation strategies

Evaluation Criteria:

  • Does the robot's form fit its function and context?
  • Are the proposed interactions natural and intuitive?
  • Is the technical specification realistic and achievable?
  • Have ethical concerns been thoughtfully addressed?
  • Is the design innovative while being practical?

👥 Collaborative Design Scenarios

Team-based exercises simulating real product development scenarios. Practice cross-functional collaboration.

Design Team Simulation

Format: 2-hour collaborative workshop

Roles:

  • Product Manager: Defines requirements and business goals
  • Designer: Creates user experience and interaction patterns
  • Engineer: Assesses technical feasibility and constraints

Challenge:

Design a service robot for hotel lobby assistance. Must greet guests, provide directions, handle check-in questions, and summon human staff when needed.

Deliverables:

  • Platform choice rationale (wheeled, legged, stationary?)
  • Interaction design (voice, screen, gesture?)
  • Technical specification (sensors, AI capabilities, network needs)
  • Implementation timeline and budget estimate

Process:

  • 15 min: Individual research and brainstorming
  • 30 min: Team discussion and requirement definition
  • 45 min: Collaborative design and specification
  • 20 min: Prepare presentation
  • 10 min: Present to stakeholders (instructor or other teams)

Ethical Dilemma Discussion

Format: Structured debate and analysis

Scenarios to Explore:

  • Automation & Jobs: Should we build robots that replace human workers?
  • Elderly Care: Are companion robots for isolated seniors helpful or dehumanizing?
  • Autonomous Vehicles: Who's responsible in an unavoidable accident?
  • Military Robotics: Should robots make life-or-death decisions?
  • Surveillance: When does helpful monitoring become privacy invasion?

Discussion Framework:

  • Present Scenario: Describe specific situation with stakeholders
  • Identify Stakeholders: Who's affected and how?
  • Multiple Perspectives: Argue from different viewpoints
  • Ethical Frameworks: Apply utilitarian, deontological, virtue ethics
  • Design Implications: How should we design given these concerns?

Learning Outcomes:

Develop ethical reasoning skills. Recognize trade-offs. Consider broader impact of design decisions. Practice respectful disagreement and nuanced thinking.

Application Brainstorming

Format: Group ideation workshop

Process:

  • Problem Finding (20 min): Observe daily life and identify pain points
  • Robot Brainstorming (30 min): Generate robot concepts to address problems
  • Feasibility Check (20 min): Evaluate technical and business viability
  • Refinement (20 min): Develop most promising 2-3 concepts
  • Presentation (10 min): Pitch concepts with sketches

Brainstorming Rules:

  • Quantity over quality initially
  • Wild ideas encouraged
  • Build on others' suggestions
  • No criticism during generation phase
  • Sketch ideas visually

Evaluation Criteria:

  • Desirability: Do people actually want this?
  • Feasibility: Can it be built with current or near-future technology?
  • Viability: Is there a sustainable business model?
  • Innovation: Is it novel or a meaningful improvement?

📊 Real-World Case Study Analysis

Examine real robots and robotic systems. Understand what worked, what didn't, and why.

Boston Dynamics: Spot & Atlas

Analysis of Boston Dynamics' remarkable robots and their journey from research to commercial products.

Key Observations:

  • Movement Mastery: Unprecedented mobility and balance
  • Viral Success: YouTube videos generated massive interest
  • Application Search: Years of looking for viable use cases
  • Commercial Pivot: Spot now available for lease/purchase

Design Analysis:

Why is movement so important? How does Spot's dog-like form affect perceptions? Why did Atlas stay in research while Spot went commercial?

Business Lessons:

Cutting-edge technology doesn't guarantee market success. Need clear use cases and value propositions. Sometimes the impressive demo isn't the viable product.

Analysis Questions:

  • What emotions do Boston Dynamics robots evoke? Why?
  • Why did inspection and monitoring become Spot's primary use case?
  • What limitations prevent wider Spot adoption?
  • Should humanoid robots like Atlas prioritize human-like movement?

Social Robots: Jibo vs. Pepper

Comparing two ambitious social robots: why Jibo failed commercially while Pepper found niche success.

Jibo (Failed, 2017-2018):

  • Vision: "World's first social robot for the home"
  • Design: Cute, expressive, voice-first interaction
  • Technology: Limited capabilities compared to smartphones
  • Failure: Couldn't compete with Alexa/Google Home, unclear value proposition

Pepper (Ongoing, 2014-Present):

  • Vision: Humanoid service robot for businesses
  • Design: Friendly but clearly robotic appearance
  • Technology: Autonomous navigation, facial recognition, programmable
  • Success: Deployed in retail, hospitality, healthcare as greeter/info provider

Key Differences:

Jibo targeted consumers, Pepper targeted businesses. Jibo promised too much, Pepper set realistic expectations. Pepper's form factor justified its cost for commercial use; Jibo's didn't for home use.

Analysis Questions:

  • What can social robots do that screens cannot?
  • Why are physical robots harder to justify in homes vs businesses?
  • What would a successful home social robot need to do?
  • How does embodiment change human-robot interaction?

Collaborative Robots in Manufacturing

How "cobots" are changing factory work by working alongside humans rather than replacing them.

Traditional Industrial Robots:

  • Fast, precise, dangerous - must be caged
  • Expensive, complex programming
  • Inflexible - retooling is time-consuming
  • Best for high-volume, repetitive tasks

Collaborative Robots:

  • Slower but safe enough to work near humans
  • Easier programming (often by demonstration)
  • Flexible - can be reassigned to new tasks
  • Complement human workers rather than replace them

Design Innovation:

Force-limiting joints, rounded surfaces, easy programming interfaces, mobile deployment. Success comes from human-centered design, not just technical capability.

Impact on Work:

Cobots take over dull, dirty, dangerous tasks. Humans focus on judgment, problem-solving, fine motor skills. Requires new training but generally welcomed by workers.

Analysis Questions:

  • Why didn't traditional industrial robots spread to small manufacturers?
  • What makes a task good for cobot automation vs human work?
  • How should factories be redesigned for human-robot collaboration?
  • What new skills do workers need in cobot environments?

Delivery Robots: Starship, Nuro, and Last-Mile Logistics

Analyzing autonomous delivery robots navigating sidewalks and streets. Different approaches to the "last mile" problem.

Starship (Sidewalk Delivery):

  • Form: Small 6-wheeled sidewalk robot
  • Speed: Walking pace (4 mph)
  • Use Case: Food and package delivery within 2 miles
  • Success: Operating in 100+ cities, millions of deliveries

Nuro (Street Delivery):

  • Form: Custom autonomous vehicle, no passenger space
  • Speed: Street legal (25 mph)
  • Use Case: Grocery and retail delivery
  • Progress: Pilot programs, regulatory approvals, partnerships with major retailers

Key Challenges:

  • Navigation: Sidewalks are complex - curbs, obstacles, pedestrians
  • Social Acceptance: Do robots belong on sidewalks?
  • Security: Preventing theft and vandalism
  • Weather: Operating in rain, snow, ice
  • Regulation: Creating new rules for new robot types

Design Decisions:

Friendly appearance to reduce fear, lights and sounds to signal intent, remote supervision for edge cases, secure compartments, simple UI for receiving deliveries.

Analysis Questions:

  • Should delivery robots use sidewalks or streets?
  • How do you design robots that share space with pedestrians safely?
  • What makes autonomous delivery economically viable vs human delivery?
  • How should these robots communicate their intentions to people?
  • What's the environmental impact compared to traditional delivery?

Continue Your Journey

Tools

Robotics Field Kit

Access maker resources, design templates, and component guides.

Get Tools →
Review

Fundamentals

Revisit core robotics concepts to deepen your understanding.

Review ↗
Menu