3. A Key Component
of Our Project Methodology
Identify
Opportunity
Analyze
Knowledge
Architecture
Establish
Plan
Monitor
and Modify
Closeout
and Evaluate
Planning ImplementationDefinition
4. During This 2 Day Session We
Develop a First Cut Project Approach
Ø We characterize your problem or opportunity in
terms of Knowledge Management
Ø We verify expected gains from using technology
in terms of knowledge architecture requirements
Ø We compare the target application’s logic to
Livelink functionality to determine level of effort
to build your application
5. What Makes It Different?
Ø Application logic described in terms of
customers, process, and MIS
Ø Business case integrated from the start
Ø Clear definition on architectural requirements
provides best foundation for evaluating
technology features
Ø Integrates best practices from many disciplines
› BPR, TQM, Policy Analysis
› AD, DOCMAN, WF
› Project Management
6. Staff Growth
Lags Revenue
Ø Management of knowledge assets
› Document management, workflow, policies,
procedures, practices, folders or cases
› Examples: BPR, Re-Use, TERM
Ø Involves knowledge workers
Ø Underlying “data” is difficult to model
Faster Work,
More Money
Web Means
More People
The Right Problem or
Opportunity
7. Not Good Candidates
Although these are important candidates for
business systems, they do not require a
detailed understanding of the knowledge
architecture
Ø Data entry or production problem
Ø Commerce opportunity
Ø Data analysis (OLAP, warehousing)
8. Refine and Clarify the
Problem
Ø Identify the ultimate customers
› Whose needs are we meeting? What supplier,
consumer or source of support or funds
benefits from solving this problem?
Ø Validate the value proposition
› What implicit promise are we making to
deliver a particular combination of values?
Ø State the project and develop objectives
› The first key project management deliverables
9. Pinpoint the Underlying
Knowledge Architecture
Ø Highlight points of high leverage
› Creation of information or new idea
› Information-intensive decision points
Ø Common underlying elements
› Business processes, documents, collections and
“hunting and gathering expeditions” of many kinds
10. Existing Infrastructure
and Integration
Requirements
Ø Work process maps
Ø Collaborative project
collections
Ø Saved searches
Ø Document libraries
Ø Customized personal
Change Agents™
Ø Integration with
calendar, email
Ø Integration with
enterprise systems
11. Customer
View
Screens, flow, file upload,
browsing, searches, agents,
downloads, reports, results
Business process
flow and rules
User administration,
interfaces, backups, upgrades,
crawls, acquisition, storage
Process
View
MIS View
