Listening as Engineering Communication

An interactive learning experience

Adapted from IEEE Professional Communication Society | Original by J. Leydens & J. Lucena (2009)

PITA: Parse Source content extraction

The AI agent first read the original IEEE PCS article and produced a structured analysis: core thesis (basic vs. contextual listening), key concepts, supporting evidence, and learning objectives. This Parse phase ensures the agent understands the content before any transformation begins.

Google This corresponds to Google's content ingestion pipeline in "Learn Your Way" (arXiv:2509.13348) — where source textbook content is analyzed before being re-shaped into multiple formats.

Google Progressive disclosure + self-pacing

Google's research found that students learn better when they control their own pace. The progress bar and section-based navigation implement this principle. In "Learn Your Way," content is divided into digestible chunks with visual progress indicators — the same pattern used here.

Vibe coding The entire progress bar, section navigation, and state management were generated from a single natural language prompt: "Add a progress bar and Next/Previous navigation that divides content into 4 sections."

1. Why Listening Matters in Engineering

Listen to narration ⏱0:00

PITA: Augment Multi-modal: real-time narration

Narration is spoken in the browser using the Web Speech API. The AI agent wrote a narration script for each section; as it plays, a synced real-time transcript highlights each word and a countdown timer shows the remaining time — no audio files required.

Google This implements Google's multiple representations principle — the same content available as text and as audio. "Learn Your Way" generates podcasts, slides, and immersive text from the same source. Here, the AI agent generates audio narration as an additional modality.

When we talk about professional communication, we almost exclusively focus on delivering messages — writing and speaking persuasively. But in a discipline whose main purpose is to serve the needs of communities, stakeholders, and clients, accurately receiving their messages is just as important.

Key insight from Leydens & Lucena: "The skill of listening is crucial to understanding engineering problems, which is the first step to doing engineering right."

Professional Communication Active Listening Stakeholder Needs Engineering Design

PITA: Identify Concept tagging for retrieval

During the Identify phase, the AI agent tagged key concepts from the source analysis. These concept pills serve as visual anchors — a technique from learning design that aids recall by making abstract concepts concrete and scannable.

Quick Check

Why is listening often overlooked in engineering education?

Correct! Leydens & Lucena found that listening is rarely formally taught despite being explicitly listed as a key engineering attribute by multiple agencies.

Not quite. The research shows that while listening seems intuitive, the depth of listening needed for engineering problem-solving requires formal instruction — it goes far beyond everyday conversation.

Google Comprehension quiz with explanatory feedback

Google's "Learn Your Way" generates quizzes as one of its multiple representation formats. Key design principle: feedback is not just "correct/incorrect" but explains why — reinforcing the concept. The wrong-answer feedback redirects learners to the core distinction rather than simply marking them wrong.

Vibe coding The quiz logic (answer checking, feedback reveal, score tracking, disabling options after selection) was entirely generated by the AI agent. The prompt specified: "Quiz questions with immediate feedback that explains why the answer is correct or incorrect."

2. Two Types of Listening

Listen to narration ⏱0:00

Leydens and Lucena make a critical distinction between basic and contextual listening:

Basic Listening

A dyadic process of speaking (output) and hearing (input). Your ability to hear or pay attention to the speaker is considered sufficient.

Like a microphone — captures sound but doesn't understand meaning.

Contextual Listening

Making meaning from more than just speech — using clues from the socio-cultural and historical contexts of stakeholders to facilitate deeper understanding.

Like an interpreter — understands the full context behind the words.

PITA: Identify Comparison table — contrasting two concepts

During the Identify phase, the agent mapped the article's central distinction (basic vs. contextual listening) to a comparison table format. This is one of several representation formats in the PITA framework — chosen here because side-by-side contrast is the most effective way to teach binary distinctions.

Google Google's "Learn Your Way" calls this re-leveling — adapting how content is presented to match the learner's needs. The analogies ("like a microphone" / "like an interpreter") were added by the AI agent to make abstract concepts concrete, a technique Google found increases comprehension.

How Contextual Listening Transforms Engineering

