<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="15137" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/15137?output=omeka-xml" accessDate="2026-06-11T02:15:31+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108701">
              <text>A collaborative application of design thinking and Taguchi approach in restaurant service design for food wellbeing</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108702">
              <text>Design thinking; Food service design; Food wellbeing; Sequential incidence technique; Taguchi experiment</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108703">
              <text>Purpose: Innovative restaurant service designs impart food wellbeing to diners. This research comprehends customer aspirations and concerns in a restaurant-dining experience to develop a service design that enhances the dining experience using the design thinking approach and evaluates its efficiency using the Taguchi method of robust design. Design/methodology/approach: The sequential incidence technique defines diners' needs, which, followed by brainstorming sessions, helped create multiple service designs with important attributes. Prototype narration, as a scenario, acted as the stimulus for evaluators to respond to the WHO-5 wellbeing index scale. Scenario-based Taguchi experiment with nine foodservice attributes in two levels and the wellbeing score as the response variable helped identify levels of critical factors that develop better FWB. Findings: The study identified the best combination of factors and their preferred levels to maximize FWB in a restaurant. Food serving hygiene, followed by information about cuisine specification, and food movement in the restaurant, were important to FWB. The experiment revealed that hygiene perceptions are critical to FWB, and service designs have a significant role in it. Consumers prefer detailed information about the ingredients and recipe of the food they eat; being confident that there will be no unacceptable ingredients added to the food inspires their FWB. Research limitations/implications: Theoretically, this study contributes to the growing body of literature on design thinking and transformative service research, especially in the food industry. Practical implications: This paper details a simple method to identify and evaluate important factors that optimize FWB in a restaurant. The proposed methodology will help service designers and technology experts devise settings that consider customer priorities and contribute to their experience. Originality/value: This study helps to understand the application of design thinking and the Taguchi approach for creating robust service designs that optimize FWB.  2021, Emerald Publishing Limited.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108704">
              <text>Rejikumar G.; Aswathy A.-A.; Jose A.; Sonia M.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="108705">
              <text>Journal of Service Theory and Practice, Vol-32, No. 2, pp. 199-231.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="108706">
              <text>Emerald Group Holdings Ltd.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108707">
              <text>2022-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="108708">
              <text>&lt;a href="https://doi.org/10.1108/JSTP-12-2020-0284" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1108/JSTP-12-2020-0284&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85116357479&amp;amp;doi=10.1108%2FJSTP-12-2020-0284&amp;amp;partnerID=40&amp;amp;md5=3d88fd857e2188dacec0ce1d7a304e6c" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85116357479&amp;amp;doi=10.1108%2fJSTP-12-2020-0284&amp;amp;partnerID=40&amp;amp;md5=3d88fd857e2188dacec0ce1d7a304e6c&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108709">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="108710">
              <text>ISSN: 20556225</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108711">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108712">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="108713">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="108714">
              <text>Rejikumar G., Department of Management, Amrita Vishwa Vidyapeetham, Kochi, India; Aswathy A.-A., Indian Institute of Management Amritsar, Amritsar, India; Jose A., Department of Professional Studies, Christ University, Bangalore, India; Sonia M., School of Business and Management, Christ University, Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
