1 / 25

SpeakUp Training

Transform Your Technical Skills into Business Success

Your Mission: Make clients happy by speaking their language

Business English for IT Professionals

July 3, 2025 • 90 Minutes • Level: All

3 minutes

Our SpeakUp Learning Framework

  • Speak First, Perfect Later - Confidence beats perfection
  • Support Your Team - We rise together
  • English = Safe Zone - Mistakes are learning opportunities
  • 1-Minute Rule - Quick thinking, active speaking
  • Celebrate Progress - Every improvement counts

Today: Real workplace communication that works!

2 minutes

The SpeakUp Golden Rule

BUSINESS VALUE first,
technical details second

Engineer Talk

"I'm refactoring the database schema to optimize query performance and reduce computational overhead..."

Client thinking: "What? Why? How much will this cost?"

Business Talk

"Your customers will see pages load 3x faster, which typically increases sales by 15%. I'll improve the database to make this happen."

Client thinking: "Great! When can we start?"

4 minutes

Easy-to-Hard Learning System

Master Business Communication Step by Step

Level 1Basic Structure: "Users will see..."

Level 2Add Context: "Users will see pages load faster..."

Level 3Add Specifics: "Users will see pages load in 1 second instead of 3 seconds"

Practice Now!

Start: "This will save money"

Build: "This will save money by reducing costs"

Master: "This will save money by reducing server costs by 30%"

Pro tip: Specific numbers = Happy clients!

7 minutes

Power Words for Business Impact

Core Business Terms

  • Impact /ˈɪmpækt/ (Tác động)
  • Value /ˈvæljuː/ (Giá trị)
  • Benefit /ˈbenɪfɪt/ (Lợi ích)
  • Solution /səˈluːʃən/ (Giải pháp)
  • Timeline /ˈtaɪmlaɪn/ (Thời gian)
  • Priority /praɪˈɒrəti/ (Ưu tiên)

Magic Phrases

  • "This helps your customers by..."
  • "The business value is..."
  • "This reduces risk by..."
  • "You'll see results when..."
  • "Let me show you how..."
  • "Here's what this means for you..."

Remember: These words turn technical work into business wins!

5 minutes

The SpeakUp Success Formula

Use this proven structure for EVERY client conversation:

Step 1: User Impact

"Users will see/experience/be able to..."

Step 2: Business Impact

"This will save/make money/reduce risk by..."

Step 3: Simple How

"We'll achieve this by..." (keep it simple!)

Step 4: Clear Timeline

"You'll see results by..."

Complete Example:
"Users will see checkout complete in 2 seconds. This will increase completed purchases by 20%, adding $50K monthly revenue. We'll optimize the payment system. You'll see results in 10 days."
5 minutes

Practice the 4-Step Formula

Scenario 1: Fixing Login System

Your task: Use the 4-step formula to explain this work to a client

Help:

  • User impact: Faster, more secure login
  • Business impact: Reduces customer complaints, increases trust
  • Technical: Improve authentication system
  • Timeline: 1 week

Practice with your partner! One person explains, one person is the client.

8 minutes

Meeting Opening Scripts

These make clients feel heard and important:

Script 1: "Before we talk about technical details, help me understand what success looks like for your business today."

Script 2: "Let me make sure I understand your business goals so I can give you the best technical advice."

Script 3: "What's the most important business problem we need to solve today?"

Notice: We start with THEIR needs, not our technical work!

8 minutes

Explaining Your Technical Work

When client asks: "What are you working on?"

Script: "I'm working on [simple description] which will help your customers [specific benefit]."

Example: "I'm working on the login system which will let your customers sign in faster and more securely."

When client asks: "How long will this take?"

Script: "Based on similar work we've done, this should take [time]. I'll tell you right away if anything changes."

When client asks: "Why is this complex?"

Script: "I can see why this looks simple from the outside. Let me explain what happens behind the scenes..."

12 minutes

Sprint Planning Meeting Role-Play

Scenario:

You're planning the next 2-week sprint for an e-commerce website. The client wants to add 5 new features, but you can only do 3 well.

Opening Script:

"Before we plan our work, let me understand your business priorities for the next 2 weeks."

When Scope is Too Big:

"We have more work than we can finish well. Which features are most important for your business goals?"

When Client Wants to Add More:

"Great idea! If we add this, we'd need to remove [other work] or extend the timeline to [new date]. What do you prefer?"

8 minutes

Role-Play Practice

Developer Role

  • Use SpeakUp scripts exactly
  • Start with business value
  • Sound helpful, not defensive
  • Give clear options

Client Role

  • Want 5 features in 2 weeks
  • Ask "Why can't you do all?"
  • Push for more work
  • Focus on business needs
Practice for 4 minutes, then switch roles!

Remember: You're helping them make good business decisions!

5 minutes

Technical Debt Simple Analogies

Car Analogy

"Technical debt is like putting off car maintenance. You can drive for a while, but eventually you need an oil change or the engine breaks down."

House Analogy

