Objectives, Key Results, Strategies & Tactics

NOTE: No priority is implied or determined at this time - all objectives are considered equally impactful.

Objective 1: Partners support the CHEFS' roadmap and understand how it aligns with theirs.

Team Objective:

DoNE Once https://bcdevex.atlassian.net/browse/DO-458

1. In progress Key Result: Establish a bi-weekly proactive communication process for change management processes, handling of Support Requests, and planning activities. (To do, doing, and done - at a higher level specific to the product roadmap)

   1. in progress Strategy: Regular communications of product roadmap updates to Partner Teams & CHEFS users via a deck presented/distributed at key meetings throughout the quarter.

   2. in progress Strategy: Executive updates (1 per quarter per executive audience) conducted by CPO & PO.

2. in progress Key Result: Architectural Forum participation rates increase by 20% in terms of people count attending. → https://bcdevex.atlassian.net/wiki/x/AwBYV

   1. IN progress Strategy: after establishing demand, we find out why, to present a message that will matter to partners, and why we are doing it now.

   2. not started Strategy: Grant early access to new CHEFS features to “CHEFS Insiders”.

   3. not strategy Strategy: Conduct award ceremony during Forum to recognize a leading partner for their contributions & impact on CHEFS users throughout the quarter. (CHEFS User Impact Awards - “CHUI Awards”).

3. not started Key Result: Receive monthly feedback from clients that they feel improvements in communications (before and after)

   1. Strategy: Weeknotes of things that others would care about.

      1. Audience 1: Partner Teams and CHEFS users

         1. (Tactic) Deliverable: (example) We have an updated instruction page for the new CHEFS Role that was added (Submission Reviewer, Read-only reviewer role “Submission Approver”, Write permission reviewer role “Submission Reviewer“)

      2. Audience 2: Executive levels that endorse the use of CHEFS for their Ministries

         1. (Tactic) Deliverable: Executive Level messaging, clarifying alignment to the technology strategies of each Ministry

   2. Strategy: Blogging about form design principles

      1. links to how to documents for users of CHEFS (for designers)

      2. links to how this relates to our roadmap (for executive)

Objective 2: Partners support our technology architecture direction

Team Objective: https://bcdevex.atlassian.net/browse/DO-459

1. in progress Key Result: Ratify a committed roadmap & project plan (including sequencing & dependencies) for critical CHEFS technology architecture components.

   1. in progress Strategy (An optional method we are experimenting with to see if it affects the key result): Decoupling of Components for improving resilience of CHEFS system integrations

      1. in progress Tactic (Jira Tickets for the team to do in a sprint): POC Tenant strategy (decoupling user management from CHEFS)

      2. in progress Tactic: POC on the message queue / event streaming to replace the hard coding webhook integration chefs is currently doing

2. not started Key Result: Demonstrate value from POCs as measured by documented lessons learned:

   1. Strategy: can manage users and roles outside of CHEFS,

   2. Strategy: CHEFS would trust a token that is not a CHEFS aud variable in the JWT

   3. Strategy: can distribute data on a tenant basis through the message queue, only the tenant can read the data. (tenant = the registered app, which displays to the users)

Objective 3: Simplify the user journey for low-complexity form design & management

Team Objective: https://bcdevex.atlassian.net/browse/DO-460

1. not started Key Result: Effectively reduce the level of technical knowledge and expertise required by CHEFS users to achieve their project/product goals.

   1. Strategy: Remove the required sequence of steps that are not actually necessary for someone to rapidly prototype a new form.

      1. Tactic: switch to a different form builder that skips the settings step and let you edit the label of the component in context. (Other than changing the label, and sometimes not even that, the default form component settings are often all that is needed)

      2. Tactic: Adding default values to all required fields

   2. Strategy: Fix the visibility of system status, user control and freedom to avoid mistaken actions, flexibility and efficiency of use

      1. Tactic: Heuristic evaluation to inform the redesign

2. not started Key Result: Collect new user & low-complexity form maintainer effort & satisfaction metrics.

   1. Strategy: Controlled experiment - new users are asked to translate a specific PDF file into a CHEFS form:

      1. with FormsGPT

      2. without FormsGPT

      3. with CHEFS HelpBot (ie. Retrieval Augmented Generation)

      4. without CHEFS HelpBot

   2. Strategy: Ask power users to provide feedback on efficacy of new features.

Objective 4: Enhanced high-complexity forms support

Team Objective: https://bcdevex.atlassian.net/browse/DO-461

1. Key Result: Increased adoption and use of CHEFS API & Custom Components as measured by the Form Profile declaration and product telemetry.

   1. In progress Strategy: Add new custom components (eg. mapping, look for more in FIDER)

   2. In progress Strategy: Improved documentation about the API usage

      1. completed Tactic: add more documentation about the API Integration (e.g. salesforce)

      2. not started Tactic: update the API spec, make a postman collection,

      3. not started Tactic: make the API Key creation step great again

2. in progress Key Result: Increased take-up of CHEFS for data and reporting use-cases as measured by the Form Profile declaration and product telemetry.

   1. completed Strategy: Enhanced API capabilities

      1. Tactic: connecting to external APIs securely

   2. Strategy: add logging to see who is using the API

   3. Strategy: easier way to achieve a basic analytics function

   4. Strategy: shutdown/sunset the manual excel export with the 4 templates, in place of the excel power query integration.

3. Key Result: Identify the value of Dev and Test form classes via product telemetry.

4. Key Result: Rebuild CHEFS Teams' in-product (Admin) dashboard metrics (formerly available through Metabase) in order to surface various counts and percentages via product telemetry (usage/utilization/engagement etc)

   1. Strategy: query of component type use

   2. Strategy: query of Javascript usage

   3. Strategy: autocomplete form profile Ministry

Sprint Pages