Knowledge Graph Foundations
Graph structures help you trace stakeholder intents, data, and regulatory obligations. Use them to inform RAG retrieval and highlight dependency chains.
Turn your governed workflow into working prototypes. Build knowledge graphs, retrieval-augmented assistants, and interactive experiences using synthetic data—and validate them with AI-assisted usability testing.
3h concept study, 4h prototyping lab, 1h user test dry-run, optional 2h RAG experimentation.
Optional: LangChain, Flowise, Figma, Maze/Lookback for usability testing.
All mapped to real stakeholder needs.
python -m venv venv && source venv/bin/activate
.pip install llama-index langchain chromadb sentence-transformers streamlit neo4j
.networkx
for local graph visualisation.Gather 8–12 documents relevant to your workflow (SOPs, policy excerpts, FAQs, transcripts). Store them under data/sources/
. These feed the knowledge graph and RAG pipeline.
Graph structures help you trace stakeholder intents, data, and regulatory obligations. Use them to inform RAG retrieval and highlight dependency chains.
Retrieval-Augmented Generation keeps AI grounded in your domain knowledge. Evaluate RAG pipelines with precision/recall, hallucination checks, and latency measurement.
Use AI to generate probing questions, summarise sessions, and detect sentiment. Combine with real user walkthroughs for rapid iteration.
Pick the highest-value workflow slice from Module 2. Define start/end triggers, success metrics, and stakeholders. Record assumptions to test.
Ingest curated documents, split into chunks with metadata (persona, step, sensitivity). Generate embeddings and store them in Chroma or Neo4j.
Build at least two artefacts:
Instrument prototypes with logging for question types, response confidence, and user feedback.
Use AI to draft tasks and follow-up probes. Conduct an internal dry-run (teammate) and capture learnings. Prepare a highlight reel approach for real stakeholder sessions.
Assess each tool against security, compliance, integration, and TCO. Document alternatives and exit strategies should the vendor not pass due diligence.
Deliver working prototypes, evaluation plans, and vendor analysis ready for stakeholder review.
prototypes/assistant
, prototypes/dashboard
).artifacts/week3/rag_architecture.md
).artifacts/week3/usability_test.md
).artifacts/week3/vendor_assessment.xlsx
).#week3-demos
.python scripts/build_kg.py
(customise per your data). Validate in Neo4j Bloom or network graph visual.streamlit run prototypes/assistant/app.py
. Ensure persona context injection and guardrails (max tokens, filtered responses).artifacts/week3/rag_architecture.md
+ architecture SVG.artifacts/week3/usability_test.md
with dry-run notes.artifacts/week3/vendor_assessment.xlsx
(or CSV).artifacts/week3/reflection.md
)—what did users struggle with, what surprised you?Prototype Fidelity (35%): Functionality, alignment to workflow, logging/guardrails.
Knowledge Management (25%): Graph/index structure, citations, evaluation plan.
User Validation (25%): Test design, insights captured, iteration plan.
Vendor Due Diligence (15%): Security/compliance analysis, alternative strategies.
Merge Week 3 branch into main once peer-reviewed. Upload artefacts to portal and schedule your stakeholder demo rehearsal. Share a 3-minute loom or live demo during Friday’s cohort session.
Check chunking strategy (overlap, size), ensure metadata filters (persona, step) are used, and adjust embedding model. Validate queries by logging top retrieved nodes and reviewing their relevance.
Enable caching for embeddings, store retrieved contexts, and reduce model size (switch to gpt-4o-mini or Gemini 1.5 Flash for testing). Optimise Streamlit components for response batching.
Surface citations, confidence scores, and human oversight messaging. Include escalation options within the prototype. Capture feedback and plan explanation enhancements.
Instrument prototypes with event logging and metrics. Gather baseline KPI data and plan for telemetry integration. Identify stakeholders responsible for change management.
Preview Module 4 →