Knowledge Management

Knowledge (Theories, Ideas & Concepts)

Through Professional/Personal Study Gained Through Experience

Knowledge Strategies – Knowledge Sharing & Collaboration, Codification/Taxonomies
Content/Documentation Management Systems, Meta-Data, Case Studies, Rapid Evidence Reviews, Knowledge Banks/Wikis, Communities of Practice, Peer Assist, Knowledge Café, Knowledge Marketplace, After Action Reviews, Retrospective Reviews, Knowledge Exchange.

From the Level 0 Fundamental Strategic View right down to Level 7 Building on Small Successes (InnoCentive Award Paper).

Together with Responsibilities/Accountabilities

Knowledge is only useful when it is shared. Collaboration helps drive engagement and ultimately innovation, yet so many organisations put up barriers to restrict this. The ability to synthesis meaning, add value, refresh and recraft it to add current relevance and context, and then using and applying that knowledge in the more effective and efficient manner is what makes good businesses great. Having a culture of generous knowledge sharing, supported by an example lead leadership/change advocates together with readily available tools and techniques is what can make all the difference.
Subject matter expert and worldwide award winning contributor on the subject of capturing institutional memory and knowledge. As employees retire or leave an organisation, it is important to devise effective mechanisms to make sure that knowledge is not lost. A report was written that provided suggestions and outlined the best practices and strategies for capturing, storing and annotating different types of institutional knowledge, and approaches for the capture of programme, operational and maintenance information.

Service-Orientated architecture (SOA) in terms of delivering capability as autonomous, loosely-coupled, discoverable service elements encapsulating the many re-useable sub-systems, that are normalised, granular, stateless and ideally have element of promoting longevity. Solutions and implementation approaches are developed to be technology agnostic (web services, messaging, RESTful) however aligned to agreed protocols that enable maximum interoperability. Deployed CORTISONE Architect responsible for the delivery of all aspects of the mobile element of system in disconnected, low latency and restricted bandwidth environments.

Together With lessons Learnt

Data is may be King, but the Kingmaker are those that can determine what data to capture and how to capture it, then turn it into information that has value to a business. Without clean or appropriate (correct, authentic, true, with integrity) data in the first place you will be starting from the wrong point. Without appropriate methods of storage, processing, analytics and conclusion generation, the data is either useless or even counter productive. Whatever data you have it must be wrapped up carefully with the right people training, processes, systems and infrastructure.
The security concerns regarding data protection starting from having the right talented people to handle and interpret the data, through the issues regarding access, connectivity, confidentiality and privacy, then the next level of issues relating to sharing, collaboration, ownership and derived benefits and values, and then finally to the information end-points of shelving (clearly identifying data of no current value), evolving (take data to the next step/phase), archiving, destruction, unauthorised release and effect on company reputation, and the process of then adding to the corporate lessons learnt compendium.

Data velocity is a critical element of the single information environment. What data needs to be real-time and be time synchronised, and what data can be classified as non-critical and transmitted asynchronously is imperative. Velocity will affect issues such as data availability (to applications, systems and people), setting of business rules (setting communication priority is bandwidth limited environments, establishing workflows and over-rides) and cluster/multiple dataset management. Establishing a scalable, adaptable and evergreen modular enterprise architecture will be critical to meet the demands of not just today, but of those issues that you will be faced with in the future.

Together with Any ‘So What’ Statements of Insights

Being able to develop a Health Usage and Monitoring System (HUMS) within a complex communications programme that not only identified any anomalies from agreed baselines, but was also able to compare across baselines for both forward and backward compatibilities issues. A detailed technical understanding of systems allowed the usage of both open and closed (maintenance) ports in order to develop the relevant outcomes. Sometimes it takes out of the box thinking to create necessary solutions.
Creating a business case for improved Collaboration and Innovation with an assigned pan-departmental team meant coming up with new methods of team engagement and critical thinking in order to deliver to very short timeframes with an ambitious scope. The assignment was so successful it won an annual engineering award, and it helped develop new skills for all the team members that could then be utilised on other future business related activities.

Developing the Deployed CORTISONE Medical Information Services Application Architecture in terms of the virtual and physical (hardware, virtual, networks) environments, technology components and relationships to information systems, links to legacy systems, adherence to industrial standards and corporate best practices and procedures/ processes, and aligned to the enterprise infrastructure, data handling models and approved application patterns. Knowledge management needs to be constructed holistically both across the organisation and in concert with external interfaces and standards.