KCS Pilot Hub
Find what we know. Improve what’s missing. Make the next ticket easier.
Pilot goals
We're testing a new way of working with real tickets, then using what we learn to prepare the next wave
Form a KCS Council
Bring volunteers together to steer the KCS process and make improvements based on frontline experience
Agree on our Solve Loop
Make search, reuse, improvement and capture a natural part of everyday ticket work. Find where our current practices need to evolve to accommodate how we solve
Co-create our content standard
Agree on what makes an article findable and usable. Refine the standard as we test it against real work
Coach the coaches
Find and empower our agents of change to lead future waves of KCS at York
Prepare for wider adoption
Build useful knowledge, identify where we need support, training, and coaching. Understand what it takes to make KCS work at York and then help others down the path we've set
The agent Solve Loop
Every branch, from searching knowledge to confirming the outcome. Click a step to open detailed, practical guidance for Halo agents.
KCS Council
The people doing the work help decide how the work gets done
York's KCS Council will gather volunteers from across our campus, bringing different perspectives to help shape our standards, tools and workflow
Shape the Solve Loop
Find what works in real tickets. Fix steps that slow us down
Own the content standard
Agree on clear guidance on how to make a good article; test it, improve it with real examples
Support the coaches
Help set up a coaching approach that our pilots and future teams can use
Remove friction
Look at feedback, common gaps and repeated problems. Make changes that help everyone.
Coaching
Training explains what KCS is... Coaching sets the practice
KCS coaches are peers who help others understand, practice and refine their knowledge habits. They help raise our collective standard and grow with confidence
Co-work through real tickets
Help colleagues search early, reuse answers, and capture what they learn
Build judgement & practice
Review examples together. Talk through article structure, accuracy and provide guidance on each step of the process
Share feedback
Share patterns, obstacles and opportunities to make the process more effective and easier for our frontline
Make answers usable
Use this quick check as you work. The Content Standard holds the detailed field guidance and examples
Check out our content standard >>-
A findable title
Use recognizable issue language and the terms someone would search for
-
A clear description
Capture the issue and environment in which it happens. Include the cause when known and useful
-
Verified resolution steps
Write steps another agent or the intended requester can follow. Make the expected result clear
-
Deliberate metadata and access
Use the relevant Halo fields, tags and access settings. Keep passwords, secrets, personal information and material unsuitable for the article’s audience out of the content
-
A connection to the work
Link the relevant article to the ticket and preserve useful context for the next person
Pilot Support
Pilot training
Virtual training sessions covering KCS 101, our solve loop and creating knowledge according to our content standards will be available to all pilot participants
1-on-1 coaching
All pilot participants can book a virtual coaching session to work through real tickets with Luke
Book a session >>
If the calendar does not load, open Microsoft Bookings >>
Weekly standup
Our weekly open forum will provide pilot participants a chance to share their feedback, advice, tips & tricks and more
Join the open forum >>Hotline
Our dedicated Team's chat will give all pilots a place to ask quick questions, request urgent help report problems
Send us a message >>FAQs
Who can create and edit articles?
All Halo agents can search, reuse, share and link the knowledge available to them. Onboarded pilot participants from SSB, OUR, CTS and CS can also create and update articles.
What if an article is wrong?
Fix it if you have the permissions and verified information. Otherwise, raise it with your pilot lead or in the Knowledge Worker @ York conversation. Don't create a duplicate to work around a problem.
What makes a good KCS article?
Someone else can find it, understand when it applies, and use it to solve the issue. Capture what is known, follow the content standard, and improve the article as it gets reused.
Will coaches approve every article?
No. Coaches help people develop KCS skills and good judgement through real work. Authoring permissions and the content standard still apply.
Are we trying to produce lots of articles?
No. We care whether knowledge helps people resolve issues, reduces repeat investigation, and is easy to find and reuse. Quality and usefulness matter more than article counts.
What happens after the pilot?
We'll use what we've learned to improve onboarding, coaching, content and workflow before expanding to more teams. The rollout roadmap aims for wider adoption in spring 2027 and self-service in summer 2027.
Knowledge Workers @ York
Ask questions, share examples, point out what isn't working, and help improve how we use knowledge in Halo
