Concourse & Jira DC Portal

Problem:
Client-facing pursuit and engagement teams—especially first-time or infrequent users—arrive on the Concourse homepage ready to start scoping or planning delivery. But the required first step of creating a workspace feels disconnected from their intent, adds cognitive overhead, and delays value. Users don’t think “create a workspace”—they think “I need to build a plan.”

Hypothesis:
If we enable Smart Starts by automatically surfacing personalized, pursuit-specific starting points—powered by Salesforce signals and workspace pre-creation—then time-to-scope initiation will drop, cognitive effort will decline, and scoping during the pursuit phase (not just delivery) will increase measurably.

Suggested Next Actions:

1. Draft Aha! Feature: “Smart Starts - Context-Aware Homepage Launch”
   Why: Establishes this as a strategic UX capability under Scope Evolution
   How: Frame it around Salesforce-driven entry points, workspace bypass, and scoping kickoff

2. Validate concept with first-time users via clickable prototype
   Why: Test if Smart Starts reduces hesitation and increases scoping confidence
   How / Test / Metric: Figma or Invision prototype showing auto-surfaced entries; track comprehension, clicks, sentiment

3. Instrument Pendo to benchmark current homepage → scope behavior
   Why: Sets a baseline to measure Smart Starts' impact
   How: Tag homepage views, workspace clicks, scope starts; segment by new vs. returning users

4. Track scoping activity by engagement phase (pursuit vs delivery)
   Why: Validates if early scoping increases as friction is removed
   How: Add Pendo tags or Aha feedback fields for phase tagging, analyze shifts post-launch

5. Assess Salesforce integration triggers and data fields with a dev resource
   Why: Determines technical feasibility and required effort for backend enablers
   How: Collaborate with Salesforce admins to map opportunity stages to Smart Start creation logic