Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| start [2026/06/22 04:51] – [Start Here] leonidas | start [2026/06/26 19:11] (current) – [Public-Sector AI Readiness] leonidas | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| OKF Expert turns scattered documents, policies, procedures, training materials, and institutional expertise into structured Knowledge Bundles that people can read, teams can maintain, and AI assistants can use responsibly. | OKF Expert turns scattered documents, policies, procedures, training materials, and institutional expertise into structured Knowledge Bundles that people can read, teams can maintain, and AI assistants can use responsibly. | ||
| - | [[contact: | + | | [[about: |
| ===== Start Here ===== | ===== Start Here ===== | ||
| Line 15: | Line 15: | ||
| | [[okf: | | [[okf: | ||
| | [[okf: | | [[okf: | ||
| - | + | | [[choose_your_starting_point|Choose Your Starting Point]] | [[https:// | |
| - | [[about:start|About OKF Expert]] | + | |
| ===== Why This Matters ===== | ===== Why This Matters ===== | ||
| Line 40: | Line 38: | ||
| [[bundles: | [[bundles: | ||
| - | * [[government: | + | ^ Related Readiness Topics ^ |
| - | * [[government: | + | | [[government: |
| - | * [[government: | + | | [[government: |
| - | * [[government: | + | | [[government: |
| - | * [[government: | + | | [[government: |
| - | * [[government: | + | | [[government: |
| - | * [[government: | + | | [[government: |
| + | | [[government: | ||
| ===== What Makes OKF Different ===== | ===== What Makes OKF Different ===== | ||
| Line 54: | Line 52: | ||
| It is a structured knowledge system where information can be: | It is a structured knowledge system where information can be: | ||
| - | * Organized into reusable Knowledge Bundles | + | |
| - | * Connected through related concepts | + | * Connected through related concepts |
| - | * Supported with citations and source references | + | * Supported with citations and source references |
| - | * Assigned ownership and review status | + | * Assigned ownership and review status |
| - | * Used for training, operations, compliance, procurement, | + | * Used for training, operations, compliance, procurement, |
| - | * Prepared for responsible AI assistant use | + | * Prepared for responsible AI assistant use |
| - | --- | + | [[legal: |
| + | |||
| + | ---- | ||
| <WRAP centeralign> | <WRAP centeralign> | ||
| **OKF Expert — Building the AI-ready wiki.** | **OKF Expert — Building the AI-ready wiki.** | ||
| + | </ | ||
| + | ====== Eleven Public-Sector Modernization Stories ====== | ||
| + | |||
| + | > //These illustrative composite stories are based on common public-sector operational challenges. They do not identify specific clients, agencies, employees, procurement actions, legal matters, or technology implementations.// | ||
| + | |||
| + | ===== 1. From Policy Overload to Procurement-Ready Modernization ===== | ||
| + | |||
| + | A public-facing agency program had committed employees but no reliable single source of truth. Policies lived in PDFs, shared drives, email threads, personal notes, and the memory of long-tenured staff. Employees answered similar questions differently, | ||
| + | |||
| + | The agency began with a focused Workflow Audit rather than a large technology purchase. The audit identified high-friction workflows, authoritative sources, knowledge gaps, governance risks, and a practical pilot opportunity. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 2. From Long Hold Times to Reliable Answers ===== | ||
| + | |||
| + | A constituent-service team spent too much time searching for answers while residents waited on hold. Staff relied on scattered policies, old desk guides, informal notes, and supervisor knowledge. The same question could receive different answers depending on who took the call. | ||
| + | |||
| + | The agency mapped its highest-volume questions, separated routine answers from matters requiring escalation, and organized approved guidance into a governed knowledge resource. The result was a foundation for faster, more consistent service without sacrificing accuracy. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 3. From Tribal Knowledge to Confident New Employees ===== | ||
| + | |||
| + | A California public agency was hiring new employees, but onboarding took too long. Important knowledge was scattered across outdated training materials, email chains, shared drives, and the memory of experienced staff. New employees often depended on whoever was available to answer questions. | ||
| + | |||
| + | The agency examined the onboarding journey, identified the most difficult tasks, and separated foundational knowledge, task-based guidance, and escalation rules. This created a clearer path for helping employees become confident and productive. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 4. From Audit Findings to Governed Operations ===== | ||
| + | |||
| + | An internal review found inconsistent procedures, outdated materials, unclear ownership, and difficulty demonstrating that staff were using current guidance. The agency had documents, policies, forms, and procedures—but no reliable system connecting them to actual work. | ||
| + | |||
| + | The agency used a Workflow Audit and Knowledge Governance Assessment to identify authoritative sources, content owners, review cycles, workflow gaps, and control gaps. The result was a practical path toward more defensible and consistent operations. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 5. From Approval Gridlock to a Governed Decision Path ===== | ||
| + | |||
| + | A statewide program was struggling with slow approvals. Requests moved between intake, program staff, fiscal teams, compliance reviewers, legal advisors, and executive approvers without a clear picture of who owned each decision or what information was required. | ||
| + | |||
| + | The agency mapped the actual approval process, clarified decision rights, identified unnecessary sequential reviews, and separated standard requests from true exceptions. The result was a more visible and governable decision path. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 6. From AI Pressure to a Responsible Public-Sector Pilot ===== | ||
| + | |||
| + | Agency leaders wanted to “do something with AI,” but staff were concerned about inaccurate answers, outdated documents, sensitive information, | ||
| + | |||
| + | The agency began with an AI-readiness workflow and knowledge assessment. It identified low-risk support opportunities, | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 7. From Policy Change Confusion to Consistent Frontline Implementation ===== | ||
| + | |||
| + | A policy update could be approved at headquarters, | ||
| + | |||
| + | The agency traced the complete path from policy approval to frontline action. It identified affected workflows, documents, roles, forms, exception pathways, and implementation responsibilities. The result was a more reliable way to turn policy decisions into consistent public service. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 8. From Retirement Risk to Preserved Institutional Knowledge ===== | ||
| + | |||
| + | Several of a division’s most experienced employees were approaching retirement. They held important knowledge about exceptions, historical decisions, unusual cases, partner relationships, | ||
| + | |||
| + | The agency identified its most vulnerable workflows, captured high-value expertise through structured interviews, connected that expertise to authoritative sources, and created a governed knowledge resource for future employees. The goal was not to replace human expertise, but to preserve what mattered most. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 9. From Fragmented Grant Guidance to Consistent Partner Delivery ===== | ||
| + | |||
| + | A grant program served local governments, | ||
| + | |||
| + | The agency mapped the partner journey from awareness through application, | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 10. From Field Inspection Variability to Consistent, Defensible Decisions ===== | ||
| + | |||
| + | A field-inspection program found that similar conditions were sometimes documented differently by different inspectors. Newer staff needed more help locating governing sources, collecting evidence, documenting findings, and knowing when to escalate an issue. | ||
| + | |||
| + | The agency mapped the full inspection workflow, clarified source authority, defined evidence standards, organized common scenarios, and created clearer escalation guidance. The result was stronger consistency without attempting to replace accountable field judgment. | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | ===== 11. From Public Records Backlog to Defensible, Searchable Responses ===== | ||
| + | |||
| + | A records-response team faced unclear intake, scattered records sources, inconsistent search practices, incomplete handoffs, and delayed legal or specialized review. The work depended too heavily on experienced staff who knew where information was likely to be found. | ||
| + | |||
| + | The agency mapped the records-request lifecycle, created a records-source and custodian map, clarified search documentation expectations, | ||
| + | |||
| + | [[case_studies: | ||
| + | |||
| + | --- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | **OKF Expert helps agencies make workflows, institutional knowledge, policies, and procedures usable, governable, citation-backed, | ||
| </ | </ | ||