http://blogs.msdn.com/b/scottwoo/archive/2005/09/21/472891.aspxNow the cat is out of the bag on a couple of areas (Workflow and Adapters) where we need some more incredibly motivated, clever, articulate folks to help us make a real impact on the business in the following two roles: 1) Senior Workflow Technicalen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/scottwoo/archive/2005/09/21/472891.aspx#479682Tue, 11 Oct 2005 20:25:25 GMT91d46819-8472-40ad-a661-2c78acb4018c:479682AnonDave: You can always rehost the workflow designer anywhere you want. It doesn't have to be inside Visual Studio.<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=479682" width="1" height="1">http://blogs.msdn.com/b/scottwoo/archive/2005/09/21/472891.aspx#473602Sat, 24 Sep 2005 20:44:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:473602Dave Runyan / drunyan8315@msn.comScott, I am not applying for the jobs, but I want to talk to you about how, or if, you plan to make the Workflow Designer more accessible to the Business Analyst. <br> <br>I am an independant consultant with many years of both programming and process development experience. I fear that as long as the Workflow Designer is hidden inside VS, it won't get traction with the Business Analyst community. The benefits of workflow I see you and your team touting are mostly around the developer and allowing them to develop robust and loosely-coupled workflows. <br> <br>But my clients are the Business Process Managers and their right-hand-men, the Business Architects and Analysts. They want to be able to enable business processes tht are easily evolved to support business agility, and to have a way to express their requirements to the developers with some rigor. <br> <br>In my career I have had some success with process modeling tools in doing this, and it occurs to me that your tool would be very good at this - but it is &quot;inside&quot; a programmer-oriented environment that is not very approachable to the BA, much less affordable. IMHO, the BA is the way into the big enterprise. With outsourcing / nearsourcing of development so common, I think a lightweight toolset that is business analyst / architect friendly would pull a lot of Microsoft product behind it. As it is however, I could not recommend it to my kind of client without fighting IT, because of how it is packaged. <br> <br><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=473602" width="1" height="1">http://blogs.msdn.com/b/scottwoo/archive/2005/09/21/472891.aspx#473434Sat, 24 Sep 2005 01:21:19 GMT91d46819-8472-40ad-a661-2c78acb4018c:473434JoeHow is the Senior Workflow Technical Product Manager different from Paul Andrew's job?<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=473434" width="1" height="1">