Computer Science · 9th Grade

Active learning ideas

Communicating Technical Details to Non-Technical Audiences

Active learning engages students in real tasks like translating, adapting, and critiquing explanations, which builds the cognitive flexibility needed to switch between technical and user perspectives. Role-playing and hands-on design challenges help students experience the gap between expert knowledge and audience needs firsthand.

• Common Core State Standards
• CSTA: 3A-IC-27
• CSTA: 3A-AP-23

• 20–40 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Think-Pair-Share
• 20 min · Pairs

Think-Pair-Share: Feature to Benefit Translation

Give students a list of technical specifications (e.g., 'AES-256 encryption,' '99.9% uptime SLA,' 'REST API with OAuth2 authentication'). Partners must rewrite each as a plain-English user benefit. Pairs share their translations and class votes on which is most accessible to a parent or school administrator.

Explain how to translate technical specifications into benefits for a non-technical user.

Facilitation Tip

During the Think-Pair-Share, assign each pair a different technical specification so the whole class experiences diverse examples of translation work before sharing out.

What to look for

Provide students with a simple technical specification (e.g., 'The algorithm uses a binary search to find data'). Ask them to write one sentence explaining the user benefit and one sentence explaining why a non-technical person might not understand the original specification.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 02

• Expert Panel
• 40 min · Small Groups

Audience Adaptation Workshop

Groups prepare a two-minute explanation of the same software feature for three different audiences: a 4th grader, a school principal, and a venture capitalist. Groups present all three versions and class identifies which language choices changed between audiences and why.

Design a presentation that effectively communicates complex technical concepts simply.

Facilitation Tip

In the Audience Adaptation Workshop, provide role cards (e.g., busy parent, retired engineer, curious teen) to push students to tailor language beyond generic 'simple' terms.

What to look for

Students pair up and explain a technical concept from a recent project to their partner. The listener then provides feedback using a rubric: Was the explanation clear? Were technical terms avoided or explained? Did the explanation focus on user benefits? The listener rates each item on a scale of 1-3 and offers one specific suggestion.

• Understand
• Apply
• Analyze
• Evaluate
• Self-Management
• Relationship Skills

Activity 03

• Expert Panel
• 35 min · Pairs

Peer Critique: Technical Presentation Pitfalls

Students give a 90-second explanation of a class project to a peer playing the role of a non-technical parent. After each presentation, the 'parent' shares one moment where they got confused. Students revise their explanation and try again. Class debriefs the most common confusion points.

Critique common pitfalls in communicating technical information to a general audience.

Facilitation Tip

For Peer Critique: Technical Presentation Pitfalls, give students a checklist that links each pitfall to a specific section of the presentation slide so feedback stays concrete and actionable.

What to look for

Facilitate a class discussion using the prompt: 'Imagine you are explaining a new feature of a smartphone app to your grandparent. What technical detail would you simplify, and how would you describe the benefit in a way they would understand?' Encourage students to share diverse examples and strategies.

• Understand
• Apply
• Analyze
• Evaluate
• Self-Management
• Relationship Skills

Activity 04

• Expert Panel
• 30 min · Individual

Design Challenge: One-Page Explainer

Individually, students design a one-page document that explains their current class project to a non-technical audience. The document must include no jargon, at least one analogy, and a clear statement of what problem the project solves. Peer review focuses on jargon identification and analogy effectiveness.

Explain how to translate technical specifications into benefits for a non-technical user.

Facilitation Tip

In the Design Challenge: One-Page Explainer, require students to include one analogy and one concrete example, ensuring their explanations move beyond abstract jargon.

What to look for

Provide students with a simple technical specification (e.g., 'The algorithm uses a binary search to find data'). Ask them to write one sentence explaining the user benefit and one sentence explaining why a non-technical person might not understand the original specification.

• Understand
• Apply
• Analyze
• Evaluate
• Self-Management
• Relationship Skills

A few notes on teaching this unit

Teaching technical communication requires students to confront their own 'curse of knowledge' directly through structured feedback. Avoid lecturing on jargon—make students recognize its effects by testing their explanations on real or simulated non-experts. Research shows that peer feedback, especially from varied audiences, improves clarity more than teacher-led revisions.

Students will translate technical specifications into clear user benefits, adapt explanations for different audiences, and receive feedback on how well their communication reduces confusion. Successful learning is evident when students can explain the same technical detail in multiple ways for varied listeners.

---

Watch Out for These Misconceptions

• During Think-Pair-Share: Feature to Benefit Translation, students may claim that simplifying means leaving out important information.

  Use the translation worksheet to show that students must select only the details relevant to the audience’s goal while keeping the core idea intact; for example, explain AES-256 protection as 'keeping your photos safe from strangers' without mentioning encryption.

• During Peer Critique: Technical Presentation Pitfalls, students may assume that if they understand the topic deeply, their explanation should work for anyone.

  Have students read their explanations aloud to a peer playing a specific non-technical role (e.g., 'explain this to your grandparent') and revise based on the listener’s confusion, not their own familiarity.

• During Audience Adaptation Workshop, students may believe jargon makes them sound credible.

  Provide a 'jargon audit' sheet where students highlight any technical terms, then rewrite each using analogies like 'like a library card catalog' instead of 'database index' to make benefits clear.

---

Methods used in this brief

• Think-Pair-Share
• Expert Panel