De landelijke CMD-opleidingen hebben op de site https://cmdmethods.nl/ een overzicht staan van de meest gebruikte onderzoeksmethoden bij CMD-projecten en een korte uitleg hiervan gegeven. Hetzelfde hebben de opleidingen Informatica en Technische informatica (https://www.hbo-i.nl/) gedaan op de site https://ictresearchmethods.nl/. Met beide domeinen heeft CMGT een grote overlap. De genoemde onderzoeksmethoden en indelingen zijn daarom ook voor CMGT relevant.
bron
| type onderzoek | doel van deze methode | uitleg |
|---|---|---|
| library | Standing on the shoulders of giants | To ensure rigor in your design explore what is already done. Watch what competitors are doing or get an overview of existing guidelines, patterns and theories. Sometimes called deskresearch. |
| field | Understand your users | Explore the application context. You apply a field strategy to get an overview of your users, know their needs, desires and limitations so your design is relevant to them. |
| lab | To measure is to know | Be certain your solution works and is relevant for the end-user. Will your design work out the way you intended it to? |
| showroom | Know & show your contribution | Be certain your ideas are better than what is already done. Proof the rigor of your design by showing it to experts, test against guidelines or decide on its USPs |
| workshop | Seek variation and improvement! | Explore opportunities. Prototyping, sketching and co-creation activities are all ways to innovate and to gain insights in what is possible and how things could work. |
| stepping stones | Condense, communicate, combine | Condense your insights into tangible representations that can be re-used in the rest of the project and help to communicate findings to the team and client. |
De kolommen 1-4 in de volgende matrix komen uit bovenstaande bronnen. De laatste kolom is een ruwe poging om veel gebruikte onderzoeksmethoden voor CMGT aan te geven.
| onderzoeksmethode | type | HBO-i | CMD | CMGT |
|---|---|---|---|---|
| available product analysis | library | x | ||
| best good and bad practices | library | x | x | x |
| community research | library | x | ||
| competitive analysis | library | x | x | x |
| design pattern research | library | x | x | x |
| expert interview | library | x | x | x |
| literature study | library | x | x | x |
| SWOT analysis | library | x | ||
| benchmark creation | library | x | x | |
| trend analysis | library | x | x | |
| document analysis | field | x | ||
| domain modelling | field | x | ||
| explore user requirements | field | x | x | |
| focus group | field | x | x | x |
| interview | field | x | x | x |
| observation | field | x | x | |
| problem analysis | field | x | x | |
| stakeholder analysis | field | x | ||
| survey | field | x | x | x |
| task analysis | field | x | ||
| context mapping | field | x | ||
| diary study | field | x | ||
| bag tour | field | x | ||
| cultural probes | field | x | ||
| fly on the wall | field | x | x | |
| participant observation | field | x | ||
| card sorting | field | x | ||
| day in the life | field | x | ||
| A/B testing | lab | x | x | x |
| component test | lab | x | ||
| computer simulation | lab | x | ||
| data analysis | lab | x | ||
| hardware validation | lab | x | ||
| non-functional test | lab | x | ||
| security test | lab | x | ||
| system test | lab | x | ||
| unit test | lab | x | ||
| usability test | lab | x | x | x |
| field trial | lab | x | ||
| online analytics | lab | x | ||
| wizard of Oz | lab | x | ||
| biometrics | lab | x | ||
| thinking aloud | lab | x | x | |
| benchmark test | showroom | x | ||
| ethical check | showroom | x | ||
| guidline conformity analysis | showroom | x | ||
| peer review | showroom | x | x | x |
| pitch | showroom | x | x | x |
| (product) (quality) review | showroom | x | x | x |
| static program analysis | showroom | x | ||
| heuristic evaluation | showroom | x | ||
| provocative prototyping | showroom | x | x | |
| co-reflection | showroom | x | ||
| expo | showroom | x | ||
| USP (unique selling point) | showroom | x | ||
| brainstorm | workshop | x | x | |
| business case exploration | workshop | x | ||
| code review | workshop | x | ||
| decomposition | workshop | x | ||
| gap analysis | workshop | x | ||
| IT architecture sketching | workshop | x | ||
| multi-criteria decision making | workshop | x | ||
| prototyping | workshop | x | x | x |
| requirements prioritization | workshop | x | ||
| root cause analysis | workshop | x | ||
| morphological chart | workshop | x | ||
| scamper | workshop | x | ||
| tinkering | workshop | x | ||
| co-creation | workshop | x | x | |
| proof of concept | workshop | x | ||
| sketching | workshop | x | ||
| ideation | workshop | x | ||
| storytelling | workshop | x | ||
| concept | stepping stones | x | ||
| empathy map | stepping stones | x | ||
| mood board | stepping stones | x | ||
| requirement list | stepping stones | x | ||
| task analysis | stepping stones | x | ||
| business model canvas | stepping stones | x | ||
| customer journey | stepping stones | x | x | |
| expert review report | stepping stones | x | x | |
| persona | stepping stones | x | x | |
| risk analysis | stepping stones | x | ||
| test report | stepping stones | x | ||
| comparison chart | stepping stones | x | ||
| design specification | stepping stones | x | ||
| inspiration wall | stepping stones | x | ||
| prototype | stepping stones | x | x | |
| scenario | stepping stones | x | x |
De genoemde onderzoeksmethoden kunnen ook ingedeeld worden naar project fase (probleem definitie-->analyse-->design-->realisatie-->evaluatie). De HBO-i heeft dit gedaan. Dit zie je als je de switch “group by phase” verschuift https://ictresearchmethods.nl/. Je vindt hier in het menu ook verdiepende informatie over “research patterns” en het “DOT framework”.
Bij je eigen afstudeeronderzoek kun je dus nadenken over wat je doel is en dan een keuze maken over welke methode hiervoor het meest geschikt is per fase van je onderzoek.