<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: 23C3 Roundup: Free and Open Source Softw&#8230; erm&#8230; Marketing?!</title>
	<atom:link href="http://stefan-lesser.com/2007/01/23c3-roundup-free-and-open-source-softw-erm-marketing/feed/" rel="self" type="application/rss+xml" />
	<link>http://stefan-lesser.com/2007/01/23c3-roundup-free-and-open-source-softw-erm-marketing/</link>
	<description>linking people and technology, moving minds and machines</description>
	<lastBuildDate>Tue, 06 Jan 2009 21:48:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Marco Lamonaca</title>
		<link>http://stefan-lesser.com/2007/01/23c3-roundup-free-and-open-source-softw-erm-marketing/comment-page-1/#comment-15</link>
		<dc:creator>Marco Lamonaca</dc:creator>
		<pubDate>Mon, 11 Jun 2007 12:37:07 +0000</pubDate>
		<guid isPermaLink="false">http://stefan-lesser.com/wordpress/?p=23#comment-15</guid>
		<description>&quot; For average users the UI practically _is_ the application (i.e. as much as we may wish to, they don’t care whether it’s programmed well, only if they can use it) &quot;
... this reminds of something I&#039;ve said long time ago about, well, let&#039;s call it &#039;Kiosk Systems&#039;:
&quot; It doesn&#039;t matter how good, advanced, complex or &#039;promising&#039; the (software) back-end of a system is. In the end the front-end itself (meaning the user interface) will let people decide about whether the (whole) product is successful or not. &quot;
I explicitly did not say &#039;good&#039; or &#039;bad&#039;. It&#039;s the &#039;end-user&#039; accepting it. If he doesn&#039;t like it (and one can really use the term &#039;like&#039; in a matter of taste) or worst case cannot &#039;use/control&#039; it, he won&#039;t buy (in terms of accepting) it. Not to forget: when talking about decision makers, you have to mix up the &#039;end-user&#039; expectations with the expectations from those people who originally &#039;ordered&#039; that piece of software. Biggest problem in that case usually is: we cannot foresee how people (end-users) will use an application.
Enough for now,
Stay in touch,...
Marco
</description>
		<content:encoded><![CDATA[<p>&#8221; For average users the UI practically _is_ the application (i.e. as much as we may wish to, they don’t care whether it’s programmed well, only if they can use it) &#8221;<br />
&#8230; this reminds of something I&#8217;ve said long time ago about, well, let&#8217;s call it &#8216;Kiosk Systems&#8217;:<br />
&#8221; It doesn&#8217;t matter how good, advanced, complex or &#8216;promising&#8217; the (software) back-end of a system is. In the end the front-end itself (meaning the user interface) will let people decide about whether the (whole) product is successful or not. &#8221;<br />
I explicitly did not say &#8216;good&#8217; or &#8216;bad&#8217;. It&#8217;s the &#8216;end-user&#8217; accepting it. If he doesn&#8217;t like it (and one can really use the term &#8216;like&#8217; in a matter of taste) or worst case cannot &#8216;use/control&#8217; it, he won&#8217;t buy (in terms of accepting) it. Not to forget: when talking about decision makers, you have to mix up the &#8216;end-user&#8217; expectations with the expectations from those people who originally &#8216;ordered&#8217; that piece of software. Biggest problem in that case usually is: we cannot foresee how people (end-users) will use an application.<br />
Enough for now,<br />
Stay in touch,&#8230;<br />
Marco</p>
]]></content:encoded>
	</item>
</channel>
</rss>
