<?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>Problem Solving &#8211; Say Yeah!</title>
	<atom:link href="https://sayyeah.com/digital-insights/tag/problem-solving/feed/" rel="self" type="application/rss+xml" />
	<link>https://sayyeah.com</link>
	<description>Digital management consulting that shapes more effective organizations.</description>
	<lastBuildDate>Mon, 03 May 2021 13:28:07 +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>Problem Solving &#8211; Say Yeah!</title>
	<link>https://sayyeah.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>William Peitri: stop creating features and solve problems</title>
		<link>https://sayyeah.com/digital-insights/dont-create-features-solve-problems/</link>
		
		<dc:creator><![CDATA[Lee Dale]]></dc:creator>
		<pubDate>Tue, 07 Oct 2014 21:09:00 +0000</pubDate>
				<category><![CDATA[Quotes]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[product design]]></category>
		<category><![CDATA[product planning]]></category>
		<guid isPermaLink="false">http://sayyeah.com/sayYeah/sayYeahNewSite/wordpress/dont-create-features-solve-problems/</guid>

					<description><![CDATA[<p>Don’t create features, solve problems. William Pietri, responding to a question on Quora asking whether it’s best to tell the product team what to do or empower them to bring the right product to market. William continues: If you’re telling (your product team) “go build Feature X” and expect them to make the thing you imagine, [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/digital-insights/dont-create-features-solve-problems/">William Peitri: stop creating features and solve problems</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<blockquote><p>Don’t create features, solve problems.</p></blockquote>
<div class="attribution">
<p>William Pietri, <a href="http://www.quora.com/I-am-the-CEO-at-a-SaaS-startup-My-dev-team-is-complaining-that-requirements-are-not-detailed-enough-though-we-are-Agile-I-feel-like-they-are-asking-to-bricklayers-instead-of-architects-Do-I-tell-them-to-take-more-initiative-in-understanding-the-customer-problem-or-tell-them-what-to-build/answer/William-Pietri">responding to a question on Quora</a> asking whether it’s best to tell the product team what to do or empower them to bring the right product to market.</p>
</div>
<p><span id="more-263"></span></p>
<div class="attribution">
<p>William continues:</p>
<blockquote><p><em>If you’re telling (your product team) “go build Feature X” and expect them to make the thing you imagine, they’re going to want a spec. Instead, have them solve problems. E.g., “Users are struggling with problem Y; come up with some solutions, test them out, and then let’s pick the best one together.”</em></p></blockquote>
<p>This perfectly frames the trouble with defining a product by its features. Features alone ignore the purpose of the product and how it’s going to serve its users and your business.</p>
<p>Don’t focus on features, focus on the market and how you’re going to deliver value to them. Then design your product around solving problems that deliver that value. The features are defined by the problem solving, not the other way around.</p>
</div>
<p>The post <a rel="nofollow" href="https://sayyeah.com/digital-insights/dont-create-features-solve-problems/">William Peitri: stop creating features and solve problems</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Our problem solving expertise, from transaction flows, to rich information, to multi-device experiences.</title>
		<link>https://sayyeah.com/digital-insights/our-problem-solving-expertise-from-transaction/</link>
		
		<dc:creator><![CDATA[Lee Dale]]></dc:creator>
		<pubDate>Tue, 22 Jul 2014 17:30:24 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[clients]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[product strategy]]></category>
		<category><![CDATA[work]]></category>
		<guid isPermaLink="false">http://sayyeah.com/sayYeah/sayYeahNewSite/wordpress/our-problem-solving-expertise-from-transaction/</guid>

					<description><![CDATA[<p>For the past couple of years, we’ve framed our expertise not by industry, but by the type of problem solving we do, which we’ve successfully applied to projects across many client verticals. When discussing our expertise, we like to talk about transactional flows, large amounts of information, and, more recently, how to support users across [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/digital-insights/our-problem-solving-expertise-from-transaction/">Our problem solving expertise, from transaction flows, to rich information, to multi-device experiences.</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>For the past couple of years, we’ve framed our expertise not by industry, but by the type of problem solving we do, which we’ve successfully applied to projects across many <a href="https://sayyeah.com/work/">client verticals</a>.</p>
<p>When discussing our expertise, we like to talk about transactional flows, large amounts of information, and, more recently, how to support users across multiple devices.</p>
<p>With our <a href="https://sayyeah.com">new site design</a>, we included these items on every page of the site, because they’re a vital lens to finding the right projects, helping folks better understand the work we do, and how we can help them.</p>
<p><span id="more-280"></span></p>
<p>Here’s the detailed list of the problem solving we do best:</p>
<ol>
<li>You need to improve the transactional flow within a product, such as signups, checkouts, or other calls to action.</li>
<li>You would like to provide users with access to complex data sets and large amounts of information in an intuitive, rewarding way.</li>
<li>You’d like to improve engagement across multiple screens, including defining experiences for users with multiple devices, such as a desktop, tablet, phone, and more.</li>
<li>You want to measure product releases over time to help ensure design and engineering efforts are meeting business and user goals.</li>
<li>You’re looking to bring a new product to market.</li>
</ol>
<p>If you’ve got a product you’re working on that could benefit from just this kind of problem solving, <a href="https://sayyeah.com/contact-us/">get in touch with us</a>.</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/digital-insights/our-problem-solving-expertise-from-transaction/">Our problem solving expertise, from transaction flows, to rich information, to multi-device experiences.</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Say Yeah, 100% template-free design.</title>
		<link>https://sayyeah.com/digital-insights/say-yeah-100-template-free-design/</link>
		
		<dc:creator><![CDATA[Lee Dale]]></dc:creator>
		<pubDate>Fri, 16 May 2014 17:00:00 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Say Yeah!]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[UX]]></category>
		<guid isPermaLink="false">http://sayyeah.com/sayYeah/sayYeahNewSite/wordpress/say-yeah-100-template-free-design/</guid>

					<description><![CDATA[<p>Say Yeah, 100% template-free design. These same-looking websites which take over your scrolling, essentially breaking 15 years of web standards, limiting differentiation, and starting with a splash screen are a pox on the internet. Hopefully they have a very short shelf life. By then, of course, mobile app templates will be de rigueur and we’ll have another bottle [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/digital-insights/say-yeah-100-template-free-design/">Say Yeah, 100% template-free design.</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></description>
										<content:encoded><![CDATA[<blockquote><p>Say Yeah, 100% template-free design.</p></blockquote>
<p>These same-looking websites which take over your scrolling, essentially breaking 15 years of web standards, limiting differentiation, and starting with a splash screen are a pox on the internet.</p>
<p><span id="more-5894"></span></p>
<p>Hopefully they have a very short shelf life. By then, of course, mobile app templates will be de rigueur and we’ll have another bottle against mediocrity to fight.</p>
<p>(Apologies for this rant from Lee, but no value comes of these over-designed, standards breaking shortcuts.)</p>
<p>The post <a rel="nofollow" href="https://sayyeah.com/digital-insights/say-yeah-100-template-free-design/">Say Yeah, 100% template-free design.</a> appeared first on <a rel="nofollow" href="https://sayyeah.com">Say Yeah!</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
