<?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: Meet your Process Concierge</title>
	<atom:link href="http://www.column2.com/2006/11/meet-your-process-concierge/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.column2.com/2006/11/meet-your-process-concierge/</link>
	<description>BPM, Enterprise 2.0 and technology trends in business.</description>
	<pubDate>Wed, 07 Jan 2009 18:29:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sandy Kemsley</title>
		<link>http://www.column2.com/2006/11/meet-your-process-concierge/comment-page-1/#comment-5279</link>
		<dc:creator>Sandy Kemsley</dc:creator>
		<pubDate>Tue, 14 Nov 2006 22:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.column2.com/2006/11/meet-your-process-concierge/#comment-5279</guid>
		<description>Rob, thanks for your comment, and I can see the path from a single environment to where you are now, I just don't necessarily agree with it. First of all, I think that there are ways to build a tool with different "personalities" depending on the user's skill level, and without diving into an IDE. By reducing the differences between the environments, you foster better communication between business and IT since they deal with exactly the same modeling environment (although IT will likely see many more functions). Also, there are many people who cross over between business and IT functionality (I'm often one of those), and they will find it inconvenient to have to use two tools: one to work with business users, and another to work with IT.

btw, I assumed that the two environments shared the data models in a common repository without translation based on my review, which is an improvement over what some vendors are doing.
</description>
		<content:encoded><![CDATA[<p>Rob, thanks for your comment, and I can see the path from a single environment to where you are now, I just don&#8217;t necessarily agree with it. First of all, I think that there are ways to build a tool with different &#8220;personalities&#8221; depending on the user&#8217;s skill level, and without diving into an IDE. By reducing the differences between the environments, you foster better communication between business and IT since they deal with exactly the same modeling environment (although IT will likely see many more functions). Also, there are many people who cross over between business and IT functionality (I&#8217;m often one of those), and they will find it inconvenient to have to use two tools: one to work with business users, and another to work with IT.</p>
<p>btw, I assumed that the two environments shared the data models in a common repository without translation based on my review, which is an improvement over what some vendors are doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Risany</title>
		<link>http://www.column2.com/2006/11/meet-your-process-concierge/comment-page-1/#comment-5278</link>
		<dc:creator>Rob Risany</dc:creator>
		<pubDate>Tue, 14 Nov 2006 17:40:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.column2.com/2006/11/meet-your-process-concierge/#comment-5278</guid>
		<description>Nice review Sandy... but an interesting comment on &lt;i&gt;"when we will merge the two development environments"&lt;/i&gt;.  To clarify, back in version 3 of Savvion BusinessManager, we &lt;b&gt;did&lt;/b&gt; have one integrated design environment -- our customers told us there was a gap, and asked us for a modeler which anyone could use.

As a result, Savvion, explored the best way to faciliate robust collaboration between business people and technically savvy people.  We considered the "change perspectives" button (advocatesd by many IDE centric BPM products); but that approach didn't meet our customers requirements as it was still to easy for business people to get themselves lost.  Since our approach is focused on supporting massive widespread BPM adoption (not just a few process experts) we took our studio and simplified it -- creating Savvion Process Modeler.  

The data model between Process Modeler and BPMStudio are shared.  You can take a model back and forth between the two designers and based on the "simplified view" you just don't have an opportunity to "get lost".  There's no "importing" concept between the designers -- they both can share the same business user browseable repository.

Collaboration between business and IT means meeting people where they are, not forcing them to learn complicated IDE's.  The question isn't when will we merge the two approaches -- but rather when will others in the space realize one size does not fit all?  

-Rob Risany, Product Marketing, Savvion</description>
		<content:encoded><![CDATA[<p>Nice review Sandy&#8230; but an interesting comment on <i>&#8220;when we will merge the two development environments&#8221;</i>.  To clarify, back in version 3 of Savvion BusinessManager, we <b>did</b> have one integrated design environment &#8212; our customers told us there was a gap, and asked us for a modeler which anyone could use.</p>
<p>As a result, Savvion, explored the best way to faciliate robust collaboration between business people and technically savvy people.  We considered the &#8220;change perspectives&#8221; button (advocatesd by many IDE centric BPM products); but that approach didn&#8217;t meet our customers requirements as it was still to easy for business people to get themselves lost.  Since our approach is focused on supporting massive widespread BPM adoption (not just a few process experts) we took our studio and simplified it &#8212; creating Savvion Process Modeler.  </p>
<p>The data model between Process Modeler and BPMStudio are shared.  You can take a model back and forth between the two designers and based on the &#8220;simplified view&#8221; you just don&#8217;t have an opportunity to &#8220;get lost&#8221;.  There&#8217;s no &#8220;importing&#8221; concept between the designers &#8212; they both can share the same business user browseable repository.</p>
<p>Collaboration between business and IT means meeting people where they are, not forcing them to learn complicated IDE&#8217;s.  The question isn&#8217;t when will we merge the two approaches &#8212; but rather when will others in the space realize one size does not fit all?  </p>
<p>-Rob Risany, Product Marketing, Savvion</p>
]]></content:encoded>
	</item>
</channel>
</rss>
