Hello! Welcome to your next lesson.
In our last session, you learned the specific vocabulary to describe project status—phrases like on schedule, over budget, and ran into an issue. You now have the words to say what is happening.
Today, we'll focus on how to organize those words. Our goal is to outline a short project update using a 'What I did, What I'm doing, What's next' structure. This simple framework is incredibly powerful for making your updates clear, professional, and easy to follow. As a technical consultant, you'll find this structure is very common in daily meetings, especially in software and IT environments.
1. The Power of a Simple Structure
When you give an update, your team wants to quickly understand three things: what is finished, what is happening now, and what might cause problems. A clear structure helps you deliver this information without confusion.
In the tech world, many teams use a "daily stand-up" or "scrum" meeting for this. The structure of these meetings is built on three simple questions.

These three questions give us the perfect outline for any professional update:
- What did I do yesterday? (What I did)
- What will I do today? (What I'm doing)
- Is there any impediment? (What's next / What are the challenges)
Let's break down each part.
2. The Three-Part Update Structure
This structure helps you organize your thoughts and use the correct grammar, which we have covered in previous modules.
Part 1: What I did (Past)
This section covers your completed work. You should use the past simple tense, which we practiced in Module 2.
- "Yesterday, I finished the server configuration."
- "Last week, I deployed the new security patch."
- "I completed the analysis of the client's requirements."
Part 2: What I'm doing (Present & Future)
This section is for your current or immediate next tasks. You can use the present continuous or simple future tenses (will or going to), which you also learned in Module 2.
- "Today, I am working on the user documentation."
- "This afternoon, I am going to test the new API."
- "Next, I will start debugging the code."
Part 3: What's next (Challenges & Future Plans)
This is where you mention any problems (often called "blockers" or "impediments") or your longer-term next steps.
- For challenges: "My main blocker is that I don't have access to the database yet."
- For future plans: "After this, I plan to integrate the payment module."

3. Seeing the Structure in Action
Now, let's watch a short video that explains this structure in the context of a daily stand-up meeting. The presenter provides clear, direct examples that are easy to follow.
What to say in your daily standup
In this video, 'What to say in your daily standup,' the speaker explains how to answer the three key questions for an update. This directly matches our structure.
Watch from 02:19 to 04:31. Pay close attention to: The recommended tenses for each question (Past Simple, Future, Present Simple). The concrete examples provided for 'yesterday,' 'today,' and 'what's blocking me.'
Test your understanding!
Based on the video, what tense should you use to talk about what you did yesterday? What about your plans for today?
Show answer
You should use the past simple for what you did yesterday (e.g., "Yesterday, I worked on...") and a future tense like going to or will for today (e.g., "Today, I am going to work on...").
4. Making Your Update More Professional
The "What I did, What I'm doing, What's next" structure is a great foundation. We can make it even more professional by adding a clear opening "headline" and a concluding "action step."
This next video explains a slightly more advanced, but very effective, framework:
- Headline: A one-sentence summary of the overall status.
- Details: Progress (what you did), Challenges, and Next Steps.
- Close: A clear statement of what happens next or what you need.
How to Give a Project Update in English at Work
The video 'How to Give a Project Update in English at Work' offers a fantastic model for delivering a clear, confident update. It builds perfectly on our three-part structure.
Watch from 05:58 to 12:58. Focus on the three steps: Start with the Headline (05:58 - 07:55): Learn phrases to give the main point first. Organize your Details (07:55 - 10:28): See how 'Progress, Challenges, Next Steps' aligns with our structure. Close with Clarity (10:28 - 12:58): Understand how to end your update with a clear action or expectation.
Let's combine these ideas. A great professional update looks like this:
- (Headline): "Overall, the project is on schedule."
- (What I did): "Yesterday, I finished the database migration."
- (What I'm doing): "Today, I am working on the front-end integration."
- (What's next - Challenges): "The only issue is a delay in getting the final design assets."
- (Close - Action): "I will follow up with the design team this afternoon."
5. Reading a Real-World Example
Let's see how this structure appears in a real conversation. The following article shows a dialogue from a scrum meeting. Notice how the developers naturally follow the structure.
Scrum Meeting Example In English
This article, 'Scrum Meeting Example In English,' contains a short dialogue that perfectly demonstrates our update structure in a technical setting.
Read the section titled 'Dialogue.' Pay close attention to the updates given by Developer 1 and Developer 2. Can you identify the 'what I did' and 'what I'm doing' parts in their updates?
For example, Developer 1 says:
- "Yesterday, I wrapped up the frontend of the registration page..." (What I did)
- "...and today, I’m going to get started on the backend." (What I'm doing)
6. Practice Structuring Your Own Update
Now it's your turn to practice. Imagine you are a technical consultant on a software project. Below are some notes you made for your morning update. Organize them into the "What I did, What I'm doing, What's next" structure.
Your notes:
- Fixed a critical bug on the login page. (This was yesterday)
- Need the API documentation from the other team. (This is a blocker)
- Start developing the new reporting feature. (This is for today)
Build your update!
Use the notes above to create a short, structured update. Try to use a full sentence for each part.
Show a possible answer
Here is one excellent way to structure the update:
"Good morning. Yesterday, I fixed the critical bug on the login page. Today, I am going to start developing the new reporting feature. My main blocker is that I'm still waiting for the API documentation from the other team."
Conclusion
Great job! You have learned a clear and professional structure to deliver project updates. This framework will help you organize your thoughts, speak more confidently, and ensure your team always understands your progress.
Key Takeaways:
- A structured update is easy for others to understand.
- Use the "What I did, What I'm doing, What's next" model.
- What I did: Use the Past Simple tense for completed work.
- What I'm doing: Use Present Continuous or Future tenses for current tasks.
- What's next: Use the Present Simple to state blockers or future plans.
- For a more polished update, start with a "headline" and end with a clear "action step."
Preview of the Next Lesson:
Now that you know how to structure your update, the next step is to make it flow smoothly. In our next lesson, we will focus on how to use linking words (e.g., 'First', 'Next', 'Finally') to connect the parts of your update. This will make your speaking sound even more natural and organized.