What do I do?
I get asked this question all the time; for years I have been asked this question. At the beginning of my career I could say I was an accounting student, or an accountant, and people understood this. However, the more education and experience I got, the more difficult it became to say precisely what I did.
When I became self-employed, I used to say that I did knowledge management consulting, and I did, but people (mostly) didn’t understand what that meant, so I tried to explain. I could give examples of projects that I had done and the impact that it had had, and they sort of understood, but not really. They smiled and nodded and we moved onto another subject.
I have been self-employed for 16 years, my consulting practice has changed and evolved, the “how” of what I do has changed. I now incorporate artistic methods/thinking into what I do (the truth is, they was there all along, I just didn’t have a name for it, much like the agile, and design thinking practices I incorporated in to my methodology, without having a name for them either). But, honestly, no one cares about the “how”, they care about the results.
What are my results?
I stop you from failing with your big, unwieldy projects and programs. Your big, cross-functional, cross-organisational initiatives, that don’t neatly fit into a box. Those initiatives that have lots of stakeholders, lots of moving parts, lots of conflicting objectives. They have technology, they have processes, they have people.
Examples: One organisation recognised an ROI of 165%, while another was prevented from throwing out a million dollar (Cdn) IT investment and starting over.
In the current environment, these projects are called digital transformation, and up to 95% of them fail. When I first started, they were mostly called knowledge management, and somewhere around 50% of them failed. Certainly, one of the first KM projects I did had failed twice previously under different project managers, and I came along and did it using an iterative, collaborative approach (what might be called agile and design thinking now). Not only did I have a successful pilot with 100 people, but eventually had almost 7000 people using the platform, which increased to 10,000 on the momentum of what I had started even after I left the organisation.
Since going out on my own, I have helped other organisations do this—well, at least the ones that trusted me. There were some that were uncomfortable with my cross-functional, collaborative, iterative approach, and so shelved my work, which is their prerogative.
My success is built on experience, trial and error, persistence, collaboration, communication, curiosity, critical thinking, leadership, and a willingness to admit that I don’t know the answer but I’ll find out. There is no course that teaches these things, only experience.
Courses and certifications teach theory, they teach best practices. But as anyone who knows about best practices will tell you, best practices are dependant on the organisation, the situation, the culture, the people, the technology, and the processes. Best practices from one situation/organisation will not necessarily give the same results somewhere else.
Experience takes best practices and asks the question, how do we take that and make it work here, in this environment, with this technology, with these people?
What do I do?
I ask the questions, and I successfully plan and execute big, unwieldy projects.