Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
And And
And And
Optimize Ensure
Governance, Risk, Compliance User Needs are Executable
And And
And
Increase the
Automation Boundary
People struggle to create effective knowledge bases today, yet they are held accountable
for governance, risk management and compliance of their operations. Text is too
laborious for humans to read, it has no agreed structure and is not effective for
automated knowledge sharing. Process mapping tools are just too complex and are a big
turn-off for users and management alike. Fortunately though there is an integrated
governance, risk management and compliance plug-in application for Hyperknowledge.
The simple, accessible, but powerful language of Hyperknowledge appeals to busy
people. The ability to follow Hyperknowledge chains around their organization, the
interconnectivity that results, is compelling - it's less time consuming and it's therefore
cheaper. The busier people are, the more it appeals.
1.6 Increase the Automation Boundary Reduce Increase the Optimize the
Costs Automation Boundary Enterprise Knowledge Base
WHY HOW
The ideal knowledgebase will not only be understandable by humans, but also by
computer systems. This will enhance the ability to automate parts of the knowledgebase And
that will benefit from being automated, as no human-to-computer language translation
Find new
will be required. Although Hyperknowledge uses natural language, it is structured in Revenue Opportunities
such a way that the system components and relational tables required to implement a
part of the knowledgebase automatically fall out.
1.6.2 Find new Revenue Opportunities Optimize Find new Increase the
Revenues Revenue Opportunities Automation Boundary
WHY HOW
Don't be moribund by existing ways of working, think about products and services your
customers need that you could provide and be driven by this, not your current
circumstances.
Thinking outside the box is what you need to do here.
And
Don't waste
People's Time
And
Understand
Project Mandate
"When the only tool you have is a hammer, everything begins to resemble a nail" -
Abraham Maslow
Don't use conventional process tools, spreadsheets or text - they're unstructured, time
consuming, and the output holds little value to those who need the knowledge.
Know that not everything is critically important…
... Hyperknowledge can help you quickly and accurately understand, share and control
the key things that people and systems do.
Don't alienate your most important ally - the business - by using tools that force a
technical lingo to be understood by all or that are so ambiguous they are open to many
interpretations.
1.1.2 Don't waste People's Time First, do no Don't waste Prepare for
Harm People's Time User Discussions
WHY HOW
Don't waste people's time, you will lose credibility and when you need their help, they'll
remember you as a time-waster; bad news spreads fast.
Before you ask people questions, make sure you're asking the right person, you know
exactly WHAT to ask and WHY you're asking - and communicate this to them!
If you are to do no harm, you need to be aware at all times of what you are and are not
mandated to do. To best achieve this, you should be intimately familiar with the IT
Strategy in general.
1.2 Break down the Communication Gap Optimize the Break down the Speak in
Enterprise Knowledge Base Communication Gap Business Terms
WHY HOW
And
Avoid
Technical terms
If you use the wrong tools, technical and/or laborious tools, you'll turn off the very
people whose knowledge you need to capture. The process needs to be enjoyable, built
around an approach that is specifically designed to do this task. And specificaly designed
to tease out tacit knowledge in minutes not hours, or in hours not days.
1.3.1 Ask the WHY question Ensure you understand Ask the
WHY WHY question
WHY
Peter Drucker said "There is surely nothing quite so useless as doing with great
efficiency what should not be done at all." Be sure you know the purpose first.
To find the ultimate goals, keep asking WHY... If your chain of why questioning doesn't
support a business objective, question whether that requirement really is valid.
And
Successfully create
Instances
1.4.1 Understand the Detailed HOW Steps Ensure Understand the Ask the
User Needs are Executable Detailed HOW Steps HOW question
WHY HOW
Can you break down the requirement into smaller and simpler requirements? If not, is
your understanding of the requirement strong?
1.4.2 Ensure each noun responds to the WHAT Ensure Ensure each noun responds to
User Needs are Executable the
question WHY WHAT question
If a noun phrase doesn't make sense when preceeded with "What", the requirement is
poorly defined. And you will have trouble converting this into an entity, class and/or
database table at later stages if you don't fix this early.
And
And
And
Implement
Component
The best way to define components is to understand WHY a component is needed. The
structure inherent within hyperknowledge means that components are automatically
identified. The integrated knowledgebase means that you are automatically alerted
about hyperknowledge maps that you could re-use - these maps could be from inside or
outside your organization.
1.5.1 Create a component for each Individual Identify Create a component for each
Reusable Knowledge Individual Concept
Concept WHY
Independent concepts are those concepts that have been reused and are therefore
natural candidates to be created as stand-alone components.
1.5.2 Define a Method for each Verb Identify Define a Method for each
Reusable Knowledge Verb
WHY
The verbs from your maps become class or component methods.