People Matter

  • August 3, 2011
  • Scott

I’ve said it often, but the people in your business – and on your projects – matter.  Doug Turner writes on his blog, with a slight twist to an old time-management proverb:

Well the issue of throwing more people at a solution and not getting to it any faster still exists, but now we have a new problem. Not only are we attempting to solve a problem by just throwing resources at it, we’re not even throwing the right resources at it for it to get accomplished at all. If you don’t begin with the right team, you’re not going to get the results you were hoping to get, no matter how positive your outlook, or how insistently you promised your superiors the job would get done.

My favorite passage, however:

With knowledge work especially, it’s the people and team you assemble that are going to make or break your solution. It’s not how much money can you, or can’t you, spend. It’s not how much time you do, or do not, have. It’s the people & their skillset that are going to help you to succeed. This is key to being successful.

You could just swap out “knowledge work” with BPM.  Doug’s blog ties back to a point I’ve made time and again with customers and colleagues, and on this blog:  an hour of labor is an input, not an outputThe hour of labor of the “right person” for a project is valuable and highly leveraged.  The hour of labor of the wrong person for a project is no better than no hour of labor at all.

It isn’t just an issue of trying to cram too much work into too short a time – if you have the wrong people, sometimes it just can’t get done.  And this is why it is so important for BP3 to build the best team we possibly can.


Related Posts
  • June 15, 2017
  • Krista

We are excited to announce our first customer speaker for Driven 2017. Quang Ton, leader of Schlumberger's pro...

  • June 12, 2017
  • Scott

We had the pleasure of presenting Brazos CX Insights to the bpmNEXT 2017 conference in April.  As we've previ...

  • June 11, 2017
  • Scott

Anatoly does a great job of explaining the event types and why you really only need 5 or 6 of them to fully ex...