The recurring issue faced by Cloud Kicks involves a power imbalance and frequent re-prioritization by the VP of Athleisure, which disrupts project management meetings and limits time for other priorities. Establishing a monthly executive steering committee can address these issues effectively.
Here's why this is the best approach:
Balanced Oversight and Governance: An executive steering committee brings together key decision-makers to review priorities, manage budget allocations, and ensure all business lines are fairly represented in development planning. This provides a formal structure to manage competing interests.
Equitable Development Allocation: By involving multiple executives, the steering committee can objectively assess and allocate resources among business lines, helping to prevent one group from overshadowing others.
This will help maintain balanced focus and avoid over-prioritizing certain projects.
Strategic Decision-Making: With a recurring monthly meeting, the committee can focus on big-picture decisions, reducing the likelihood of frequent, ad hoc project adjustments that derail meetings and detract from strategic discussions.
Option A (weekly all-hands call) may be too frequent and is not ideal for executive decision-making. Option C (dividing the development team) could lead to resource inefficiencies and reduce flexibility. The steering committee approach is a standard Salesforce-recommended best practice for managing cross-functional priorities and balancing strategic initiatives. For more on governance best practices, refer to Salesforce's guide on Governance Frameworks.

Best Case includes amounts you are likely to close, closed/won opportunity amounts, and amounts in the Commit category Closed includes amounts for closed/won opportunities Commit includes amounts you are confident about closing and closed/won opportunity amounts Omitted means the amount does not contribute to your forecast Pipeline includes amounts from all open opportunities

With Cloud Kicks having a large number of Account records and a substantial volume of Invoice records linked via a master-detail relationship, page load performance can be affected when a large related list is displayed. Moving the Invoice related list to a separate tab on the Account record page can help alleviate this issue by reducing the initial data load required when viewing the Account record.
* Optimizing Page Layouts for Performance: By placing the related list on a separate tab, Salesforce loads the tab's contents only when accessed, rather than at the initial page load. This can significantly improve page performance, especially with large data volumes.
* User Experience and Adoption: Communicating this change ensures that users understand where to find the Invoice information while benefiting from faster page load times.
Option A (converting to a lookup relationship) could alter the data model and existing functionality, and Option C (indexing) may not address initial page load performance directly. Salesforce recommends using custom page layouts and tabs to manage large related lists as part of performance optimization best practices, detailed in Salesforce Large Data Volume Considerations.