> Markdown version of [/videos/2071-same-words-different-worlds-who-s-in-control](https://www.wearedevelopers.com/videos/2071-same-words-different-worlds-who-s-in-control). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Same Words, Different Worlds: Who's in Control?

Why do simple requests trigger infinite edge cases for developers? Discover how applying AI prompt engineering to human conversations eliminates ambiguity and guarantees predictable project delivery.

- **Speakers:** [Christina Rohrmoser](https://www.wearedevelopers.com/@christina-rohrmoser), [Stefan Wöhrer](https://www.wearedevelopers.com/@stefan-wohrer)
- **Event:** World Congress 2026 Europe - Virtual Stage
- **Published:** July 2, 2026
- **Duration:** 39:03
- **URL:** https://www.wearedevelopers.com/videos/2071-same-words-different-worlds-who-s-in-control

## Summary

Software development projects consistently face major bottlenecks due to miscommunication, particularly between requirements engineers and developers. While modern tools like Slack, Miro, and AI assistants have transformed workflows, the fundamental challenge remains that the same words rarely mean the same thing to different people. Because human communication is multi-sensory and heavily reliant on individual mental models, simple requests can trigger infinite permutations of edge cases for developers while seeming straightforward to stakeholders. Bridging this gap requires treating communication as an engineered skill that must be actively trained and structured. Interestingly, the rise of generative AI has provided a blueprint for solving human-to-human communication failures. To force ambiguous natural language models to produce precise code, developers have mastered prompt engineering by layering rich context, defining strict rules, and enforcing iterative feedback loops. When these exact methods are applied to team interactions, ambiguity drops significantly. By adopting a plan mode where developers explicitly paraphrase requirements back to stakeholders before writing code, teams can validate alignment and catch blind spots early. Similarly, instructing colleagues to actively ask questions rather than making assumptions mimics the AI prompting technique of requesting clarifying questions, which drastically reduces costly rework. To codify these practices, engineering teams should establish concrete communication protocols similar to those used in high-stakes environments like aviation. By consistently starting conversations with a clear purpose, focusing on the what and why instead of prematurely defining solutions, and implementing standardized checkpoints, teams can remove the social friction and guesswork from collaboration, ultimately transforming disjointed conversations into highly predictable project delivery.

**Keywords:** project communication failures, requirements engineering, prompt engineering techniques, generative ai collaboration, software development workflows, communication checkpoints, agile sprint planning, developer feedback loops, paraphrasing techniques, context building in teams, miscommunication mitigation, cross-functional alignment, iteration and planning, coding assumptions, human-to-ai interaction

## Chapters

1. **Historical context of communication failures in software projects** (00:19) — Despite new collaboration tools, poor communication remains a primary cause of project failure.
1. **Friction between requirements engineers and software developers** (03:20) — Simple requirements often hide complex technical permutations that demand early clarification from engineering.
1. **How context shapes the construction of message meaning** (06:51) — Receivers interpret identical words differently based on their unique mental models and background.
1. **Strategies and training for improving team communication behaviors** (11:57) — Structured communication training and guided checklists can significantly reduce operations overhead and team friction.
1. **Applying prompt engineering principles to human team communication** (14:57) — Providing rich context to reduce ambiguity works equally well for generative models and coworkers.
1. **Using iteration and paraphrasing to verify requirement understanding** (19:17) — Enforcing a routine where the receiver rephrases instructions prevents misaligned expectations before execution begins.
1. **Planning and asking specific questions before writing code** (21:23) — Requesting explicit feedback options before implementation reduces expensive code rework and wasted resources.
1. **Comparing background context processing in humans and artificial intelligence** (24:57) — Building reliable common ground requires explicitly sharing the unstated background assumptions that coworkers lack.
1. **Actionable frameworks for effective technical conversations and meetings** (27:30) — Defining meeting purposes, exploring underlying project rationale, and formalizing next steps eliminates hidden assumptions.
1. **Implementing communication protocols to standardize team collaboration quality** (35:05) — Adopting rigid checklists and requirement playback routines removes guesswork and normalizes critical team feedback.

## Related Moments

- [Adapting communication skills for AI collaboration](https://www.wearedevelopers.com/videos/100297-the-impact-of-ai-on-game-development-and-the-industry) (from "The Impact of AI on Game Development and the Industry")
- [Applying context engineering across the full software lifecycle](https://www.wearedevelopers.com/videos/100256-can-this-elephant-dance-ibm-bob-and-the-future-of-ai-first-software-development) (from "Can This Elephant Dance? IBM Bob and the Future of AI-First Software Development")
- [Rethinking software engineering processes beyond human constraints](https://www.wearedevelopers.com/videos/1830-wearedevelopers-live-speculaitions) (from "WeAreDevelopers LIVE - SpeculAItions")
- [The growing necessity of orchestrating AI in software teams](https://www.wearedevelopers.com/videos/1950-the-scrum-master-as-an-orchestrator-guiding-human-ai-collaboration-in-modern-teams) (from "The Scrum Master as an Orchestrator: Guiding Human–AI Collaboration in Modern Teams")
- [Navigating developer bottlenecks and human accountability](https://www.wearedevelopers.com/videos/100265-fireside-chat-in-conversation-with-werner-vogels-cto-of-amazon-com) (from "Fireside Chat - In conversation with Werner Vogels, CTO of Amazon.com")
- [Redesigning cross-functional teams for AI-driven software development](https://www.wearedevelopers.com/videos/100036-the-new-org-chart-when-ai-joins-the-workforce) (from "The New Org Chart: When AI Joins the Workforce")

## Related Articles

- [Transforming Software Development: The Role of AI and Developer Tools](https://www.wearedevelopers.com/magazine/527-transforming-software-development-the-role-of-ai-and-developer-tools)
- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)
- [WWC24 Talk - Scott Hanselman - AI: Superhero or Supervillain?](https://www.wearedevelopers.com/magazine/469-wwc24-talk-scott-hanselman-ai-superhero-or-supervillain)
- [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)

## Related Jobs

- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**
- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [AI Software Engineer (Germany)](https://www.wearedevelopers.com/jobs/48317-ai-software-engineer-germany) at **Sunhat**
- [Head of AI Applications](https://www.wearedevelopers.com/jobs/ext/1231536-head-of-ai-applications) at **ZEISS Group**