<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Service design &#8211; Say Yeah!</title>
	<atom:link href="https://sayyeah.com/glossary/category/service-design/feed/" rel="self" type="application/rss+xml" />
	<link>https://sayyeah.com</link>
	<description>Digital management consulting that shapes more effective organizations.</description>
	<lastBuildDate>Thu, 24 Nov 2022 00:40:42 +0000</lastBuildDate>
	<language>en-CA</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.4</generator>

<image>
	<url>https://insights.sayyeah.com/wp-content/uploads/2021/10/cropped-apple-touch-icon-32x32.png</url>
	<title>Service design &#8211; Say Yeah!</title>
	<link>https://sayyeah.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Use case</title>
		<link>https://sayyeah.com/glossary/#use-case</link>
		
		<dc:creator><![CDATA[Kate Matesic]]></dc:creator>
		<pubDate>Wed, 23 Nov 2022 16:01:49 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary/#</guid>

					<description><![CDATA[<p>A use case in design or software development is a way of identifying specific needs that a person might have in engaging with a product or service to accomplish something. Use cases go beyond the person&#8217;s needs, objectives, and outcomes to include describing how the people and systems involved interact with each other through the [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#use-case">Use case</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A use case in design or software development is a way of identifying specific needs that a person might have in engaging with a product or service to accomplish something.</p>
<p>Use cases go beyond the person&#8217;s needs, objectives, and outcomes to include describing how the people and systems involved interact with each other through the flows and engagements that are necessary to achieve the goal.</p>
<p>Use cases are a way of determining what the design requirements should be when delivering a product or service, including mapping these requirements back to user goals and actions, interface behaviours, and organizational needs and objectives.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#use-case">Use case</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Personas</title>
		<link>https://sayyeah.com/glossary/#personas</link>
		
		<dc:creator><![CDATA[Kate Matesic]]></dc:creator>
		<pubDate>Wed, 23 Nov 2022 15:53:51 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary/#</guid>

					<description><![CDATA[<p>Also known as: User personas, profiles, archetypes, avatars Personas are example profiles of customers, based on characteristics identified in user or market research. They help organizations paint pictures of how different characteristics may impact how users experience a product or service by identifying common goals, needs, and behaviours for a given user group. Personas at [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#personas">Personas</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Also known as: User personas, profiles, archetypes, avatars</p>
<p>Personas are example profiles of customers, based on characteristics identified in user or market research. They help organizations paint pictures of how different characteristics may impact how users experience a product or service by identifying common goals, needs, and behaviours for a given user group. </p>
<p>Personas at their best are the result of user research, including qualitative and quantitative data from talking to and observing users. Organizations use personas to identify the needs of their customers and understand broader user group characteristics. </p>
<p>At their worst, personas are focused on demographic data that implies an average set of customers to target or engage with that does not help improve product or service delivery. It is always best to begin with jobs-to-be-done (JTBD) and use cases to craft an understanding of how customers will engage with your product or service, before considering other aspects of a customer such as demographics.</p>
<p>Implementing personas in the strategy or concept stage of a project can identify gaps and uncover new business opportunities, while personas considerate of intersectional factors can build a rich understanding of the nuance and diversity of a user base.  </p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#personas">Personas</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>JTBD</title>
		<link>https://sayyeah.com/glossary/#jtbd</link>
		
		<dc:creator><![CDATA[Kate Matesic]]></dc:creator>
		<pubDate>Tue, 31 Aug 2021 12:16:59 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary#</guid>

					<description><![CDATA[<p>Jobs-to-be-done is an approach to user research and design strategy product development and consumer insights that helps teams understand why users would choose to use their product and what s situations and goals drive them to make a purchase decision. </p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#jtbd">JTBD</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Jobs-to-be-done (JTBD) is a model for understanding what circumstances and needs cause someone to act or seek a solution in any given situation.</p>
<p>This framework is applied in product strategy, service design, and user research to help organizations understand what motivates a person so that the organization may align a product or service to that person&#8217;s objective and desired outcome.</p>
<p>In its purest sense, a person will consider an outcome they wish to reach in order to satisfy a need. That is the <strong>job-to-be-done</strong>. This could be turning on the TV to <strong>decompress after a long day</strong>. It could be drinking a milkshake while driving to work to <strong>feel full enough to get through the morning</strong>.</p>
<p>Understanding this foundational need allows an organization to consider alternatives, competitors, and opportunities to fulfill the foundational user need, or JTBD.</p>
<p><a class="text:underline" href="https://www.youtube.com/watch?v=Stc0beAxavY">In this video, Clayton Christensen talks McDonald&#8217;s, milkshakes, and JTBD.</a></p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#jtbd">JTBD</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>OKRs</title>
		<link>https://sayyeah.com/glossary/#okrs</link>
		
		<dc:creator><![CDATA[Lee Dale]]></dc:creator>
		<pubDate>Wed, 28 Oct 2020 21:11:02 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary#</guid>

					<description><![CDATA[<p>An OKR, or Objectives and Key Results, is a framework and management structure that organizations use to define large, overarching goals. They are goals that are quantitatively (numerical or metric) measurable. They are ambitious organizational goals, not small objectives within a project. One example of an OKR would be: Objective: “Increase the engagement and inclusivity [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#okrs">OKRs</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>An OKR, or Objectives and Key Results, is a framework and management structure that organizations use to define large, overarching goals. They are goals that are quantitatively (numerical or metric) measurable. They are ambitious organizational goals, not small objectives within a project.</p>
<p>One example of an OKR would be:</p>
<p>Objective: “Increase the engagement and inclusivity of our internal team structure”</p>
<p>Key result 1: “Employee turnover down 10% over the next two quarters”<br />
Key result 2: “Implement a diversity team and at least 3 events or initiatives to boost inclusion”<br />
Key result 3: “Raise employee engagement ratings by 30% over the next two quarters”</p>
<p>From these larger, big-picture OKRs, your organization can define smaller indicators of success within initiatives using KPIs (key performance indicators).</p>
<p>In a marketing OKR framework, a KPI for a website might be something like &#8220;maintain a bounce rate below 70%&#8221;, while the key result this would inform is &#8220;Hit 100% of each quarter&#8217;s goals for closing new business&#8221;. There would be a series of KPIs that would inform this key result so that you could both validate how the KPIs impact the key result in order to refine them and check on the KPIs on a more frequent interval to understand how you&#8217;re trending toward the larger quarterly goal.</p>
<p>Both OKRs and KPIs are key for setting measurable goals and growth plans in organizations in order to achieve impactful, transformative organizational objectives.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#okrs">OKRs</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Diary study</title>
		<link>https://sayyeah.com/glossary/#diary-study</link>
		
		<dc:creator><![CDATA[Lee Dale]]></dc:creator>
		<pubDate>Wed, 19 Aug 2020 22:52:29 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary/#</guid>

					<description><![CDATA[<p>A diary study is a type of qualitative user research, which typically involves a user recording their activities, thoughts, or behaviours over time at regular intervals (for example, when you wake up, or just before bed, each day for a week, after a phone call, or each time you brush your teeth, and so on). [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#diary-study">Diary study</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A diary study is a type of qualitative user research, which typically involves a user recording their activities, thoughts, or behaviours over time at regular intervals (for example, when you wake up, or just before bed, each day for a week, after a phone call, or each time you brush your teeth, and so on). </p>
<p>This type of qualitative data helps teams better understand user behaviour, especially in cases where it isn&#8217;t practical to observe users directly. A diary study enables organizations to see how the usage of a product or service varies depending on different contexts and over time.</p>
<p>A public transit user recording when they took public transit, along with their experiences, thoughts, conversations, and differences about each trip over a period of two weeks would be an example of a diary study for a public transit agency.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#diary-study">Diary study</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Ethnography</title>
		<link>https://sayyeah.com/glossary/#ethnography</link>
		
		<dc:creator><![CDATA[Kate Matesic]]></dc:creator>
		<pubDate>Tue, 18 Aug 2020 23:25:51 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary/#</guid>

					<description><![CDATA[<p>Ethnography describes a form of research that involves the observation of people. It is a qualitative research method based on observing ideally natural behaviour and speaking with users in context. For example, an ethnographic study for a research question for a pharmacy would involve observing and speaking to pharmacists in situ at the pharmacy. This [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#ethnography">Ethnography</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Ethnography describes a form of research that involves the observation of people. It is a qualitative research method based on observing ideally natural behaviour and speaking with users in context. </p>
<p>For example, an ethnographic study for a research question for a pharmacy would involve observing and speaking to pharmacists in situ at the pharmacy. This kind of unobtrusive approach to research within the natural environment aims to gain genuine data about how someone behaves and direct insight into a process. </p>
<p>This is especially vital in understanding people and processes where it may be impossible or difficult to accurately document, reflect, or draw insight from other, non-observational research methods such as user interviews or surveys. </p>
<p>A complement to an ethnographic study, or a best compromise where this kind of direct observation may not be possible, could be a diary study.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#ethnography">Ethnography</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Evaluative research</title>
		<link>https://sayyeah.com/glossary/#evaluative-research</link>
		
		<dc:creator><![CDATA[Kate Matesic]]></dc:creator>
		<pubDate>Mon, 17 Aug 2020 18:36:12 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary/#</guid>

					<description><![CDATA[<p>Evaluative research is a type of user research that aims to determine or evaluate how well a product or service is meeting the needs of its users. Evaluative research is key to identifying specific issues with a product or service that is in development or already in market. As such, evaluative research practices typically occur [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#evaluative-research">Evaluative research</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Evaluative research is a type of <a href="https://sayyeah.com/approach/research/">user research</a> that aims to determine or evaluate how well a product or service is meeting the needs of its users.</p>
<p>Evaluative research is key to identifying specific issues with a product or service that is in development or already in market. As such, evaluative research practices typically occur once a product or service is in development, rather than during early exploratory phases.</p>
<p>Research methods used as part of evaluative research include <a href="https://sayyeah.com/approach/usability-testing/">usability testing</a>, A/B testing, and <a href="https://sayyeah.com/glossary/#first-click-study">first-click testing</a>, all aimed at gaining insights into participants&#8217; behaviour while using a product or service and on an ongoing basis.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#evaluative-research">Evaluative research</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Generative research</title>
		<link>https://sayyeah.com/glossary/#generative-research</link>
		
		<dc:creator><![CDATA[Kate Matesic]]></dc:creator>
		<pubDate>Mon, 17 Aug 2020 18:33:13 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary/#</guid>

					<description><![CDATA[<p>Generative research, also known as exploratory research, is a type of research typically used in the earlier stages of research, strategy, and design processes. Generative research can include activities like user interviews, ethnographic observation, or workshops with the aim of validate a market opportunity, concept, or to understand what users need in order to better [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#generative-research">Generative research</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Generative research, also known as exploratory research, is a type of research typically used in the earlier stages of research, strategy, and design processes. Generative research can include activities like user interviews, ethnographic observation, or workshops with the aim of validate a market opportunity, concept, or to understand what users need in order to better conceptualize a product or service.</p>
<p>Through generative research, teams can find ways to innovate from the building blocks of a comprehensive understanding of user pain points, contexts, and potential use cases of a product or service.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#generative-research">Generative research</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Current state</title>
		<link>https://sayyeah.com/glossary/#current-state</link>
		
		<dc:creator><![CDATA[Kate Matesic]]></dc:creator>
		<pubDate>Fri, 10 Jul 2020 21:19:44 +0000</pubDate>
				<guid isPermaLink="false">https://sayyeah.com/glossary/#</guid>

					<description><![CDATA[<p>Current state is a term used in service design, often during service blueprinting, to identify the current service model and customer experience for an existing service. The current state of a service includes everything from the processes in place, to the current customer journey, to the people and other elements operating &#8220;behind the scenes&#8221; that [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#current-state">Current state</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Current state is a term used in service design, often during service blueprinting, to identify the current service model and customer experience for an existing service. </p>
<p>The current state of a service includes everything from the processes in place, to the current customer journey, to the people and other elements operating &#8220;behind the scenes&#8221; that allow a service to be fulfilled.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/glossary/#current-state">Current state</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
