The Project That Almost Fell Apart
Suggested reading time: 12–15 minutes
1When Amira agreed to organise a weekend technology workshop at her local community hub, she thought it would be straightforward. The aim was to help older residents everyday online tasks, from booking appointments to spotting suspicious emails. She had run smaller events before and usually everyone. This time, however, she was working with a new team and a deadline that seemed to be approaching at an alarming speed.
2At first, things were going well. Daniel, a volunteer with experience in IT, offered to prepare the demonstrations. Priya agreed to contact local businesses for equipment, while Amira would organise the venue and publicity. But on Monday morning, Daniel sent a brief message: “We may need to rethink Saturday. The computers aren’t ready.” Amira was travelling on a noisy train and only read the first sentence. She immediately assumed that Daniel wanted to cancel the whole event.
3Instead of asking for clarification, Amira sent a frustrated message to the group. “We can’t keep changing plans. Everyone needs to .” Daniel felt unfairly criticised. He had simply meant that they should borrow tablets instead of using the old computers. Priya, meanwhile, thought the message was aimed at her because two companies had not replied to her emails. By lunchtime, three people had , and nobody was speaking openly.
4The following day, Amira tried to Daniel by phone, but he was teaching all morning. When they finally spoke, she discovered what he had actually meant. She apologised and admitted that she had allowed stress to her. Daniel accepted the apology, although he pointed out that constant criticism was beginning to . They agreed to discuss problems directly rather than make assumptions in a group chat.
5There was still the practical problem of finding suitable devices. Priya had managed to six tablets from a local business, but they needed twelve. Amira contacted a nearby college, which agreed to lend them another six. She also persuaded a café owner to provide refreshments at a reduced price. By Thursday, the team was finally . They had solved most of the problems, although the workshop schedule still needed attention.
6On Friday evening, a volunteer suggested cancelling the final practice session because everyone was tired. Amira understood the temptation: she also wanted to and go home. Yet she knew that rushing could cause confusion on Saturday. Instead, she shortened the practice session to twenty minutes and asked each volunteer to explain one task clearly. The rehearsal revealed a small but important problem: several instructions used technical words that beginners would not understand.
7The workshop itself was not perfect. One tablet stopped working, and the first session started ten minutes late. Nevertheless, participants asked questions, helped one another and gradually grew more confident. An elderly visitor who had been nervous about online banking said that she had finally her fear of using digital services. That comment meant more to Amira than the attendance figures.
8Afterwards, the team reviewed what had happened. Amira realised that the real difficulty had not been the equipment or the timetable; it had been the way people reacted when they felt under pressure. A short message had created a conflict that almost damaged the project. She had learnt that successful teamwork is not about never making mistakes. It is about noticing misunderstandings early, listening properly and finding a way forward together.