Turning a Distrusted Pipeline Dashboard into an Operating Rhythm
Bluepeak Logistics deployed Sales Cloud to 180 reps six months ago. Reps still build pipeline in spreadsheets, and managers do not trust the pipeline dashboard. The org shows 62% of open opportunities with a close date in the current quarter, but 41% have been pushed at least three times. Only 28% of opportunities have any activity in the last 14 days. Stage 3 has 38% of open opportunities, many older than 90 days. Reps say the opportunity page has 47 fields and requires 12 clicks to log a call; managers say reps 'game' the forecast category. Bluepeak has two admins, no developer, and eight weeks before the next quarter. Leadership wants a dashboard it can run the business on and an adoption plan that does not feel like policing.
1. Diagnose the root causes and prioritize the fixes for the next eight weeks.
Read the worked answer
The symptoms point to friction plus unclear rules, not a reporting tool problem. Forty-seven fields and twelve clicks to log a call make the correct behavior harder than the spreadsheet. If stage 3 can hold 38% of open opportunities for over 90 days, the stage definition is too vague. If 41% of deals have been pushed three times, close dates are not credible and forecast category is not controlled.
Prioritize in this order: simplify the opportunity page; define stage exit criteria; automate forecast category from stage and restrict overrides; add a lightweight close-date change reason; make activity capture easy. Do not start with a punitive dashboard. Reps will update fields to satisfy the dashboard rather than to reflect reality.
The eight-week plan should include a pilot with two teams, a champion network, and a weekly manager review using the same definitions. Measure leading indicators such as opportunities with a next step and activity in 14 days, not only forecast accuracy.
2. How would you redesign the opportunity page and data capture to reduce clicks and improve trust?
Read the worked answer
Reduce the page to the fields needed to run a deal: amount, close date, stage, next step, forecast category, owner, account, and product summary. Move administrative and finance-only fields to a separate section or page layout by record type. Use Path with key fields so reps see stage guidance without opening help.
Logging a call should take one or two clicks from the opportunity. Use the standard Log a Call action and make next step and next-step date visible. If Bluepeak has Outlook or Gmail integration, enable activity capture for the pilot group rather than asking reps to duplicate work.
Automate forecast category from stage with a Flow. Allow override only for managers, and require a reason when a close date moves. Keep validation rules few and specific; a page full of blocks will drive reps back to spreadsheets. Test the redesigned page with five reps and count clicks before rollout.
3. Design the dashboard and adoption cadence that leadership can actually run the business on.
Read the worked answer
Build three dashboards, not one mega-dashboard. Pipeline health shows open pipeline by stage, close date, owner, and forecast category, plus aging in stage using opportunity history. Data quality shows opportunities with no activity in 14 days, no next step, no products, and close-date pushes. Forecast vs actual shows commit, best case, and closed by team.
Use dynamic dashboards or scheduled subscriptions so each manager sees their team. Keep definitions visible on the dashboard. Review the same three reports in a weekly 30-minute pipeline meeting: what changed, what is stuck, and what evidence is missing. Managers should coach to stage evidence, not interrogate every field.
Adoption cadence: two pilot teams in weeks 1-2, role-based training in weeks 3-4, full rollout in week 5, and office hours through the quarter. Track adoption with login, activity per rep, opportunities with next step, and forecast accuracy. Publish a before-and-after view so reps see that the dashboard reduces spreadsheet work rather than adding policing.