Role? Discipline? Knowledge? Definition? What do we need from a professional organisation?

I wrote a rant last time about my personal feelings toward organisations like the IIBA. I’ve got nothing against the IIBA itself, just a philosophical and ideological point of difference that is about making knowledge free to everyone. I wasn’t expecting, however, the number of tweets that came my way regarding these issue, so I thought I would actually ask the question, in this modern era of free knowledge and communications tools from Wikipedia and Twitter to Gmail and Ning,what do we want or even need from specialised, professional organisations?

1. Do we need standardisation?

I’ve heard a lot of organisations over the last decade proclaim that standardisation brings certainty and a level playing field to the market. It is suggested that it means an instantly recognisable criteria for recruitment and measurement of skills along with which comes measures of market values and salary. It also provides a means by which trainers can make a living. The principle of standardisation is a good one, but unfortunately when ‘owned’ by a professional organisation it becomes hard to adapt and change as the professional community begins to move in different directions and takes on board new techniques and tools from closely affiliated disciplines. One only has to look at the Scrum movement to see how some areas, like traditional project management, have become unable to incorporate ‘agility’ into its methods. It also means professional bodies may be turning away the very people who are able to transform their organisations. Take Information Architecture, for example. The president of the Information Architecture Institute during 2008, Eric Reiss,  has no formal qualifications in IA yet is regarded as one of the organisation’s most brilliant thinkers.

In the end, standardisation by a professional organisation only serves to reinforce normalisation, the status quo, within its organisation, ensures that its members can memorise and recall off the tops of their heads in an exam situation the principles that the organisation adheres to (e.g. the IIBA’s version of business analysis, or PRINCE2′s version of project management, but not your own thoughts on project management), and thereby stifles growth and innovation by the very thinkers it should be seeking to engage.

2. Do we need definition?

Again, we just need to look at project management to see what definition does to a profession — it fragments it. This is the time old problem with taxonomical classification that goes back to the time of Aristotle — definition means classifying what a thing is and what it is not. In relation to professional organisations, what follows is that people will either identify with that definition or will not. If they don’t identify with how you define what they do then they’ll look elsewhere or create their own group. We only have to look to project management organisations to see what definition has meant for their profession. Now we now have many different flavours of what projects manager do, from PMI and PMBOK, PRINCE2, to MSP and most recently P3O. The Business Analysis community is not immune either, with an American-made international body called the IIBA and an Australian one called the ABAA both with their own ideas as to what makes a business analyst and what does not. Which one is the One True Faith? Does it matter? I always look to Jesse James Garrett’s essay IA Recon when debating the need for definition by a professional organisation for the sake of its professional community:

“Definitions based upon the role tend to creep naturally toward broadness. Because the responsibilities that correspond to the role vary so greatly from organization to organization, the definition of the role (and thus the discipline) grows larger and larger.

“The opposing approach is to define the role based on the discipline. Whatever the field of information architecture is, an information architect is the person who specializes in it …these definitions tend to creep naturally toward narrowness …but when this definition (intended for the discipline) is applied to the role, it creates for some the fear of being ‘boxed in’, trapped in a role so narrowly defined that many of the elements essential to the success of any given architecture are outside the control or influence of the architect.”

For me, personally, this is how I feel about where Business Analysis is headed. That BA is being so  “narrowly defined that many of the elements essential to the success” of business analysis is starting to become outside my control or influence. And I hear this often from PMs who claim that it’s not a BAs role to do X or Y, and I’m starting to hear it from the ABAA who suggest that business architecture has little to do with being a business analyst.

3. Who owns the body of knowledge?

Once you create a publication you can sell it and make money. When it comes to creating a tome of knowledge, capturing it as a book and selling it turns knowledge into a commodity for which there are gatekeepers. Someone must decide what is of relevance and what is not. The logical decision is to reach back to a definition and a standardisation to choose. The result is a subjective call, not an objective one, as to whether an individual, or a set of empowered individuals consider to be worthy of documenting. This is the gatekeeper version of knowledge management, rather than assuming that collective knowledge resides within the community itself and changes and evolves over time.

Again, I’ll take a leaf from the IA Recon and note that “only by being generous with our knowledge can we reap all of its benefits. And only by creating a culture in which these principles are fully embraced can we foster the growth of our field, and ensure our continued success.” Peter Morville goes further to say that community is of equal value, that a profession’s role in order to evolve is to take the role and discipline to those who undertake similar activities to aid them with their work. I’d like to suggest that knowledge for profession is the intersection of all the areas of role, discipline, and community.

In essence, knowledge must be an emergent quality of all three areas, not prescribed by a professional organisation or described by a select, powerful few. This is what makes wikis such a powerful medium for sharing knowledge , either within organisations or by the public. To me, therefore, we need professional organisations to support the community and through the community influence role, discipline and knowledge.

This means we don’t need professional organisations to define the community and all aspects of the profession, but support the community to explore and influence the aspects of role, discipline and knowledge that are of relevance to them.

Hopefully, food for thought.

M

Advertisement