Skip to Main Content
Concourse & Jira Cloud Portal
ADD A NEW IDEA

Pinned ideas

PINNED Digital Assets - Consider Hierarchy and Tagging to remove repetitive Assets
I can see why the assets repeat themselves but simple use of hierarchy and metadata tagging would allow for different views and sorts without repeating the assets. Also - it would be good to delineate between external assets and internal PwC devel...

All ideas

Showing 1291 of 1291

Discovery- Define Seamless Workflow Integration Between Concourse and Outcomes Hub for Managed Services

Put Simply: Create a clearly defined process for how and when to shift from Concourse (project setup) to Outcomes Hub (managed services delivery), including roles, data, and triggers. Why it Matters: As PwC engagements increasingly include long-te...
Ritu Raj Agrawal 4 months ago in  0 Not started

Guided Workflow for Pursuit Phase Engagement Leaders

Put Simply: Create a step-by-step guided workflow for engagement leaders—especially new, experienced joiners—to manage work efficiently during the pursuit phase using tools like Salesforce AFS, Flex, Team Builder, and Concourse. Why it Matters: Fa...
Ritu Raj Agrawal 4 months ago in  0 Not started

Metadata Management & Tagging Layer

Put Simply: Introduce a dynamic, centralized tagging service. Why It Matters: Allows user-role-based personalization and dynamic filtering. What’s Needed: Tag management API Support for role, stage, use case tags Not in Scope: AI-base...
Garrett Kelchner 4 months ago in  0 Not started

Governance Workflow for Content Publishing

Put Simply: Introduce publishing workflow for playbook content changes. Why It Matters: Ensures quality and compliance in delivery standards. What’s Needed: Contributor → Reviewer → Publisher roles Version history and approval status tracki...
Garrett Kelchner 4 months ago in  0 Not started

Versioned API Endpoints for All Delivery Standard Content

Put Simply: Expose playbook content via versioned APIs for consistent integration. Why It Matters: Enables real-time content delivery and modular architecture. What’s Needed: Versioned APIs for all content types Support for semantic version...
Garrett Kelchner 4 months ago in  0 PM Refinement

Dynamic Content Management via Headless CMS

Put Simply: Replace static JSON files with structured content hosted in a headless CMS or PDM-native store. Why It Matters: Enables real-time content updates and a scalable publishing process. What’s Needed: CMS matching prototype schemas A...
Garrett Kelchner 4 months ago in  0 PM Refinement

Visual Framework Cards & Activity Pages

Put Simply: Consistent visual format to render each playbook activity with static content fields. Why It Matters: Establishes UI pattern for structured and actionable guidance. What’s Needed (Static): JSON schema with: Purpose, FrameworkVis...
Garrett Kelchner 4 months ago in  0 Not started

Structured Content Schema for AI Enablement

Put Simply: Break down content into fielded, machine-readable format. Why It Matters: Enables smarter AI responses and content targeting. What’s Needed: Fields like Purpose, Entry/Exit Criteria, Tools, Pro Tips Decomposition of unstructured...
Garrett Kelchner 4 months ago in  0 Dev Refinement

Playbook Explorer (Post-Scoping Canvas UI)

✅ 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 User...
Garrett Kelchner 4 months ago in  0 Not started

Delivery Standard: Inline Flyout for Work Items with Playbooks Mapped

✅ Put Simply Add inline indicators and a flyout panel within the Delivery Plan view so users can see when a Work Item is backed by Playbook guidance — and view the related Playbook content without leaving their delivery workspace. ✅ Why It Matters...
Garrett Kelchner 4 months ago in  0 Not started