CHEFS = Common HostEd Form Service

How do we create a connected community that can learn and improve together?


(blue star) CHEFS Team Weeknotes 7

Explore the CHEFS roadmap progress, Proof of Concept Tenant Manager app, BC Services Card integration opportunities, and meet Bhuvanesh - the problem-solver making CHEFS more accessible for everyone (2- min read)

Our roadmap guides our purpose, shaping our team's goals and vision for a clear and united future.

New to you

The Proof of Concept (POC) for the Tenant Manager Web App was successfully presented at our last Sprint Review by Robinson, Chris MOTI:EX, Sethuraman, Shankar JEDI:EX, and Pattanashetti, Bhuvanesh CITZ:EX. This POC enables seamless role-based access control (RBAC) across ministries and is key to building a scalable, user-friendly system.

Delivered ahead of schedule, the POC demonstrates how Scrum@Scale drives team efficiency and time savings.

The team is entering the final sprint to refine:

Let’s Collaborate! 

Many people are eager to use the BC Services Card as a credential in their forms, but if that requirement has held you back from using CHEFS, we want to hear from you!

We're looking for partners to collaborate on solutions together. Connect with Duncan Strong, Product Owner, on MS Teams to discuss how we can move forward.

Want to Use the BC Services Card for Your Forms? Let’s Collaborate! Are you holding back a great CHEFS project because it requires BC Services Card integration? You're not alone! Many teams are looking for this functionality.

Let’s connect! Contact Duncan Strong on MS Teams to explore how we can integrate your project with CHEFS and make your vision a reality.

What’s next

We will be able to share what the Value team is doing with the results from the Architecture Forum usability testing sessions in the next quarter.

Team Spotlight

Meet Bhuvan Pattanashetti, the problem-solver behind CHEFS! As a Client Success Analyst and Technical Architect, Bhuvan transforms challenges into user-friendly solutions that enhance the accessibility of CHEFS services. His work ensures clients can easily create, manage, and optimize forms, ultimately improving service delivery across British Columbia. 

Thanks for reading!

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

 Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design


(blue star) CHEFS Team Weeknotes 6

Your feedback is driving important changes—enhanced CHEFS security and new collaboration opportunities across ministries. Learn more about the updates and meet Minshen Wang, who’s turning your feedback into action! (2-min read)

Our roadmap guides our purpose, shaping our team's goals and vision for a clear and united future.

Using External Content in CHEFS? Read This!

We're enhancing CHEFS security by adding a Content Security Policy (CSP) header. This means external media like scripts or images won't load automatically, improving your data security.

If this affects your work or you have questions, join the conversation in the MS Teams Channel. We're here to help!


New to you

Usability testing results: The Architecture Forum conducted usability testing with 250 online participants to identify users' pain points. Twenty percent of the feedback received from our audience was positive. Our UX Designer reviewed all nine breakout room videos to extract key insights.

Key findings from the testing include

  1. Expected vs Actual Time with Productivity Loss Graph

    Expected vs Actual.png
  2. Frequency vs Impact Grid

    Frequency vs Impact Grid.png

Update on the Proof of Concept from the workshop held on Tuesday, March 4.

Tenant Manager's Potential:

Impact: (Former CHEFS teammate) Lucas O'Neil - CITZ:EX 

Collaboration Between Ministries:

Excitement for Workflow in Enterprise CHEFS:

What’s next

In Weeknotes #7, we will share what the Value team plans on doing with the results from the Architecture Forum usability testing sessions.

Team Spotlight

Meet Minshen Wang, a Service Designer on the CHEFS team who’s passionate about turning user insights into meaningful improvements. Discover how unexpected paths and gardening fuel her creativity and drive!

Your Voice Matters!

Please share your thoughts in our quick two-minute poll—your insights directly shape the future of Weeknotes. We’re listening! Make sure to respond by Wednesday, April 12.

Thanks for reading!

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design


(blue star) CHEFS Team Weeknotes 5 

Discover how your feedback is shaping our future projects and meet one of our team members driving these exciting initiatives!

