I've just transitioned to a new role at IBM - from the BPM Services organization to the BPM Product Management organization. This is a position that I have wanted for a long time - Truth be told my original application to Lombardi Software in 2006 was for a position in their product management group, and the slot in their service group was just meant to "get my foot in the door".
Serendipity is an amazing thing, and much to my surprise I really loved my service job. I was able to work with really smart folks all over the world on a wide variety of process projects, and I learned a great deal about what BPM can really be and about what BPM is definitely not. Hopefully the things that I learned will contribute to the creation of better products for all of my past and future process colleagues.
I've received many congratulations on my new role, and they're all very appreciated... but there's one compliment I've received that stands out - recognition by my peers that I am a "Thought Leader" in BPM.
That's a wonderful compliment... but it's not really true. I'm not a "Thought Leader"... I am a "Thought Harvester".
I may have had an original thought or two of my own, but the reality is that the vast majority of my posts on BPM (and programming in general) are borrowed thoughts. The community of BPM practitioners is amazingly generous with their thoughts, and it's through connections with you that I get all of "my" good ideas. Thanks to all of you who've provided the inspiration and insights for my ramblings.
Going forward, I think we all have a great future as Process, Rules, Cases etc. begin to merge into comprehensive solutions. As more and more of our technical infrastructure components disappear within the boundaries of our "business software appliances" we'll be able to empower non-programmers to build more of their own solutions - sort of putting ourselves out of a job, but not really. There are always new challenges... and plenty of old problems to solve.
Serendipity is an amazing thing, and much to my surprise I really loved my service job. I was able to work with really smart folks all over the world on a wide variety of process projects, and I learned a great deal about what BPM can really be and about what BPM is definitely not. Hopefully the things that I learned will contribute to the creation of better products for all of my past and future process colleagues.
I've received many congratulations on my new role, and they're all very appreciated... but there's one compliment I've received that stands out - recognition by my peers that I am a "Thought Leader" in BPM.
That's a wonderful compliment... but it's not really true. I'm not a "Thought Leader"... I am a "Thought Harvester".
I may have had an original thought or two of my own, but the reality is that the vast majority of my posts on BPM (and programming in general) are borrowed thoughts. The community of BPM practitioners is amazingly generous with their thoughts, and it's through connections with you that I get all of "my" good ideas. Thanks to all of you who've provided the inspiration and insights for my ramblings.
Going forward, I think we all have a great future as Process, Rules, Cases etc. begin to merge into comprehensive solutions. As more and more of our technical infrastructure components disappear within the boundaries of our "business software appliances" we'll be able to empower non-programmers to build more of their own solutions - sort of putting ourselves out of a job, but not really. There are always new challenges... and plenty of old problems to solve.
No comments:
Post a Comment