Page Comparison

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

1. Key Result: seeing Effect a measurable reduction in the level of technical knowledge and expertise held by chefs CHEFS users.

   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. 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.

Team Objective: Enhanced high-complexity forms support

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

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

   2. Strategy: Improved documentation about the API usage

      1. Tactic: update the API spec, make a postman collection,

      2. Tactic: make the API Key creation step great again

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

   1. Strategy: Enhanced API capabilities

   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: Better understanding of Identify the value of Dev and Test formsform classes via product telemetry.

4. Key Result: Dashboard metrics to more accurately make 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