Pages

Sunday, 13 April 2014

Reflection on Team-based Research Project Proposal (Post #3)

I am glad that I was able to work with very wonderful team mates and at the end of the day, all of us were very proud of our Happisnap solution. Here are some of the takeaways I have gained from the project:
1.       
      1. Everyone was too cordial with each other
In the first meeting, which was a brainstorming session, many ideas surfaced. However, the team was rather indecisive in filtering the topics. This may be because no one really voiced out what they liked or disliked about a particular plan. With everyone saying that they were flexible with any topic, it made it hard to proceed with the project at the initial stage. Fortunately, this situation did not last for long as everyone began to know each other better and was more willing to raise their concerns

This is actually a common situation that many of us will face in the workplace. At times, colleagues may be reticent about voicing any problems lest it incur the wrath of the counterparty. When conversing with superiors, we may also be hesitant in pointing out any errors or inadequacies. However, the most appropriate course of action is actually to be frank to each other. This will help to build trust and minimise occurrences of misunderstanding. To mitigate the possibility of coming across as too blunt, we could try to phrase our concerns in a more tactful manner. With better understanding of each other, work progress will be more efficient and productivity can be raised.

2.     2. Team members have different commitments
There were instances when some people may not have the same level of commitments throughout the duration of the project.

Our team was able to manage this very well as everyone was comfortable with the idea of everyone contributing different amount throughout the process.  This is a very useful approach in the workplace but it would also depend on the circumstances. Some companies may have very conservative corporate work culture that do not allow their employees to adjust their level of commitments flexibly.

Nonetheless, it is still ideal if one can deliver sustained performance throughout the process. Having unpredictable performance may give the wrong impression that you are not that reliable and consistent in your work.

3.     3. The need to constantly reviewing project progress
Initially, the team had selected the solution of promoting work-life balance amongst other initiatives to help promote happiness. It was only much later that the team realised that the solution was too banal and that the focus group (everyone from young to old) was actually too huge to tackle. The main reason why all of us overlooked this problem was due to the lack of constantly reviewing the project progress and checking whether it fulfilled our intention which was to target the secondary school age group.

This is frequently observed in the work environment too. At times, some of us may be too engrossed in our project that we often forgot the real intention of what the project aims to solve. For instance, when designing a phone for the elderly, some of us may be too pre-occupied with the idea of adding many features to the phone. The correct approach would be to understand what the elderly needs and how the product fulfils the requirements, which in most cases should be issues of readability and volume control. 

0 comments:

Post a Comment

 

(c)2009 Yi Kai's ES2007S Blog. Based in Wordpress by wpthemesfree Created by Templates for Blogger