How to Explain What Happened Step by Step in Software Onboarding Conversation English
When you are setting up a new software tool and something goes wrong, you need to explain the problem clearly so the support team or your colleague can help you quickly. The best way to do this in English is to describe what happened in the order it happened, using simple past tense verbs and clear time markers. This article gives you the exact phrases, sentence structures, and practice you need to explain a software onboarding problem step by step, whether you are writing a chat message, speaking on a call, or sending an email.
Quick Answer: How to Explain a Problem Step by Step
To explain what happened, follow this simple three-part structure: First, state what you were doing. Then, describe the action you took. Finally, explain the unexpected result. Use time words like “first,” “then,” “after that,” and “finally.” Keep your sentences short and use past tense verbs. For example: “First, I opened the dashboard. Then, I clicked the ‘Import Data’ button. After that, the screen went blank.”
Why Step-by-Step Explanations Matter in Software Onboarding
During software onboarding, you are learning new workflows, menus, and buttons. If you skip a step or describe events out of order, the person helping you may misunderstand the problem. A clear, chronological explanation helps them reproduce the issue and find the fix faster. This is especially important in chat or email, where the other person cannot see your screen.
Key Language for Step-by-Step Explanations
Time Markers to Show Order
Use these words and phrases to show the sequence of events:
- First / To start / Initially
- Then / Next / After that
- Later / Afterwards
- Finally / In the end
Past Tense Verbs for Actions
Use the simple past tense for each action you took. Here are common verbs used in software onboarding:
- opened, clicked, selected, entered, typed, uploaded, downloaded, saved, closed, restarted
Describing the Problem
After you describe the action, explain what went wrong. Use these phrases:
- …but nothing happened.
- …and the screen froze.
- …but I got an error message.
- …and the page did not load.
- …but the data did not appear.
Formal vs. Informal Tone
Your choice of words depends on who you are talking to and how you are communicating.
| Context | Tone | Example |
|---|---|---|
| Chat with a colleague | Informal | “Hey, first I clicked the button, then the screen went white.” |
| Email to support team | Formal | “First, I opened the configuration panel. Then, I selected the import option. After that, an error appeared.” |
| Phone call with IT | Neutral | “To start, I logged in. Next, I went to the settings page. Then, I tried to save, but it didn’t work.” |
Natural Examples for Different Situations
Example 1: Chat Message to a Teammate (Informal)
“Hey, I was trying to set up the user roles. First, I went to the Admin panel. Then, I clicked ‘Add New Role.’ After that, I typed the name and hit save. But nothing happened. The button just didn’t work.”
Example 2: Email to Support (Formal)
“Dear Support Team,
I am currently onboarding with your software and encountered an issue. First, I logged into my account. Then, I navigated to the ‘Integrations’ section. Next, I selected the API option and entered my key. After that, I clicked ‘Test Connection.’ However, I received an error message that said ‘Connection Failed.’ Please advise on the next steps.”
Example 3: On a Call with IT (Neutral)
“Hi, I need help with the data import. First, I opened the import tool. Then, I selected the CSV file from my computer. After that, I clicked ‘Upload.’ The progress bar moved to 50%, and then it stopped. The page did not change after that.”
Common Mistakes and How to Fix Them
| Common Mistake | Why It’s a Problem | Better Alternative |
|---|---|---|
| “I clicked the button and error.” | Missing verb and article. | “I clicked the button and got an error.” |
| “First I open the dashboard then I click save.” | Using present tense for past events. | “First, I opened the dashboard. Then, I clicked save.” |
| “I was clicking and then it was freezing.” | Using past continuous for single actions. | “I clicked the button, and then the screen froze.” |
| “The problem is that when I did that thing, it happened.” | Too vague. No clear steps. | “First, I selected the file. Then, I clicked upload. After that, the page stopped responding.” |
Better Alternatives for Common Phrases
Instead of “It didn’t work”
- “The button did not respond.”
- “The page did not load.”
- “The system did not save my changes.”
Instead of “Something went wrong”
- “I received an unexpected error message.”
- “The process stopped at 50%.”
- “The screen went blank after I clicked submit.”
When to Use It
Use the specific alternative when you want to give the support team a clear clue about what happened. The more detail you give, the faster they can help you.
Mini Practice Section
Read each situation and choose the best step-by-step explanation.
- Situation: You tried to reset your password, but the email never arrived.
A) “I clicked reset password and no email.”
B) “First, I went to the login page. Then, I clicked ‘Forgot Password.’ I entered my email and clicked send. After that, I checked my inbox, but the email did not arrive.”
C) “The password reset is broken.” - Situation: You were adding a new user, but the system said the email was already taken.
A) “First, I opened the user management page. Then, I clicked ‘Add User.’ I entered the email address and clicked save. After that, I saw a message that said ‘Email already exists.'”
B) “I tried to add a user and it didn’t work.”
C) “The system is wrong about the email.” - Situation: You were setting up a report, but the data looked wrong.
A) “First, I selected the date range. Then, I clicked ‘Generate Report.’ After that, the numbers did not match what I expected.”
B) “The report is bad.”
C) “I generated a report and it was wrong.” - Situation: You tried to install a plugin, but the installation failed.
A) “First, I went to the plugin section. Then, I searched for the plugin and clicked ‘Install.’ After that, a red error message appeared saying ‘Installation failed.'”
B) “The plugin didn’t install.”
C) “I clicked install and it failed.”
Answers: 1-B, 2-A, 3-A, 4-A
FAQ: Explaining Problems Step by Step
1. Should I always use past tense when explaining a problem?
Yes. Use simple past tense for each action you took. For example, “I clicked,” “I entered,” “I selected.” This makes the sequence clear and easy to follow.
2. What if I don’t remember the exact order of steps?
Start with what you remember first. You can say, “I am not sure about the exact order, but I think first I clicked the settings icon, and then I selected the import option.” It is better to give an approximate order than to mix up the steps.
3. How many steps should I include in my explanation?
Include enough steps so the other person can reproduce the problem. Usually, three to five steps are enough. If you are not sure, include one extra step rather than skipping an important one.
4. Can I use present tense if I am describing something that is still happening?
Yes, but only for the current state. For example: “First, I clicked the button. Then, the screen froze. Now, the page is still frozen.” Use past tense for actions you completed and present tense for the current situation.
Final Tips for Clear Explanations
Practice describing a problem out loud or in writing before you contact support. Use the three-part structure: what you were doing, the action you took, and the result. Keep your language simple and direct. If you are writing an email, read it once to check that the steps are in the right order. If you are speaking, pause between steps to give the other person time to follow.
For more help with common phrases during onboarding, visit our Software Onboarding Conversation Problem Explanations section. You can also review Software Onboarding Conversation Starters for ways to begin these conversations. If you need to make polite requests for help, check out Software Onboarding Conversation Polite Requests. For practice with responses, see Software Onboarding Conversation Practice Replies. For more information about this site, please visit our About Us page.