<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Discussion on: Small Business Custom Software Development - Always a Challenge</title>
	<link>http://itknowledgeexchange.techtarget.com/customapps/small-business-custom-software-development-always-a-challenge/</link>
	<description></description>
	<pubDate>Mon, 06 Oct 2008 18:35:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.1</generator>

	<item>
		<title>By: LadyRatri</title>
		<link>http://itknowledgeexchange.techtarget.com/customapps/small-business-custom-software-development-always-a-challenge/#comment-17</link>
		<author>LadyRatri</author>
		<pubDate>Thu, 18 Oct 2007 04:23:23 +0000</pubDate>
		<guid>http://itknowledgeexchange.techtarget.com/customapps/small-business-custom-software-development-always-a-challenge/#comment-17</guid>
		<description>Beyond just tolerating "klunkiness", it's always a surprise when business or operational process is designed around the deficiencies of a tool or its interface -- especially when it adds significantly to the time it takes users to do their day-to-day work. Having moved into an application development group after starting out in operations, I have a first-hand view of that frustration. You make a good point about a very real, and often overlooked, problem. A brilliant worker can't make up for a poorly designed application.

I feel like too often, we have trouble gaining access to the specific people who will be "in the trenches" using an application, and end up talking to business owners further up the management tree instead of team members or leads who spend their time doing the work and living the specific details and problems our applications are designed to address. It's like playing a game of telephone -- the messages always get garbled.</description>
		<content:encoded><![CDATA[<p>Beyond just tolerating &#8220;klunkiness&#8221;, it&#8217;s always a surprise when business or operational process is designed around the deficiencies of a tool or its interface &#8212; especially when it adds significantly to the time it takes users to do their day-to-day work. Having moved into an application development group after starting out in operations, I have a first-hand view of that frustration. You make a good point about a very real, and often overlooked, problem. A brilliant worker can&#8217;t make up for a poorly designed application.</p>
<p>I feel like too often, we have trouble gaining access to the specific people who will be &#8220;in the trenches&#8221; using an application, and end up talking to business owners further up the management tree instead of team members or leads who spend their time doing the work and living the specific details and problems our applications are designed to address. It&#8217;s like playing a game of telephone &#8212; the messages always get garbled.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
