Professional Communication
Objective: Learn to communicate like a professional in IT contexts.
Technical skills get you in the door. Communication keeps you in the room. You can be the best engineer alive, but if you can't write a clear email, document a ticket properly, or ask a question without wasting someone's time, you'll get overlooked by people who can.
This isn't a soft skills seminar. This is practical communication that IT professionals use every day.
-
Professional email : Specific subject line. Lead with what you need. Context body only. Clear next step. No walls of text. No 'Hope this finds you well.'
-
Trouble tickets : Title, environment, steps to reproduce, expected behavior, actual behavior (copy/paste errors, never paraphrase), and what you've already tried.
-
Asking questions online : Search before you post. State what you're trying to do, not just the error. Include OS, versions, exact error output, and what you tried. Don't say 'it doesn't work.'
-
Explaining to non-technical people : If they don't understand, that's your failure, not theirs. This is the skill that puts you at the table.
- 1
Write a professional email to a fictional vendor requesting a quote for 10 desktop computers for a small office. Include specs, timeline, and budget constraints.
- 2
Write a mock trouble ticket: the company website is returning a 502 error. It started after the latest deployment. Users in the eastern US are affected.
- 3
Write a forum post asking for help: your Nginx server returns 403 Forbidden when accessing a subdirectory. Include everything someone needs to help you.
- 4
Pick three concepts from this course (e.g., DNS, file permissions, SSH). Write a one-paragraph plain-English explanation of each for a non-technical person. No jargon.