To answer your specific question, to measure how well a text editor integrates with a programming language, you just ask its users to rate how well it does. It's bread and butter for many product managers and user researchers, to justify to execs why a particular feature ought to be built rather than other ones (combined with other factors like cost, risk, strategy, etc.).Īnd there you have it. Several hundred randomly chosen survey respondents will generally give you the statistical precision you need.Ĭompanies do this all the time. Both of these can be done using Likert scales, most commonly giving a score between 1 (does not meet needs at all) to 5 (completely meets needs), with intermediate values being "mostly doesn't", "somewhat", and "mostly". Third, survey users to determine both the relative importances of those features/requirements, as well as how well each editor meets their needs for each feature/requirement. Second, tag and categorize those responses into a standardized list of features/requirements. There is absolutely an objective process for identifying criteria and identifying how well it meets those criteria.įirst, an open-ended survey among text editor users to identify the features/requirements that matter to them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |