In the knowledge era, we still have no real way to encode and share knowledge, the DNA of a modern organization.
The WHY Code is a fundamental way to unblock organizational knowledge flow, empowering people to discover and share exactly WHAT needs to be done, HOW and most importantly WHY.
Challenge: The WHAT-HOW-WHY chains inevitably cross functional boundaries and cooperation between functions is needed.
Suggestion 1: Find a ‘champion’ in the organization who has the reputation and respect to inspire such a cross-functional initiative.
Suggestion 2: Start with a small, quick-wins cross-functional project that can represent a compelling example for others to follow.
Challenge: Innovations such as this are known to follow Everett Rogers Diffusion of Innovations model – adopted by innovators first and only accepted by others after these innovators have proven the benefits.
Suggestion: Find a ‘champion’ who has a reputation for successful innovation.
Challenge: Such cross-functional initiatives, with a technology underpinning, are often delegated to the IT function. But the IT function is often locked into old fashioned input-output process thinking. And their architecture tools are often too technical and do not talk a business language.
Suggestion: Find a senior business ‘champion’ rather than IT sponsor (unless the latter is very business-oriented).
I've been asked to explain the genesis of this idea.
When I was a CIO, I became disatisified with the approaches for understanding the key business processes and drivers. The divide between business language and IT language was a real problem. I felt that there must be a better way than the techie tools that were mostly (and still are mostly used). It started me thinking. Then as a partner of a big consultancy, I encountered the same problem in a different form. I needed to staff a project in one part of the world, while the person with the best knowledge was in another part of the world. How to transfer the knowledge? Text was pretty useless but was (and still is) mostly used.
So I felt there was an opportuntity to create a common, standard way to define knowledge, regardless of domain. Yes, different tools and different encoding rules may be needed in the detail of some specialisms, BUT it's my view that a fundamental code underlies all knowledge, regardless of domain and that surfacing this code can dramatically breakdown knowledge silos and faciliate much better knowledge sharing. If one can understand and explain a process (natural or human or organizational) in the WHY codes's WHAT, HOW, WHY structure, then one truly understands it. And others can understand and internalize the explanation quicker, and they can replicate it more accurately.
For those interested, there are now good success stories on using the WHY Code in a number of different industries including Oil & Gas, Banking and Insurance.
Our work with the WHY Code is very much focused on organizational knowledge.
But we believe the approach to be applicable in other knowledge domains, and some experimentation is currently under way. For example, a project to create the WHY Code of the human body is just beginning, as is another project in the Physics domain.
Yes, unfettering information flow within an organization is important. The "WHY" question seems very prominent. We say organizational clarity. Everyone knows what the organization's goals are.
What's also important is moving the decision making ability to the people with the information. Instead of moving information up to the people with authority.
Trevor Davies
January 9, 2012 at 6:58am"Because the modern organization is composed of specialists, each with his or her own narrow area of expertise, its mission must be crystal clear. The organization must be single-minded, or its members will become confused. They will follow their own specialist rather than apply it to the common task. They will each define “results” in terms of their own specialty and impose its values on the organization. Only a focused and common mission will hold the organization together and enable it to produce."
"The first questions in increasing productivity – in working smarter - have to be: WHAT is the task? WHAT do we try to accomplish? WHY do it at all?" Classic Drucker, From the pages of Harvard Business Review