According to Leydens & Lucena, contextual listening helps engineers:

Develop empathic relationships — Moving beyond one-way information transmission to multidirectional dialogue
Transform actions — Actions become collaborative rather than individual, with stakeholder empowerment and project ownership
Foster accountability — A dialogic relationship creates transparency
Create awareness — Sensitivity to individuals' roles, abilities, biases, and their consequences

Scenario: Which Type of Listening?

Scenario

You are an engineer designing a water treatment system for a rural community. During a community meeting, a village elder says: "We don't trust the water from the new pipes."

A basic listener would:

A contextual listener would:

Exactly! The contextual listener recognizes that "trust" is not about water chemistry — it's about history, culture, and power dynamics. This deeper understanding leads to solutions the community will actually adopt.

This is a basic listening response — it addresses the surface meaning but misses the deeper context. The elder's concern about "trust" likely involves much more than water quality.

PITA: Transform Scenario-based exercise — application, not recall

The PITA framework distinguishes between formats for recall (quizzes) and formats for application (scenarios). This scenario exercise was mapped during the Identify phase as the best format for the article's practical implications — it asks learners to apply the basic/contextual distinction to a realistic engineering situation.

Google In "Learn Your Way," this corresponds to interest-based examples — Google found that learners engage more deeply when concepts are illustrated through scenarios relevant to their field. The water treatment scenario connects listening theory to real engineering practice.

Vibe coding The scenario content was generated by the AI agent, drawing on the source article's discussion of community-based engineering projects. The prompt was: "Create a scenario exercise where learners must distinguish basic from contextual listening in an engineering context."

3. Applying Contextual Listening

Listen to narration ⏱0:00

Your Turn — Reflection Exercise

Think of a professional communication situation where basic listening led (or could lead) to a misunderstanding. Describe how contextual listening would change the outcome.

PITA: Identify Reflection prompt — metacognition

The Identify phase mapped the article's call to action to a reflection prompt format. Unlike quizzes (which test recall) or scenarios (which test application), reflection prompts engage metacognition — learners connecting the concept to their own experience. This progression from recall to application to reflection follows Bloom's taxonomy.

Google Google's architecture supports personalization — adapting content to the individual learner. The reflection prompt is the simplest form of personalization: the learner supplies their own context, making the content personally meaningful.

Key Takeaways

Listening is a professional communication skill that deserves the same attention as writing and speaking
Basic listening (hearing words) is necessary but insufficient for engineering practice
Contextual listening (understanding socio-cultural meaning) leads to better design, stronger stakeholder relationships, and more equitable outcomes
Engineering curricula should formally teach listening, not assume students will develop it naturally

Final Quiz

An engineer is developing a mobile health app for elderly patients. Which practice best demonstrates contextual listening?

This is contextual listening in practice! By understanding the full socio-cultural context — not just stated preferences — the engineer can design a solution that truly fits the users' lives.

While useful, this approach relies on basic listening — collecting explicit input without exploring the deeper context that shapes how users relate to technology and health.

Your Results

Listen to summary ⏱0:00

0 / 3

Complete the quizzes to see your score.

This interactive page was created from a static IEEE PCS article using vibe coding — an AI agent transformed the content in minutes, with no traditional programming required.

Original article: IEEE PCS — Listening as Engineering Communication
Reference: J. Leydens and J. Lucena, "Listening as an Engineering Skill," IEEE Trans. Prof. Commun., vol. 52, no. 4, Dec. 2009.

PITA: Transform Gamification — score tracking and adaptive messaging

The score display and performance-based messages implement gamification — a representation format from the PITA framework. The AI agent generated four levels of feedback messages based on score, providing encouragement calibrated to performance rather than generic praise.

Google Google's efficacy study showed that active engagement (quizzes, self-checks) was a key factor in the 11-percentage-point retention gain. The score summary at the end reinforces learning by prompting self-assessment.

Vibe coding This entire page — 300+ lines of HTML, CSS, and JavaScript — was generated by an AI agent from natural language prompts in an IDE. No traditional programming was required. The transformation from a static 800-word article to this interactive experience took minutes, not hours.