"Think of technical debt like a house foundation. You can't see it, but if it's weak, everything built on top becomes unstable."

Road Analogy

"Technical debt is like driving on a bumpy road. You can still get where you're going, but it's slow and uncomfortable."

Choose the analogy that feels most natural to YOU!

4 minutes

Technical Debt Business Impact

Business Impact Script 1:

"Right now, simple changes take [current time]. After we fix technical debt, they'll take [reduced time]. This means we can deliver [specific business benefit] 30% faster."

Business Impact Script 2:

"Technical debt is slowing us down. We spend [time] fixing bugs instead of building features. Addressing this means more time building things that make you money."

Complete Example:
"Technical debt is like a bumpy road - you can still travel, but it's slow. Right now, adding simple features takes 3 days. After we fix this, they'll take 1 day. This means we can deliver new features 3x faster."
4 minutes

Technical Debt Practice

Scenario:

You need 1 week to fix technical debt. The client says "I don't want to spend time on technical debt. I need features."

Your Task:

  1. Choose your favorite analogy (car, house, or road)
  2. Explain business impact with specific numbers
  3. Make the client understand the value
Practice with your partner: One explains, one resists. Then switch!
5 minutes

Crisis Communication Script

When Everything Goes Wrong:

"I need to tell you about a serious problem and what we're doing to fix it.

  • What happened: [simple explanation]
  • How it affects your business: [specific impact]
  • What we're doing right now: [immediate actions]
  • What we'll do next: [plan with timeline]
  • When I'll update you again: [specific time]"
Vietnamese Cultural Note: In Vietnamese culture, we might delay bad news. In English business culture, immediate honesty builds trust!
5 minutes

Crisis Communication Practice

Crisis Scenario:

The main server crashed. All user data is safe, but the website will be down for 6 hours.

Your Task:

Use the SpeakUp crisis script to communicate this to your client.

Focus On:

  • Sound calm and in control
  • Be honest and direct
  • Focus on solutions
  • Give specific timelines

Remember: Honesty builds trust, even in bad situations!

3 minutes

Simple Words Instead of Jargon

Technical Jargon

  • "Refactor the codebase"
  • "API returning 500 errors"
  • "Implement microservices"
  • "High coupling in system"
  • "Performance degradation"

Simple English

  • "Clean up the code"
  • "Users getting error messages"
  • "Rebuild for easier updates"
  • "Parts too connected"
  • "System getting slower"

Always explain WHAT IT MEANS FOR BUSINESS!

2 minutes

What NEVER to Say

Never Say

  • "That's impossible"
  • "You don't understand"
  • "That's not my job"
  • "We can't do that"
  • "It's complicated"
  • "That's a stupid idea"

Say Instead

  • "That's challenging. Let me show you what we can do."
  • "Let me explain this in a different way."
  • "Let me find the right person to help you."
  • "Here are our options."
  • "Let me break this down into simple steps."
  • "Let me understand what you're trying to solve."
2 minutes

Signs You're Doing Well

Success Signs

  • Client asks follow-up questions
  • Client says "that makes sense"
  • Client refers to your explanations in other meetings
  • Client trusts your recommendations
  • Client seems relaxed and confident

Warning Signs

  • Client stops asking questions
  • Client looks confused or frustrated
  • Client asks same questions repeatedly
  • Client goes to other team members
  • Client seems worried about project
3 minutes

Quick Reference Cheat Sheet

For Any Technical Explanation:

  1. Start with business impact
  2. Use simple words and analogies
  3. Give specific numbers when possible
  4. Connect to user experience
  5. Provide clear next steps

For Any Problem:

  1. Say what happened (simply)
  2. Explain the business impact
  3. Give 2-3 solution options
  4. Recommend the best option and why
  5. Commit to specific follow-up
2 minutes

Choose Your Top 3 Scripts

From all the SpeakUp scripts we practiced, choose 3 you'll use this week:

Popular Choices:

  • Opening meeting script
  • 4-step explanation formula
  • Problem communication script
  • Technical debt analogy
  • Scope change response
Write them down! These are your tools for this week!
2 minutes

Real Work Application

Think about your actual work. When will you use these scripts?

Commitment Examples:

  • "I'll use the 4-step formula in tomorrow's client demo"
  • "I'll practice the opening script for Friday's sprint planning"
  • "I'll explain technical debt using the car analogy next week"
  • "I'll use the crisis script if any problems happen"
Share your commitment with a partner!
1 minute

This Week's Homework

Your Practice Tasks:

  1. Choose ONE SpeakUp script - practice it daily
  2. Use it in real work - at least once this week
  3. Note client reaction - did they understand better?
  4. Write 3 sentences - about your experience
Next week: Bring a real work scenario where communication was difficult!
Final

Remember

Your job is to make clients happy by explaining technical work in simple business terms.

Every conversation should make them feel:

More CONFIDENT, not more confused!

You already have the technical expertise.
Now you have the communication tools too!

Thank You!

Ready to make clients happy!

Practice your chosen scripts this week.
See you next class with success stories!

Business Value First Technical Details Second