Concourse & Jira DC Portal

Background

Solution Studio Architects use a variety of AI tools and content repositories (e.g., ChatGPTs, Copilot agents, SharePoint folders, benchmarking tools) to create solution plans during the pursuit phase. These tools are scattered across different platforms with no central workflow or shared workspace, leading to inefficiencies in how inputs are accessed and outputs are stored.

Challenge

The current setup leads to:

• Repetitive inputs (e.g., uploading the same RFP or client details to multiple tools)

• Context loss across tools and team members

• Disjointed storage of outputs in personal folders or temporary locations

• Inefficient collaboration between architects and pursuit teams

• Inconsistent application of PwC data governance and risk controls

Proposed Solution: Solution Studio Workflow Hub

Develop a centralized, intelligent workflow hub that serves as the operational and collaboration layer for Solution Plan creation. This hub should:

1. Guide a Connected Solution Plan Flow

• Define a clear step-by-step process across the 10-layer solution plan.

• Ensure outputs from one step feed into the next (e.g., Vision → Capabilities → Architecture → RICEF).

2. Retain Core Pursuit Inputs for Reuse

• Store and reuse key information such as:

  • RFP

  • Client industry, work requested

  • Workstreams and offerings in scope

3. Enable Centralized Document Management

• Store solution plan artifacts, slides, AI tool outputs, and research in a single, structured location tied to the engagement.

• Allow version control and access history across team members.

4. Provide Shared Access Across Roles

• Grant appropriate visibility and editing rights to:

  • Architects

  • Pursuit leads

  • Pricing & commercial team

  • CXO and design

5. Uphold PwC Risk Standards

• Enable compliant storage of client-sensitive data.

• Ensure records of engagement planning meet legal and documentation standards.

6. Connect to PwC & External Knowledge Sources

• Enable seamless integration or access to:

  • Connected Source

  • Solution Studio & Practice SharePoints

  • LEAP

  • Benchmarking

  • PwC Industry Insights

  • GIF

  • Trusted web sources (e.g., SEC filings, 10-Ks)

7. Incorporate Reusable Templates and Gold Standards

• Surface gold-standard solution plans, vision statements, architecture diagrams, and KPI mappings for reference or reuse.

• Promote continuous learning and consistency across pursuits.

8. Integrate with Concourse and Core Studio Tools

• Embed into or connect with Concourse components like:

  • Intelligent Scoping

  • Dev Object Generator

  • Engagement workspace

Key Benefits

• Improved Continuity and Efficiency: By connecting the various steps in the pursuit process through a seamless flow, the hub minimizes repetitive inputs and ensures that all work builds upon previous efforts, reducing redundancy and saving time.

• Enhanced Document Management and Accessibility: Centralized storage of documents within the engagement or a common repository makes it easier for architects and pursuit team members to locate, update, and build upon existing solution plans without losing context.

• Stronger Collaboration Across Teams: With a shared, easily accessible platform, collaboration between Solution Studio Architects and the broader pursuit team becomes more effective, promoting real-time knowledge sharing and alignment.

• Knowledge Reuse & Standardization: Promotes sharing of templates and best practices to improve quality and consistency over time.

• Governance & Compliance: Ensures proper documentation storage, access tracking, and data handling per PwC standards

Visual Ideas: https://miro.com/app/board/uXjVIjywacc=/?moveToWidget=3458764637370231135&cot=14

Notes from Interviews:

Dedicated Concourse workspace for managing 10-layer solution plans, distinct from delivery tools. Envisions it as the central place where architects do the actual work of building the solution plan.

Sanjyoth Described it as:

“A solution plan development workbench which provides the architects all the tools available... It should give access to relevant content, allow drag-and-drop from a repository, and track progress across layers.”

Emphasized:

• Persona-based roles and access.

• Plug-and-play integration with tools like GPTs, PDM, E-Pro, and repositories.

• The importance of designing the workbench before building isolated tools so they can eventually connect into a cohesive system.

Strongly supports tying it into Concourse, if possible, since it’s already used for delivery:

“If we use Concourse in the pursuit process, that should seamlessly flow into delivery.” Sanjyoth

Diego thoughts:

“The Workbench makes sense and that is the North Star… it ultimately hosts our processes and tools all in one place.”

Stressed business value:

• The purpose is to help PwC win more and be more competitive.

• Wants tools that help with scoping, pricing, and estimation to eventually be included in the Workbench.