Design Challenge III - Final Performance and Final Thoughts

The Final Week and Workshop of Design Challenge III.
Compared to Design Challenge II, Design Challenge III was a lot more easy going. Instead of repeating another cycle of the Design thinking process, we merely continued improving our role play and putting the poster together

With the poster and the role play finalized and cemented, we requested every team member perform rehearsals of their performance for the workshop.
On the day of the workshop, the group had fun presenting and we obtained positive feedback for our performance. The group ended on a happy note.

Overall, In Design Challenge III, we were more focused on the role play than the solution and didn't rapid prototype and simply (in the end) combined our ideas together to create an overall giant solution. We lacked interviewing members for their opinion (Further Empathizing) and lacked further ideation. Again, we were caught working towards a solution.

Nonetheless, despite the lack of true design thinkers. The group, while the most incidents, was also one of the most fun groups where we all struggled on the back foot and the start and were caught during the rehearsals, but managed to pull it together with everyone assisting each other and helping each other pull their bits together (including scripts) to achieve the shared goal of a 6. I could've been a better team member this design challenge by implementing a similar tactic to Design Challenge 2 where we added 2nd team meetings. But due to the lack of people appearing for team meetings I was less inclined to do so. I could've tried harder to make sure the members appeared for team meetings or reschedule it if they always seemed to have something on to make the team and our final performance more productive.

Design Challenge III - The Great Rehearsal

This week, we had compiled our interviews from the "Empathize" design thinking mode and it had luckily related to our "Problem Definition" and ideas.
We were all already in the middle of the prototyping stage from last week and were able to complete it easily (Our various sketches and solutions to our problem).

 This meant putting together our solution and our role play ready for the rehearsal on the workshop.
While we realized the next workshop was a rehearsal, we did not know what to expect - nor properly understand what the roles of the narrator and problem definer were really meant to do. This was especially because we had an extra member of our team which meant we were unsure to have more stakeholders or split the problem definition and the solution to 2 different people.
However on the day of the workshop - ("Testing" Design Thinking Mode), we found we were supposed to produce the poster (which we haven't put together) and produce the full role play for the workshop. While we were supposed to go first, we had weaseled out and allowed another group to perform first. This allowed us to see an example of the role play we were to perform and understand the roles better.
Upon this discovery, a last second change was made (right before we went up) where I was to become a stakeholder from the student's perspective.
 The role-play went well except for some last second shuffling by the team which could have gone a lot better, but the feedback received assisted us in improving our role play for the actual performance.

Overall, this week, again we had a couple of problems. We could've been a lot better organized for the role play if we had properly asked and understood the task beforehand, rehearsed and organize scripts (My own role was speaking out of my own experience with O-Week with a couple points from the interview). If I had assisted my team in that area and helped one of our team members (he was absent for team meeting again due to job interview) to catch up to speed, it would have reduced a lot of hassle.

Design Challenge III - Here we go Again!

The third Design Challenge is underway, with the Team entering the "Ideation" design thinking mode, we had collaborated and discussed potential problems and solutions.
Sadly, our team meeting was missing a member for unknown reasons and we couldn't decide on a solution or the problem (as each one had a different opinion). As such, we re-entered the "Define" thinking mode and upon further reading the task sheet, we were reminded that we were supposed to role play and represent various members of the stakeholders.
This allowed us to narrow down the problems to the single which we thought would be the easiest to portray

• O-Week is clumped and too messy

With the problem re-defined from multiple problems to a single problem, we re-entered the "Ideation" design thinking mode and came up with several solutions including:

• Organizing O-Week (Separating it by category)
• A QUT O-Week Application
• Brochures (Maps) that are given out at all entrances

We decided to try the simplest of them all and simply organize O-Week. At which, we all agreed and began thinking of different ways to do it.

As we entered the workshop for the week, we were told we had to interview all stakeholders to "empathize" with their various viewpoints of O-Week in our particular problem. Considering we had already begun/finished our Prototyping phase we were fairly worried but not too overly concerned. As the week closed, we all split up to interview our various different Stakeholders. I was assigned to interview the QUT Success program on their advice on their O-Week experience

Overall, there were a few mishaps this week, the team member's absence was a great disturbance (although it probably worked our for the best) as well as during the workshop, we gained an extra member. This meant we had 1 more member than every other group. Aside from that, we all worked well and help both members get up to speed easily. I could've been a better team member by reading the task sheet and understanding the task clearer allowing us to finish interviewing the stakeholders without being reminded. This would have allowed us to construct our Design Challenge in a more productive manner.

I