Validate the following hypotheses around desirability, viability, and feasibility

Desirability

Desirability, in this context, is about providing a compelling enough user experience such that this feature is used, but also that the platform is perceived as higher value

I believe that business goal setting will...

1. (User Journey Timing) be used during the modeling stage by process owners because they want to drive success
2. (Pain Point Existence) make Camunda approachable for more business users because it speaks their language of business goals/KPIs
3. (Willingness to Use) be performed for a majority of processes by process owners because they immediately see the reward from their work
4. (Engagement) improve Optimize usage rates among process owners because they can see relevant information
5. (Key Actions) enable more meaningful dashboards to be built by business users because reports can be tied directly to approved business goals
6. (Key Actions) result in more actionable insights by any Optimize user because they can see how the process needs to improve
7. (Willingness to Pay) improve the likelihood that our customers pay for our products because there is a stronger link between using our product and positive business outcomes

Viability

Viability, in this context, is primarily driven by the interests of adjacent Field Ops teams in driving business success

I believe that business goal setting will...

1. (Marketing) result in significantly stronger positioning by marketing because of the clear link between using our product and positive business outcomes
2. (Customer Success) enable more effective customer conversations by CSMs because they can discuss process health
3. (Consulting) facilitate faster process launch by developers because it provides clear quality criteria and encourages following best practice
4. (Sales) drive faster sales for free trial participants because they can preview the value of Optimize without implementing a full process
5. (Sales) drive upsell for existing CE users because there is a persistent reminder that a feature is locked

Feasibility

Feasibility, in this context, is primarily driven by the time taken to create an initial version and unblock future development work that is aligned with Optimize's vision and roadmap.

I believe that business goal setting will...

1. (Estimate) be feasible for Engineering to build an initial version within 6 weeks
2. (Dependency) not detract from another Camunda component's UX whether or not Optimize is installed
3. (Future Tech) unblock the automatic creation of custom Optimize dashboards
4. (Future Tech) unblock Optimize content from being available anywhere in the Camunda Platform
5. (Future Tech) unblock user alerting on changes in business goal/metric status
6. (Future Tech) unblock Optimize-wide summary statistics from being easily available
7. (Future Tech) unblock the possibility to automatically generate suggestions based on current performance and expressed business goals