← Back to workshops
Professional Communication for Tech & Design Careers

Professional Communication for Tech & Design Careers

•Workshop•

Workshop Resources

Watch on YouTubeView Slides

Workshop Overview

This workshop focused on building strong professional communication skills for tech and design careers. We explored best practices, real-world challenges, and practical frameworks to help participants communicate more clearly, confidently, and effectively in consulting and cross-functional environments. Toward the end, a CodeLab member was invited to apply these strategies by tackling real-world communication scenarios live, demonstrating how to navigate common challenges in professional settings.

A huge thank you to Professor Lloyd Wheeler, one of our faculty advisors, for leading this insightful session and sharing actionable strategies for success!

Best Practices Checklist

  • Strive to make understanding EFFORTLESS

    • Audience Adaptation: Tailor technical depth to your audience's expertise and needs.
    • Business Context: Connect technical work to real business value.
    • Front-Loading: Start with your conclusion or recommendation first.
    • Precision: Use specific, measurable terms ("40% faster" instead of "much faster").
    • Clarity in Writing: Use headers, bullet points, and highlights for important information.
    • Transparent Documentation: Maintain clear records of decisions, timelines, and responsibilities.

  • Earn trust through CONSISTENCY

    • Proactive Updates: Communicate regularly; don't wait for problems.
    • Expectation Management: Clearly communicate constraints, dependencies, and potential challenges.

  • Embrace problems to SHINE

    • Active Listening: Validate understanding before responding.
    • Constructive Problem-Solving: Present challenges alongside potential solutions or strategies.

Key Communication Frameworks

Situation-Impact-Recommendation (SIR) Model

  • Situation: Describe the current context.
  • Impact: Explain why it matters (positive or negative).
  • Recommendation: Propose a clear next step.

Example:

Our code reviews take an average of 3 days (Situation), delaying releases by 20% and frustrating the dev team (Impact). I recommend implementing automated code checks and dedicated daily review blocks (Recommendation).

Common Communication Challenges

  • Too Technical or Detailed: Focus on why it matters, simplify, and match your audience's understanding.
  • Burying the Lead: Always front-load the most critical information.
  • Lack of Confidence: Project assurance using specific metrics and clear estimates.
  • Avoiding Conflict: Raise concerns early and pair them with actionable solutions.
  • Last-Minute Surprises: Proactively communicate risks before they impact timelines.
  • Monopolizing Meetings: Keep presentations short and leave time for discussion and next steps.

Scenario Applications

  • "I don't get it": Translate technical concepts into clear business value. Example: Real-time stock updates reduce overselling by 90%.

  • "Where are you?": Front-load project progress to reassure clients. Example: "We're on track for June, with major feature updates completed."

  • "Just fix it": Tie technical problems to business impact and offer clear solutions. Example: "Load times are up 5 seconds, dropping engagement by 15%. We have three solutions ready."

  • "It should be simple, right?": Set realistic expectations while offering phased alternatives. Example: "Video chat requires compliance testing; we can implement a phased rollout."

During the workshop, a CodeLab member was put on the spot to tackle these scenarios live — check out the video to see how they handled it!

Final Takeaways

  • Translate technical concepts into business value.
  • Persuade using clear metrics and measurable outcomes.
  • Proactively communicate risks and progress.
  • Document key decisions and updates.
  • Pair every challenge with potential solutions.