User experience: giving feedback and discussing past mistakes
1
Think about these questions before reading the article. Share your ideas with a partner.
- Think about a website or app you find incredibly frustrating to use. What specific design features make it difficult to navigate or understand?
- Imagine a company released a new feature for an app you use daily, but it made the experience worse. How would you phrase your feedback to be constructive rather than just negative?
- Describe a time you purchased a gadget or subscribed to a service that didn't meet your expectations. If you had had the chance to test it first, what specific changes would you have recommended to the designers?
2
Giving Design Feedback
Listen to the dialogue. Notice how the vocabulary and grammar from the lesson are used.
3
Answer these questions based on the article about the team's first app launch.
01What was the direct consequence for the company immediately after launching the app?
Sample answerThe company faced a wave of negative publicity because the app was unreliable and frustrating for early adopters.
02The author mentions the team spent two months 'frantically trying to iron out the kinks'. What does this phrase imply about the app's condition at launch?
Sample answerIt implies that the app was released with many small and large problems, was not a finished product, and required urgent, stressful work to fix.
03How did the experience of this failed launch affect the team's approach to work in the long term?
Sample answerIt fundamentally changed their development philosophy, making them prioritize listening to user feedback and ensuring product quality over a quick release.
04According to the author, what was the root cause of the team's failure to act on the beta testers' feedback?
Sample answerThe root cause was that the team was too focused on a quick release and, as a result, they overlooked the critical feedback they received.
4
Key vocabulary for product design and feedback
Vocabulary
These expressions will help you discuss user experience and product development more effectively.
Examples
A steep learning curve — when a product or skill is difficult and takes a lot of effort to learn.
This is often used to describe complex software or systems. For example: 'The new editing software is powerful, but it has a very steep learning curve.' The opposite is a 'gentle' or 'shallow' learning curve.
To iron out the kinks — to solve the small problems or faults in a new product, plan, or system.
This idiom is common in professional contexts. It suggests the main idea is good, but minor adjustments are needed. 'We need to iron out a few kinks before the official launch.'
In hindsight — understanding an event or situation only after it has happened.
Use this phrase to start a sentence when reflecting on a past mistake. It connects well with the third conditional: 'In hindsight, if we had done more research, we would have designed it differently.'
To flag an issue — to report or draw attention to a problem so that it can be dealt with.
This is a common and professional way to talk about problems during user testing or in a team meeting. 'During the test, I flagged an issue with the checkout process.'
Seamless integration — the process of combining different systems or parts so they work together smoothly, without any noticeable interruptions.
This is a key goal in modern product design. You might talk about the 'seamless integration' of a new feature into an existing app, or between two different software platforms.
5
Complete the sentences with words from the box. One word is extra.
Word bank
01The new software is powerful, but users are complaining about the learning curve; it takes them weeks to feel comfortable.
02We're launching the beta version next month to a small group of users, which should help us iron out any remaining before the full release.
03In , we should have done more user research before committing to the design. If we had, we would have avoided these problems.
04During the testing session, a user a major issue with the checkout process that our internal team hadn't noticed before.
05The goal is to achieve integration between our mobile app and the desktop version, so users can switch between them without any disruption.
6
Grammar: Third conditional
Grammar
We use the third conditional to talk about imaginary or hypothetical situations in the past. It's perfect for reflecting on past projects and decisions, like in product design. We imagine a different past action and the different past result that would have followed.
Examples
If we had conducted more user testing, we would have discovered the navigation issues earlier.
Use this structure (If + past perfect, would have + past participle) to talk about an unreal past condition and its probable past result.
The launch might have been more successful if the team had iterated on the design based on the initial feedback.
You can use 'might have' or 'could have' instead of 'would have' to suggest a possible, but less certain, result.
If the interface hadn't been so confusing, we wouldn't have received so many support tickets.
Both parts of the sentence can be negative to talk about how a negative situation could have been avoided.
Key points
- Structure: If + past perfect, ...would/could/might have + past participle.
- Use it to express regret or reflect on past mistakes and their hypothetical outcomes.
- Common mistake: Never use 'would have' in the 'if' clause (e.g., NOT 'If we would have conducted...').
7
Correct the mistakes
Read the sentences below, which are all related to product design and user feedback.
Each sentence contains one error. Find and correct it.
01If we would have tested the prototype more, we would have discovered the navigation problems earlier.
Corrected version
If we would have had tested the prototype more, we would have discovered the navigation problems earlier.
02The user interviews provided us with some invaluable sights into how people actually use our product.
Corrected version
The user interviews provided us with some invaluable sights insights into how people actually use our product.
03The app's menu wasn't very intuition, so new users found it difficult to get started.
Corrected version
The app's menu wasn't very intuition, intuitive, so new users found it difficult to get started.
04With hindsight, we realize that we should have spent more time on the initial research phase.
Corrected versionWith In hindsight, we realize that we should have spent more time on the initial research phase.
05The new chat feature was integrated so seamless that most users didn't even notice the change at first.
Corrected version
The new chat feature was integrated so seamless seamlessly that most users didn't even notice the change at first.
06If the team had flagged the bug earlier, the product launch wouldn't have be delayed by a week.
Corrected version
If the team had flagged the bug earlier, the product launch wouldn't have be been delayed by a week.
07For the next version, we need to avoid to make the same design mistakes again.
Corrected version
For the next version, we need to avoid to make making the same design mistakes again.
8
Useful phrases: giving feedback on a new product
Vocabulary
In a professional setting like a team meeting or user testing session, how you give feedback is as important as the feedback itself. These phrases will help you share your thoughts clearly, politely, and constructively.
Examples
My initial thought is that... — use this to give your first, general impression.
Register: Neutral. A great way to start your feedback. You can follow it with a positive or negative point, e.g., '...the layout is very clean' or '...the navigation is a bit confusing'.
What really stands out to me is... — use this to highlight a specific positive feature you noticed.
Register: Neutral. This sounds enthusiastic and specific. It's more impactful than just saying 'I like it', for example, 'What really stands out to me is the speed of the search function.'
It wasn't immediately clear to me where to find... — a polite way to point out something that is confusing or difficult to use.
Register: Neutral to formal. This phrase focuses on your personal experience ('to me') rather than directly criticising the design, which makes it less confrontational.
From a user's perspective, it might be helpful if... — use this to suggest a specific improvement or change.
Register: Neutral to formal. This shows you are thinking about the end-user and frames your suggestion as a helpful possibility, not a demand.
I wonder if we could consider... — a very soft and collaborative way to propose an alternative idea.
Register: Formal. Ideal for situations where you are not the decision-maker. It opens a discussion rather than stating a strong opinion, e.g., 'I wonder if we could consider adding a shortcut'.
Could you walk me through the thinking behind this part? — use this to ask for more context before giving your opinion.
Register: Neutral to formal. This is a smart way to gather more information. It shows you are trying to understand the design choices, which is more constructive than simply saying 'I don't understand this'.
9
Reflecting on a product launch
Read this team lead's reflection on a challenging project.
Fill in each blank with the correct word or phrase from the word bank.
Word bank
, we can see that our initial design had major flaws. If we had conducted more user testing, we wouldn't have released a product with such a . Thankfully, our beta testers helped us before the official launch. One user was quick to with the payment system, which was invaluable feedback. We had aimed for with other popular apps, but it didn't work as planned. If we had focused more on that, the user experience would have been much better.
10
A lesson in product development
Read the passage below, then answer the comprehension questions.
Our team's first major app launch was a disaster, but it taught us an invaluable lesson about listening. We were so focused on a quick release that we overlooked critical feedback during the final testing phase. The app's core feature, which promised seamless integration with users' calendars, was notoriously unreliable. In hindsight, the warning signs were all there. If we had paid more attention when our beta testers flagged an issue with the syncing process, we would have avoided the wave of negative publicity that followed. Instead, early adopters were met with a steep learning curve and a frustrating experience. We spent the next two months frantically trying to iron out the kinks, releasing update after update. If we had delayed the launch by just a few weeks, we could have presented a much more polished product. That failure fundamentally changed our development philosophy.
01What was the main problem with the app's core feature?
Sample answerIt was unreliable and did not provide the seamless integration with users' calendars that it had promised.
02According to the author, what was the team's biggest mistake?
Sample answerTheir biggest mistake was ignoring critical feedback from beta testers because they were focused on releasing the app quickly.
03What does the author imply about the company's current development philosophy?
Sample answerThe author implies that their current philosophy is now more focused on listening to user feedback and quality, rather than speed of release.
04What does the author believe would have happened if they had delayed the launch?
Sample answerThey believe they would have been able to present a much more polished and finished product to the public.
11
Discuss these questions with a partner. Try to use vocabulary from the lesson.
- Think about a popular app or website in your country that has changed significantly over the years. In hindsight, do you think the designers made the right decisions? If you had been on the design team, what issues would you have flagged before the changes were released?
- Some argue that companies should release products early to let users help 'iron out the kinks', while others believe a product should be nearly perfect before launch. Which approach is better for a company's reputation and user loyalty? Discuss the pros and cons.
- Many modern tech products aim for 'seamless integration' but sometimes have a 'steep learning curve'. Which is more important to you when choosing a new gadget or software? Would you sacrifice ease of use for powerful, integrated features, or vice versa?