Knowledge Workflow Diagnostic — 8-Domain Audit and 90-Day Improvement Protocol

Usable diagnostic protocol. This page provides the actual audit structure an institution can apply before commissioning any engagement. It examines how knowledge is read, captured, tested, shared, and reused.

When to use it

Use when reports are repeatedly rewritten, sources cannot be traced, teams keep knowledge in personal files, theory or frameworks are used decoratively, presentations obscure evidence, or valuable learning disappears when staff leave.

Audit unit

Select one real knowledge workflow—such as research-to-policy, fieldwork-to-report, training-to-practice, or meeting-to-decision. Sample 5–10 recent artifacts and interview people who create, review, use, and archive them.

Eight-domain scorecard

Score each domain from 0 to 3: 0 absent; 1 informal/inconsistent; 2 defined and usually followed; 3 evidenced, reviewed, and reusable.

1. Purpose: Is the question, audience, and intended decision/output explicit?
2. Source traceability: Can claims be traced to lawful, identifiable evidence and locations?
3. Evidence–interpretation separation: Are quotations, paraphrases, analysis, and uncertainty distinguishable?
4. Argument architecture: Are problem, claim, counterclaim, evidence, and limitations aligned?
5. Theory/framework fit: Are concepts selected for explanatory fit and tested against alternatives?
6. Audience translation: Are presentations and briefs understandable without hiding evidentiary limits?
7. Practice sustainability: Are roles, review routines, feedback, recovery, and workload realistic?
8. Knowledge reuse: Are outputs searchable, versioned, accessible, and usable beyond their original author?

Evidence request

• Two strong and two weak examples of the chosen output
• Source files and citation trail for sampled claims
• Templates, review checklists, and approval steps
• Repository structure, naming/version rules, and access roles
• Examples of AI use, verification, and disclosure
• Interviews with creator, reviewer, user, and archive owner

Diagnostic interview

1. What question starts this workflow and who needs the answer?
2. Where do source materials enter, and how is permission recorded?
3. How can a reviewer distinguish evidence from interpretation?
4. Where do claims most often become unsupported?
5. Who challenges the framework or theory used?
6. What is lost when work moves from report to presentation?
7. What makes good practice difficult to sustain?
8. How would a new staff member find and reuse last year’s knowledge?
9. What may AI do, what may it not do, and how is use disclosed?

Risk classification

Red: any domain at 0, or traceability below 2. Amber: total 10–17 with informal controls. Green: total 18–24 with no domain below 2. A high total does not cancel a zero-risk control.

Minimum deliverables

• Current-state workflow map
• Evidence-backed scorecard with examples
• Top five failure modes and their causes
• 30-day quick fixes
• 90-day pilot with owner, evidence, checkpoint, and success measure
• Templates for traceable notes, claim–evidence review, theory fit, and AI disclosure

30-day self-start

1. Choose one workflow and owner.
2. Score five recent artifacts independently with two reviewers.
3. Resolve scoring disagreements using evidence.
4. Fix the single highest-risk break in traceability.
5. Retest on the next three outputs and document change.

Source note

This diagnostic is an original operational adaptation informed by Metode Belajar KBA: Sharing, Caring, and Producing Knowledge (Kamaruzzaman Bustamam-Ahmad, 2018). It uses the book as conceptual material without reproducing or selling it.

Interactive Workflow

Gunakan sistem berikut untuk menjalankan materi secara langsung. Data yang dikirim disimpan sebagai workflow record privat untuk tindak lanjut dan evaluasi.