Important Links
|
Research Document Link
Survey Link |
Target Audience Interviews
| Objective: | As per my group project on behalf of AICG BV. I was to conduct qualitative client research in order to better gauge what would our target audience like to see in our product. |
| Action: | In order to conduct my own qualitative research I opted to conduct 4 structured interviews with my group. As such we drafted the interview questions, they made the initial questions together, and I polished up the final result to ensure it was structured properly with more relevant questions. The Interview initially had 20 question, which was updated after some feedback was received. As it had too many leading questions, which could form biases within the interviewees perspective. We then adjusted the questions to be more broad and neutral, which landed us at a total of 23 questions. Once the questions were formulated we ended up conducting the interviews on 4 fellow students from various courses. We all did one interview each. Whilst I did most of the summaries and analysis of the data. Summary: Qualitative Research / Created 20 Questions / 4 Interviews / Iterated Research Methodology / Compile Data |
| Data Summary: | After transcribing our interviews we had a significant amount of data as each interview lasted around 20 minutes, they all generally agreed that we should focus on making a centralised repository for easily accessible coding information rather than go over general Fontys knowledge. We found some other patterns such as all students doing self study for almost everything, searching online for whatever they need. Summary: 20 Mins per Interview / Received Feedback & Indications for Product |
| Reflection: | I realised that general Fontys knowledge wasn't as inaccessible as we initially thought, and students were more worried about code than school schedules and such. I realised that our website should focus on reliving regular inconveniences from fellow students rather than attempt to replace other services. Summary: Some of our hypotheses were wrong / Learnt what Students really wanted |
| Decision: | After some discussion decided re-adjust our attention to a survey in order to gather even more data, quantitative for this matter in order to confirm what we have gathered from our interviews. In addition to this we adjusted out MOSCOW and our Project Plan to better reflect the new found needs of our target audience. Summary: Make a Survey / Adjust MOSCOW & Project Plan |
Interview Questions
Fig. 1 - Interview Questions
Fig. 2 - Interviewee Questions
Target Audience Survey
| Objective: | To conduct a larger survey in order to get quantitative data. |
| Action: | I personally created a survey based upon our previously made interview questions, however adjusted a bit in order to make it more digestible for the average survey taker. My group members assisted in sharing the interview. Summary: Quantitative Research / Survey based on Interview Questions |
| Data Summary: | In our survey of 12 people we found out that:
50% of Students wished for a mixed approach between technical & general Fontys information. 67% of Students preferred Desktop only All students agreed that if we were to add a secondary subject it should be Software All students agreed that we should focus on our frontend development Only 33% of respondents were from the Media profile All students agreed that they would use such a website Almost all students agreed that we should focus on Code Structure however 50% said that we should focus on HTML, CSS & Code Structure |
| Reflection: | We realised that some of the answers in the survey somewhat contradicted the answers from the interviews, as more students emphasised a mixed approach when it came to what topic of information we should dispense of. However, some of the data did match with our interviews as the students agreed we should focus on frontend development, such as the website style and content rather than a complex backend. Summary: Survey Contradict Intewviews / Students wanted Mixed approach |
| Decision: | We decided to take the information gathered from the survey and implement it into our wireframe as the final website structure. We decided upon a dedicated page called "How to survive Fontys" and another dedicated to some basic HTML & CSS repositories. The games we had initially planned took a backseat. Summary: Implement Data into Wireframe & Overall website plan |
Fig. 3 - Partial Survey Screenshot
Fig. 4 - Partial Survey Results Screenshot
