Concourse & Jira DC Portal

✅ Put Simply

Introduce a dynamic, visual “Explorer” panel that surfaces only the Playbooks relevant to the selected Offerings — letting users toggle seamlessly between scoped Work Items and the Playbooks used to deliver them.

✅ Why It Matters

Users don’t always know which Playbooks to use — especially in early-stage pursuits or scoping sessions. Today, selecting Offerings in scope and reviewing the delivery approach are disconnected workflows.

The Playbook Explorer closes that gap by:

• Automatically surfacing Playbooks that map to the selected Offerings and their inferred Building Blocks.

• Visually aligning Playbooks with the stages of PDM via a familiar diagram.

• Allowing users to switch contexts easily between “what we’re doing” (Work Items) and “how we’ll do it” (Playbooks).

This improves proposal quality, accelerates delivery setup, and supports greater Playbook adoption without disrupting the scoping flow.

✅ High-Level Acceptance Criteria

1. Given a user is in the scoping workflow,
   When they select one or more Offerings,
   Then the Playbook Explorer should display a visual map of the Playbooks inferred from the associated Building Blocks.

2. Given the Playbook Explorer is visible,
   When users interact with the map,
   Then Playbooks should be arranged across the four stages of PDM in a canvas-style layout, highlighting relevant Frameworks in each stage.

3. Given a user is reviewing a scoped Work Item,
   When they toggle to the Explorer panel,
   Then they should see which Playbook(s) inform delivery for that Work Item (with one-click access to frameworks and guidance).

4. Given a user is toggling between scopes and Playbooks,
   When they click into a Framework,
   Then details should appear inline or in a slide-out panel, not disrupting their scoping flow.

5. Given some engagements have complex or multi-Offering scopes,
   When multiple Playbooks are relevant,
   Then the Explorer should clearly segment which Frameworks belong to which Playbooks, with optional filters by Offering or Building Block.

6. Given users may need to validate or learn more,
   When hovering over a Framework or Playbook in the map,
   Then they should see a quick summary and have the option to preview or open the full guidance page.

7. Given the Explorer complements the existing scoping workflow,
   When implemented,
   Then it should follow Concourse’s UX patterns and maintain clarity between “what’s in scope” (Work Items) and “how we deliver” (Playbooks).