• by KM Officer
• 0 Comments

First Step to Fully Functional Technology Solution for KM

Developing technology solutions for your knowledge management initiative might look easy. Buying a ready to use software, integrating with the existing infrastructure, and make it go live. But it never that simple. Most of the cause of failure for any IT implementation is lack understanding of the business need and translate it into technical requirements. This is most likely the same with knowledge management. Without a comprehensive understanding of KM process, accountabilities, and governance, your KM technology system most likely become another leftover application.

Purpose

In order to seamlessly link your business needs with KM technology solution, you should develop a business requirement document or system design document. This document will translate your needs into detailed IT architecture, feature, technical requirement, workflow, persona, worksheet, and other elements needed by IT Developer or Implementor.

Method

We will work closely with both of your business team and IT team to construct business requirement for KM that can be easily implemented with proposed IT resources. With your business team, we will gather the need for technology as KM enabler, discussing the core element of technology solution (feature, processes, taxonomy, persona, workflow, and governance), while providing our insight on matching the need with proposed resource availability. As for your IT Team, we will assess the current infrastructure and the alternative technology solution. Using gathered data from business team and IT Team, we will formulate technical document as guidance for implementor team to develop your technology solution.

Deliverables

At the end of activities, you will get system design document. The document will contain a detailed explanation of:

• existing IT infrastructure condition;
• selected and it’s alternative for technology solution;
• business requirement analysis;
• user requirement analysis;
• decision analysis;
• business model;
• database model;
• workflow model;
• development approach;
• implementation roadmap;
• best practice for feature, processes, taxonomy, persona, workflow, worksheet, and governance.

 

Can’t find solutions to your unique cases or simply need more explanation?

Drop us an email and our experts will respond within days