See IKIWISI in All languages combined, or Wiktionary
{ "head_templates": [ { "args": { "1": "en", "2": "phrase" }, "expansion": "IKIWISI", "name": "head" } ], "lang": "English", "lang_code": "en", "pos": "phrase", "senses": [ { "alt_of": [ { "word": "I'll know it when I see it" } ], "categories": [ { "kind": "other", "name": "English entries with incorrect language header", "parents": [ "Entries with incorrect language header", "Entry maintenance" ], "source": "w" }, { "kind": "other", "name": "Pages with 1 entry", "parents": [], "source": "w" }, { "kind": "other", "name": "Pages with entries", "parents": [], "source": "w" } ], "examples": [ { "ref": "1989, Software risk management, page 125:", "text": "information overload situations; user differences of opinion on preferred displays or interaction styles; or a number of users saying such things as, \"I can't really tell you what I need, but I'll know it when I see it (IKIWISI).\"", "type": "quote" }, { "ref": "1990, Strategies for software engineering: the management of risk and quality:", "text": "Another sort of prototype helps in the situation where you are not even sure what behaviour you want - the ikiwisi' syndrome (I'll know it when I see it). This is the sort of prototype that is built for evaluating user interfaces. Prototyping is therefore experimentation designed to yield information for the development process", "type": "quote" }, { "ref": "1991, Managing Quality Dynamics, page 26:", "text": "customers or users do not always know what they want or what they need. Before the arrival of the microcomputer, for example, very few customers would have been capable of expressing their need for a microcomputer. The needs and segments covered only appear clearly once the product or service is on the market - this is known as the 'ikiwisi' syndrome (I'll know it when I see it). But what are the needs of the customer?", "type": "quote" }, { "ref": "1991, Towards a Theory of Cognition and Computing, page 175:", "text": "Users also often find it difficult to define what they want in abstract or verbal terms independent of some working system : I'll know it when I see it' (IKIWISI). A prototype provides a means for users to say more precisely what they do or do not want. The general idea, then, is to construct a series of prototypes, to allow prospective users to examine each one, and say what changes they want in the next one.", "type": "quote" }, { "ref": "1995, Electronic Document Management Systems: A Portable Consultant:", "text": "An acronym has been coined in this industry to express the \"I'll know it when I see it\" phenomena: IKIWISI.", "type": "quote" }, { "ref": "1997 Design, Specification and Verification of Interactive Systems ’97: Proceedings of the Eurographics Workshop in Granada, Spain, June 4–6, 1997 (2012 reprint)", "text": "One of the fundamental difficulties of creating computer systems is the IKIWISI principle. I find it hard to envisage what it is I want, but I am sure that I'll know it when I see it. This principle describes the behaviour of users, who find it far easier to assess a working model than to review a technical document" } ], "glosses": [ "Acronym of I'll know it when I see it." ], "id": "en-IKIWISI-en-phrase-DHOSnJVZ", "links": [ [ "I'll", "I'll#English" ], [ "know", "know#English" ], [ "it", "it#English" ], [ "when", "when#English" ], [ "see", "see#English" ] ], "related": [ { "word": "Potter Stewart test" } ], "tags": [ "abbreviation", "acronym", "alt-of" ], "wikipedia": [ "IKIWISI" ] } ], "word": "IKIWISI" }
{ "head_templates": [ { "args": { "1": "en", "2": "phrase" }, "expansion": "IKIWISI", "name": "head" } ], "lang": "English", "lang_code": "en", "pos": "phrase", "related": [ { "word": "Potter Stewart test" } ], "senses": [ { "alt_of": [ { "word": "I'll know it when I see it" } ], "categories": [ "English acronyms", "English entries with incorrect language header", "English lemmas", "English phrases", "English terms with quotations", "Pages with 1 entry", "Pages with entries" ], "examples": [ { "ref": "1989, Software risk management, page 125:", "text": "information overload situations; user differences of opinion on preferred displays or interaction styles; or a number of users saying such things as, \"I can't really tell you what I need, but I'll know it when I see it (IKIWISI).\"", "type": "quote" }, { "ref": "1990, Strategies for software engineering: the management of risk and quality:", "text": "Another sort of prototype helps in the situation where you are not even sure what behaviour you want - the ikiwisi' syndrome (I'll know it when I see it). This is the sort of prototype that is built for evaluating user interfaces. Prototyping is therefore experimentation designed to yield information for the development process", "type": "quote" }, { "ref": "1991, Managing Quality Dynamics, page 26:", "text": "customers or users do not always know what they want or what they need. Before the arrival of the microcomputer, for example, very few customers would have been capable of expressing their need for a microcomputer. The needs and segments covered only appear clearly once the product or service is on the market - this is known as the 'ikiwisi' syndrome (I'll know it when I see it). But what are the needs of the customer?", "type": "quote" }, { "ref": "1991, Towards a Theory of Cognition and Computing, page 175:", "text": "Users also often find it difficult to define what they want in abstract or verbal terms independent of some working system : I'll know it when I see it' (IKIWISI). A prototype provides a means for users to say more precisely what they do or do not want. The general idea, then, is to construct a series of prototypes, to allow prospective users to examine each one, and say what changes they want in the next one.", "type": "quote" }, { "ref": "1995, Electronic Document Management Systems: A Portable Consultant:", "text": "An acronym has been coined in this industry to express the \"I'll know it when I see it\" phenomena: IKIWISI.", "type": "quote" }, { "ref": "1997 Design, Specification and Verification of Interactive Systems ’97: Proceedings of the Eurographics Workshop in Granada, Spain, June 4–6, 1997 (2012 reprint)", "text": "One of the fundamental difficulties of creating computer systems is the IKIWISI principle. I find it hard to envisage what it is I want, but I am sure that I'll know it when I see it. This principle describes the behaviour of users, who find it far easier to assess a working model than to review a technical document" } ], "glosses": [ "Acronym of I'll know it when I see it." ], "links": [ [ "I'll", "I'll#English" ], [ "know", "know#English" ], [ "it", "it#English" ], [ "when", "when#English" ], [ "see", "see#English" ] ], "tags": [ "abbreviation", "acronym", "alt-of" ], "wikipedia": [ "IKIWISI" ] } ], "word": "IKIWISI" }
Download raw JSONL data for IKIWISI meaning in English (3.2kB)
This page is a part of the kaikki.org machine-readable English dictionary. This dictionary is based on structured data extracted on 2024-12-15 from the enwiktionary dump dated 2024-12-04 using wiktextract (8a39820 and 4401a4c). The data shown on this site has been post-processed and various details (e.g., extra categories) removed, some information disambiguated, and additional data merged from other sources. See the raw data download page for the unprocessed wiktextract data.
If you use this data in academic research, please cite Tatu Ylonen: Wiktextract: Wiktionary as Machine-Readable Structured Data, Proceedings of the 13th Conference on Language Resources and Evaluation (LREC), pp. 1317-1325, Marseille, 20-25 June 2022. Linking to the relevant page(s) under https://kaikki.org would also be greatly appreciated.