Theory is useless without practice. This post gives you 30 days of structured daily exercises — each one based on a real scenario you face as a tech lead. Complete one per day. Each takes 15-20 minutes.
How to Use This Guide
- Do one exercise per day — don’t skip ahead
- Speak out loud — every exercise has a speaking component
- Record yourself — use your phone, listen back
- Use AI for feedback — paste your written answers into Claude/ChatGPT for improvement suggestions
- Repeat the cycle — after Day 30, start again. You’ll see improvement
Week 1: Foundation — Daily Communication
Day 1: Morning Standup Update
Scenario: Your team uses daily standups. Give a clear, 60-second update.
Exercise: Write and then speak aloud your standup update using this structure:
“Yesterday I [completed task]. Today I’m working on [task]. I need [help/blocker].”
Practice prompt:
Yesterday I completed the API endpoint for user authentication.
Today I'm working on integrating it with the frontend login form.
I need the design team to finalize the error state mockups by
end of day.Your turn: Write your real standup update for today. Say it out loud 3 times. Time yourself — aim for under 60 seconds.
AI feedback prompt:
“Review my standup update for clarity and professionalism: [your update]“
Day 2: Slack Status Update
Scenario: The product manager asks for a quick update on your feature progress.
Exercise: Write a structured Slack message using the emoji format:
✅ Completed: [what's done]
🔄 In progress: [current work]
⚠️ Blocked: [any blockers]
📅 ETA: [expected completion]Practice: Write a status update for a feature you’re currently working on. Keep it under 5 lines.
Speaking component: Read your message aloud as if explaining it in a call.
Day 3: Explaining a Bug
Scenario: A client reports a bug. You need to explain what happened and what you’re doing about it.
Exercise: Use the PREP framework:
Point: “The search feature is returning incorrect results for some users.” Reason: “Our database query doesn’t properly handle special characters in search terms.” Example: “For example, if a user searches for ‘O’Brien’, the apostrophe breaks the query.” Point: “We’ve identified the fix and will deploy it by end of day today.”
Your turn: Think of a recent bug at work. Explain it using PREP. Record yourself.
Day 4: Asking for Clarification
Scenario: A client explains a requirement, but you’re not sure you understand correctly.
Exercise: Practice these clarification phrases:
- “Just to make sure I understand correctly — you want [your understanding]?”
- “Could you give me an example of what that would look like?”
- “When you say [term], do you mean [option A] or [option B]?”
- “Let me summarize what I’ve heard: [summary]. Is that right?”
- “I want to make sure we’re on the same page. You’re saying [restatement]?”
Practice: Pick a recent requirement you received. Rewrite it, then write 2 clarification questions you could ask.
Speaking: Say each of the 5 phrases 3 times, substituting real examples from your work.
Day 5: Email — Requesting Information
Scenario: You need database credentials from the client’s DevOps team.
Exercise: Write a professional email:
Subject: Request: Database Credentials for Staging Environment
Hi [Name],
I hope you're doing well. We're ready to begin integration testing
for the [project name] project.
Could you please provide us with the following:
1. Staging database host and port
2. Read-only credentials (username and password)
3. VPN configuration (if required)
We'd like to start testing by [date]. Please let me know if you need
any additional information from our side.
Thank you,
[Your name]Your turn: Write a real email you need to send this week. Time yourself — aim for under 5 minutes.
Day 6: Disagreeing Politely
Scenario: In a meeting, the client proposes using a technology you think is wrong for the project.
Exercise: Practice these disagreement patterns:
| Too Direct (avoid) | Professional (use) |
|---|---|
| “That’s wrong" | "I see it differently" |
| "That won’t work" | "I have some concerns about that approach" |
| "No, we should use X" | "Have we considered X as an alternative?" |
| "That’s a bad idea" | "I’d like to suggest we explore another option" |
| "You’re wrong about the timeline" | "Based on our experience, the timeline might be optimistic” |
Practice: Say each professional phrase 3 times. Then create a 30-second argument for why React is better than Angular (or vice versa) using professional language.
Day 7: Weekly Review + Reflection
Speaking exercise: Record yourself giving a 2-minute summary of your week:
- What you accomplished
- What challenged you
- What you learned
- What you plan for next week
Writing exercise: Write 3 sentences about your English learning progress this week.
AI feedback: Share your recording transcript with AI for feedback.
Week 2: Meetings and Client Communication
Day 8: Opening a Meeting
Exercise: Practice 5 different ways to open a meeting:
- “Thanks for joining, everyone. Let’s get started. Today we’ll be discussing [topic].”
- “Good morning. Before we dive in, I’d like to quickly recap where we left off last time.”
- “Alright, let’s kick things off. We have three items on the agenda today.”
- “Hi everyone. I appreciate you making time for this. We have a lot to cover, so let’s begin.”
- “Welcome, everyone. I’ll keep this brief — our main focus today is [topic].”
Practice: Say each opening 3 times. Then improvise your own opening for tomorrow’s meeting.
Day 9: Summarizing Action Items
Scenario: The meeting is ending. Summarize what was decided.
Exercise:
"Let me quickly summarize what we agreed on:
1. [Person] will [action] by [deadline]
2. We'll [decision] starting [date]
3. The next meeting is [date/time] to review [topic]
Does everyone agree? Did I miss anything?"Your turn: Think of a recent meeting. Write and speak the summary you should have given.
Day 10: Handling Pushback
Scenario: The client pushes back on your timeline estimate.
Exercise: Practice the “Acknowledge → Explain → Offer” pattern:
Acknowledge: “I completely understand your concern about the timeline.” Explain: “The reason we estimated three weeks is that the payment integration requires thorough security testing, which typically takes a full week on its own.” Offer: “What I can suggest is this: we deliver the core features in two weeks, and the payment integration in the third week. That way you can start UAT earlier.”
Your turn: Think of a recent pushback you received. Write your response using this pattern.
Day 11: Presenting a Technical Decision
Scenario: You need to explain why you chose PostgreSQL over MongoDB.
Exercise: Use the “What → Why → Tradeoff → Recommendation” structure:
“What: I recommend PostgreSQL for this project. Why: Our data is highly relational — users have orders, orders have items, items have categories. PostgreSQL handles these relationships efficiently with joins. Tradeoff: MongoDB would give us more flexibility for schema changes, but our schema is well-defined and unlikely to change significantly. Recommendation: Let’s go with PostgreSQL. We can add MongoDB later if we need a document store for specific features like activity logs.”
Your turn: Pick a recent technical decision you made. Explain it using this structure.
Day 12: Progress Report to Stakeholders
Exercise: Write and deliver a 90-second progress report:
"Here's our progress update for [project]:
📊 Overall: We're at approximately [X]% completion, which puts us
[on track / slightly behind / ahead of schedule].
✅ This week we:
- Completed [feature A]
- Resolved [issue B]
🔄 Next week we plan to:
- Start [feature C]
- Begin testing [component D]
⚠️ Risk: [main risk and mitigation plan]
Any questions?"Speaking: Deliver this report standing up, as if presenting to a room.
Day 13: Saying “I Don’t Know” Professionally
Exercise: Practice 5 ways to say “I don’t know” without sounding incompetent:
- “That’s a great question. I don’t have the answer right now, but I’ll research it and get back to you by [time].”
- “I’m not 100% sure about the specifics. Let me confirm with the team and follow up.”
- “I’d like to give you an accurate answer rather than guess. Can I get back to you tomorrow?”
- “That’s outside my area of expertise, but I know [person] would have the answer. I’ll connect you.”
- “I haven’t looked into that specific aspect yet. Let me add it to my investigation and update you.”
Practice: Say each phrase 3 times. Use them in a simulated Q&A with AI.
Day 14: Weekly Review — Meeting Skills
Exercise: Rate yourself on these meeting skills (1-10):
- Opening a meeting confidently: ___
- Summarizing action items: ___
- Handling pushback: ___
- Saying “I don’t know” professionally: ___
- Keeping discussions on track: ___
Record a 2-minute reflection on what improved and what needs more practice.
Week 3: Technical Explanations and Problem Solving
Day 15: Explaining Architecture to Non-Technical People
Exercise: Explain microservices architecture using a restaurant analogy:
“Think of our current system like a restaurant where one chef does everything — takes orders, cooks, serves, and cleans. If that chef gets sick, the whole restaurant closes.
Microservices is like having specialized stations: one person takes orders, another cooks pasta, another grills meat, and another handles desserts. If the pasta station goes down, people can still get grilled meat and desserts.
Each station works independently but together they serve the full menu.”
Your turn: Explain one of these using an everyday analogy:
- Container orchestration (Kubernetes)
- Event-driven architecture
- Database sharding
- API gateway
Day 16: Incident Communication
Scenario: Production is down. Write a series of update messages.
Exercise:
Initial message (T+0 min):
”🔴 We’re aware of an issue affecting [service]. Users may experience [symptom]. We’re investigating now and will provide updates every 15 minutes.”
Update (T+15 min):
”🟡 Update: We’ve identified the root cause — [brief explanation]. We’re implementing a fix now. Estimated resolution: [time].”
Resolution (T+45 min):
”🟢 Resolved: [Service] is fully operational. Root cause was [explanation]. We’ve applied [fix] and will share a detailed post-mortem by [date].”
Your turn: Write all 3 messages for a real or hypothetical incident.
Day 17: Code Review Feedback in English
Exercise: Practice giving constructive code review feedback:
| Harsh (avoid) | Constructive (use) |
|---|---|
| “This code is terrible" | "I think we could improve the readability here" |
| "Why did you do it this way?" | "Have you considered using [alternative]? It might handle [edge case] better" |
| "This will cause bugs" | "I see a potential issue with [scenario]. We might want to add validation for [case]" |
| "Delete this" | "I think we can simplify this section by [suggestion]" |
| "Wrong approach" | "What if we approached this from a different angle? For example…” |
Practice: Write 3 constructive code review comments for a recent PR.
Day 18: Estimating and Communicating Timelines
Exercise: Practice the estimation communication template:
“[Feature] will take approximately [time]. I’m estimating [confidence level: high/medium/low] confidence on this.
Here’s the breakdown:
- [Component 1]: [time] — [reason]
- [Component 2]: [time] — [reason]
- Buffer for unknowns: [time]
The biggest risk factor is [risk]. If that materializes, it could add [additional time].
I’d recommend we check in on [date] to reassess.”
Your turn: Pick a feature and write a realistic estimate communication.
Day 19: Post-Mortem / Retrospective
Exercise: Write and present a mini post-mortem:
Incident Post-Mortem: [Title]
Date: [Date]
What happened:
[2-3 sentences describing the incident]
Timeline:
- [Time]: [Event]
- [Time]: [Detection]
- [Time]: [Resolution]
Root cause:
[Technical explanation in simple language]
Impact:
- [Number] users affected
- [Duration] of downtime
- [Business impact]
Prevention:
1. [Action item 1] — Owner: [person] — Due: [date]
2. [Action item 2] — Owner: [person] — Due: [date]
Lessons learned:
- [Lesson 1]
- [Lesson 2]Speaking: Present this as a 3-minute talk.
Day 20: Technical Proposal Writing
Exercise: Write a one-page technical proposal:
Proposal: [Title]
Problem:
[What problem are we solving? Why now?]
Proposed Solution:
[What we'll build/change. Include a simple diagram if helpful.]
Alternatives Considered:
1. [Option A] — Rejected because [reason]
2. [Option B] — Possible but [tradeoff]
Estimated Effort:
- Development: [time]
- Testing: [time]
- Deployment: [time]
Risks:
1. [Risk] — Mitigation: [plan]
Recommendation:
[Clear call to action]Day 21: Weekly Review — Technical Communication
Exercise: Record yourself explaining a technical concept for 3 minutes. Choose one:
- Why we need database migrations
- The difference between REST and GraphQL
- How container orchestration works
- What happens when you type a URL in a browser
Listen back. Rate your clarity, pace, and use of analogies.
Week 4: Advanced Scenarios
Day 22: Negotiating Scope
Scenario: The client wants 5 features but you have budget for 3.
Exercise:
“I’ve reviewed the feature list and I’d like to suggest we prioritize. Based on user impact and technical complexity, here’s what I recommend:
Must-have (Sprint 1):
- User authentication — this is foundational, everything depends on it
- Product catalog — this is the core user experience
- Shopping cart — direct revenue impact
Nice-to-have (Sprint 2): 4. Wishlist — valuable but not critical for launch 5. Reviews system — can be added post-launch without affecting existing features
This way, we deliver a working product in Sprint 1 and enhance it in Sprint 2. Shall we discuss?”
Your turn: Write a scope negotiation for a real project scenario.
Day 23: Onboarding a New Team Member (in English)
Exercise: Write and speak a 5-minute onboarding brief:
- Project overview (30 sec)
- Tech stack and architecture (1 min)
- Development workflow — branches, PRs, deployment (1 min)
- Key contacts and communication channels (30 sec)
- First task assignment (1 min)
- Questions and support (1 min)
Day 24: Presenting at a Standup with a Client Present
Exercise: When clients join standups, your communication needs to be polished:
Internal standup style:
“Fixed the auth bug. Working on the cart. Blocked on the payment API docs.”
Client-present style:
“Yesterday we resolved the authentication issue that was affecting login. Today we’re building the shopping cart functionality. We’re waiting on the payment gateway documentation — [client name], could your team share the API specs? That would help us stay on schedule.”
Practice: Rewrite 3 of your recent standup updates in client-present style.
Day 25: Handling Difficult Questions
Exercise: Practice responses to uncomfortable questions:
“Why is this taking so long?”
“Great question. The timeline has been impacted by [specific reason]. Here’s what we’ve done to address it: [actions taken]. We’re now estimating completion by [date]. Would it help to schedule a quick call to walk through the remaining work?”
“Can you guarantee this won’t happen again?”
“I can’t guarantee zero issues — no system is perfect. But I can tell you what we’ve put in place to prevent this specific problem: [preventive measures]. We’ve also improved our monitoring so if something similar occurs, we’ll detect it within [timeframe] instead of [previous timeframe].”
“Your competitor says they can do it in half the time.”
“I respect that estimate. What I can share is our experience with similar projects: [brief track record]. We prioritize quality and long-term reliability. I’d be happy to walk through our approach in detail so you can make an informed comparison.”
Day 26: Writing a Technical Blog Post Summary
Exercise: Write a 200-word summary of a technical topic:
Pick one:
- “Why We Migrated from REST to GraphQL”
- “5 Lessons from Scaling to 10,000 Users”
- “How We Reduced Our Build Time by 80%”
Use: short sentences, one idea per paragraph, conclusion with takeaway.
Day 27: Phone Call with a Client
Exercise: Phone calls are harder than video calls (no visual cues). Practice these phone-specific phrases:
- “Sorry, could you repeat that? The line isn’t great.”
- “Just to confirm, you said [repeat what you heard]?”
- “I’m going to take some notes while we talk. Please go ahead.”
- “I’ll send a follow-up email summarizing what we discussed.”
- “Can I put you on speaker for a moment? I’d like my colleague to hear this.”
Practice: Simulate a 5-minute phone call with AI. No text — speak your responses out loud.
Day 28: Delivering Bad News
Scenario: You need to tell the client about a delay.
Exercise: Use the “Sandwich” approach (but make it genuine):
“I want to give you an honest update on the project. The good news is that the core features are complete and performing well in our testing environment.
The challenge we’re facing is that the third-party payment integration has some compatibility issues with [their system]. This means we need an additional week to ensure a stable integration.
Here’s our plan: we’ll deliver on the original date with all features except payment. Payment will follow one week later. This means your users can start exploring the product while we finalize the payment flow.
I want to be transparent about this because reliable delivery matters more than optimistic promises. How does this sound to you?”
Day 29: Celebrating Team Wins
Exercise: Write and speak a team recognition message:
“I want to take a moment to recognize the team’s work this sprint. [Person] did an excellent job on the authentication system — the code quality was outstanding. [Person] solved a tricky performance issue that was affecting our load times. And [Person] went above and beyond helping the QA team with test automation.
As a team, we delivered [feature] on time and under budget. That’s a direct result of everyone’s effort and collaboration.
Thank you. Now let’s tackle the next sprint with the same energy.”
Day 30: Final Assessment
Comprehensive exercise: Record yourself doing all of the following (15 minutes total):
- Standup update (1 min)
- Explain a recent technical decision to a non-technical person (2 min)
- Handle a Q&A question you don’t know the answer to (1 min)
- Deliver bad news about a project delay (2 min)
- Present a 5-minute technical topic of your choice (5 min)
- Summarize today’s action items as if closing a meeting (1 min)
- Free-form reflection on your 30-day journey (3 min)
Listen back. Compare with Day 1. You will hear the difference.
After Day 30: What Next?
- Start the cycle again — you’ll notice you do each exercise better the second time
- Customize — replace exercises with real scenarios from your current project
- Increase difficulty — do exercises without preparation time
- Add a partner — practice with a colleague or AI role-play partner
- Build Part 10’s app — automate your daily lessons with progress tracking
Next up: Part 10 — Build a Daily Lesson Generator App — an app that generates a new lesson every day, tracks your progress, and unlocks the next day’s content only after completion.