11.12.2012 Views

Knowledge Management Tools and Techniques ... - Index of - Free

Knowledge Management Tools and Techniques ... - Index of - Free

Knowledge Management Tools and Techniques ... - Index of - Free

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 3.1<br />

May-Sept<br />

2001<br />

Oct-Dec<br />

2001<br />

January<br />

2002<br />

Looking for<br />

Elaboration<br />

an answer:<br />

<strong>of</strong> user<br />

Assessment<br />

requirements<br />

<strong>of</strong> existing<br />

<strong>and</strong><br />

processes<br />

Assessing<br />

vendors with Better<br />

new ideas underst<strong>and</strong>ing<br />

strawman<br />

Result: We <strong>of</strong> what we<br />

knew what wanted,<br />

we did not assessed three<br />

want to do vendors,<br />

selected one<br />

Solution time line<br />

February<br />

2002<br />

Plan, Design, Execute . . . Reap? 85<br />

Business Case Plan & Design Implement Maintenance<br />

Design <strong>and</strong><br />

develop<br />

wireframes<br />

<strong>and</strong> conduct<br />

content<br />

audit<br />

The executive team then appointed an executive champion, who in turn picked a<br />

team to design a solution. The core team initially consisted <strong>of</strong> an executive sponsor, a<br />

project manager, <strong>and</strong> the IT director. Their challenge was time. The decision was made<br />

in late October 2001, <strong>and</strong> the site had to be delivered in early April 2002 (see Figure<br />

3.1).<br />

Designing <strong>and</strong> Deploying a Solution<br />

Vendor Assessment<br />

March<br />

2002<br />

Construction<br />

<strong>and</strong> content<br />

input<br />

April<br />

2002<br />

April 15,<br />

Launch<br />

May<br />

2002<br />

Phase 2<br />

Support<br />

Identifying<br />

requirements for<br />

Phase 2 <strong>and</strong><br />

focusing on clean<br />

content<br />

The first step was to determine what the solution should look like. A critical<br />

requirements session was conducted with the executive champion, project manager,<br />

<strong>and</strong> technology director, as well as marketing <strong>and</strong> product group representatives. An<br />

external consultant in application <strong>and</strong> Web site deployment facilitated the session. The<br />

group identified two key elements: an initial set <strong>of</strong> functionality for the site <strong>and</strong> the<br />

realization that center staff would need external assistance in deploying the system.<br />

With the requirements in h<strong>and</strong>, APQC again approached vendors. APQC’s position<br />

to these vendors was, “We don’t know what technology to use or what solution we<br />

should have. Here are the requirements; you propose a solution.” Three solutions were<br />

proposed:<br />

1. A custom solution based on s<strong>of</strong>tware developed for other customers<br />

2. Content management s<strong>of</strong>tware, a search engine, <strong>and</strong> a custom portal for Web<br />

delivery<br />

3. Content management s<strong>of</strong>tware, a search engine, <strong>and</strong> a portal application for<br />

content delivery<br />

To support the decision-making process, the vendor suggesting a custom solution<br />

created a prototype <strong>of</strong> the site so that the team could visualize what the application<br />

might look like. This was an eye-opening experience for the team. With no business<br />

analyst to guide the effort, the vendor created a prototype that was visually dismal.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!