Our roadmap guides our purpose, shaping our team's goals and vision for a clear and united future.

New to You

What’s Next


Weeknotes #7: Our Next Steps for Usability Testing Results

Are you curious about what's next for the Architecture Forum's usability testing results? In Weeknotes #7, we'll reveal our plans for turning your insights into action.

Join us for the March 6 CHEFS Workshop on Road Use Permitting

This interactive session allows team members to explore and provide feedback on how CHEFS (Common Hosted Forms Service) can support the Road Use Permitting project. We’ll cover:

Please share your comments and thoughts on the work below and how we can enhance the Weeknotes experience. We are listening.

Thanks for reading!

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design


(blue star) CHEFS Team Weeknotes 4 

Creating a connected community that can learn and improve together  

Please share your comments and thoughts on the work below and how we can enhance the Weeknotes experience. We are listening. 

Our roadmap guides our purpose, shaping our team's goals and vision for a clear and united future.

New to the User

Future Focus

Thank you for Collaborating at the Architecture Forum

We were thrilled to welcome 852 attendees to the morning and afternoon sessions. The CHEFS team shared our new roadmap and connected with the audience to discuss how it aligns with their use cases.

Morning Session - The New CHEFS Roadmap: How does it fit your use case?

·       Video - 51 mins

·       Summarized transcripts - 5 mins

Afternoon Session - Delivering scalable, sustainable and configurable solutions

·       Afternoon – 31 mins

·       Summarized transcripts – 6 mins

We had 59 people express interest in connecting with our product owners to discuss the opportunity to partner with them on proof of concepts and current products. You will be hearing from us shortly.

If you missed the session and would like to discuss proof of concepts or current products with CHEFS for your team, please write your name and what you want to talk about in the chat, and we will arrange a call.

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design


(blue star) CHEFS Team Weeknotes 3 

Creating a connected community that can learn and improve together  

Please share your comments and thoughts on the work below and how we can enhance the Weeknotes experience. We are listening. 

Has been fixed  

New to the user  

Has been improved 

Future focus 

Thank you for Collaborating 

Deployment of HLTH’s ESS LiveStream Service:
Product Owner Daniel Pizarro and his team—Walter Moar, Jason Chung, and Jason Sherman—successfully deployed HLTH’s ESS LiveStream Service. Working closely with HLTH ministry members, CGI, and the Polysomnography team, the project was delivered on time through exceptional collaboration. 

Service Improvements:
The team incorporated feedback from HLTH’s Polysomnography team, significantly enhancing the CHEFS service and user experience. 

Client Appreciation:
The client greatly valued the dedication, communication, and teamwork, contributing to the project's success. 

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design


(blue star) CHEFS Team Weeknotes 2 

Creating a connected community that can learn and improve together  

Has been fixed  

New to the user  

Has been improved 

Future focus 

Thank you for Collaborating 

Thanks to @Russell Vinegar's suggestions, we have made updates to enhance our Weeknotes. 

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design


(blue star) CHEFS Team Weeknotes 1

 

  1. Has Been Fixed (Broke No More): Broken things that we fixed  

 

  1. New To The User (Brand New, Secondhand): These are the most exciting because they are new

  1. Has Been Improved(Continuous Improvement Bucket): A conversation about anything and everything that makes the product faster and better 

  1. Future Focus (Boldly Go Where No Common Component Has Gone Before) Feedback on things we have started building  

Check out Weeknotes from other teams on MS Teams: Digital Delivery Network (Open) | Weeknotes | Microsoft Teams

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

  1. Has been fixed (broke no more): Broken things that we fixed

    • They can be linked to a kudos or a thank you for reporting

  2. New to the user (brand new, second hand): they are the most exciting because they are new

  3. Has been improved (Continuous improvement bucket): A conversation about anything and everything that makes the product faster and better

    • This part is for demoing things that are deployed and improved

  4. Future focus (boldly go where no common component has gone before) Feedback on things we have started building

    • Observe and learn before we help

    • i.e. FIDER ideas that are bubbling up

    • Outcomes of user research or service design