Several years ago I read Microsoft guru, public speaker, and author Scott Berkun’s book Making Things Happen: Mastering Project Management. It was a fun, easy read about how he developed his PM skills (including many “human skills”: Listen to Simon Sinek for 5 minutes on leadership and human skills) as he grew and developed at Microsoft Corporation.
The following paragraph is from his chapter on What To Do When Things Go Wrong. I was struck by how closely his words define what I think the expectations of a TSI consultant are.
Taking responsibility for something doesn’t make it your fault: it means that you will be accountable for resolving the situation. Many people fear taking responsibility because they don’t want to be held accountable and put at risk for reprimand. A good [TSI consultant has] the opposite disposition: in matters involving teams, [they] … seek out responsibility and use it to help the team and the project succeed. If relieving an engineer or tester of fear of blame will get [them] a better solution, or the same solution faster, [they will] gladly take the trade. If [our client manager] is any good, taking responsibility for a problem may earn [TSI] praise. By lending real responsibility to the problem, [we] instantly make the problem less dangerous to the project.
As consultants, we are accountable for more than just what our role is defined as and more than the specific tasks outlined in a statement of work. At Transforming Solutions Inc., we are senior, experienced consultants; that is why clients have brought us in. We are not hesitant about stepping up and taking on something that will help our client “get to done” more quickly or more efficiently. We are accountable for our work and the work of our teams – even when we are not the leader of the initiative.
Interested? Take a look at some of our team members.
