This is my first blog as a Gartner analyst so I’ll start by introducing myself. I previously worked at Gartner doing research for the Enterprise IT Leaders services in applications and outsourcing, where we helped senior executives (direct reports to the CIO) work through their current challenges (in a similar way to Gartner’s EXP model). Whilst working with this group, I found that BPM was a hot topic and I’m now thrilled to be part of Gartner’s BPM team since March.
One of my first tasks in my new role was to work on some research with one of my fellow analysts, Elise Olding, to help clients who are getting started with BPM. This is a big enough topic to merit three research notes and any Gartner clients reading this can access the documents via the link below:
However I’m interested to hear your experiences of getting your first BPM project off the ground. Comments on the following questions are particularly welcome:
• Whose decision was it to start BPM in your organization?
• How did you select your first project? What was it and why?
• How did you secure business buy-in?
• Did you have a clearly defined outcome and how did you measure it?
• Or, more likely, are you still struggling with all of the above?!
Whatever your experiences, I would really like to hear from you. My Twitter username is @scsearle so feel free to follow/message/interact with me there.
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.