IBM Software / SaaS Global

IBM Chief Analytics Office

IBM product teams were receiving tens of thousands of feature requests, categorizing many of them manually, and using inconsistent local tools that made prioritization slow, duplicative, and hard to compare across products.

10 software products
128 product managers
500+ product managers across IBM
over 250,000 employees

Reported impact

Business outcome

The pilot helped product managers make more consistent, data-driven prioritization decisions, reduce manual review work, and build a common framework for roadmap planning across IBM software teams.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

The IBM Chief Analytics Office piloted a watsonx.ai-based prioritization workflow to help product managers process feature ideas across IBM teams. Instead of relying on an optional user-entered theme field and inconsistent local tooling, the solution reads each idea description, applies prompt engineering in watsonx.ai, assigns the request to one or more of eight predefined ISO-aligned categories, and calculates a recommendation using the RICE scoring framework. The workflow then logs prioritization results into the group's roadmap tool so teams can collaborate, track progress, visualize trends, and compare ideas using a shared language rather than isolated spreadsheets and directories. During the six-month pilot, 128 product managers across 10 software products used the approach to reduce manual categorization work and make roadmap decisions faster. The design turns dispersed request data into a repeatable AI pipeline for software planning and portfolio governance.

Data flow

Feature requests enter the workflow from existing idea-submission processes, watsonx.ai categorizes and scores them with RICE, and the results are logged into the product roadmap tool for collaboration, tracking, and visualization.

Solution architecture

1 components · 1 layer
  1. Compute
    • IBM watsonx.ai Reads feature requests, assigns categories through prompt engineering, and computes prioritization guidance using RICE scoring.

Architecture clues

  • Before the pilot, teams stored configurations and outputs in local directories that created accidental duplicates.
  • Prioritization results are logged into the group's roadmap tool for real-time progress tracking.
  • The model uses the RICE scoring methodology and eight predefined ISO-aligned categories.

Evidence from the source

"128 product managers focused on 10 software products"
"Across IBM, there are more than 500 product managers"
"The model utilizes the RICE (Reach - Impact - Confidence - Effort) scoring methodology"
"Watsonx.ai reads the idea description and assigns it to a category through prompt engineering."
"received over 30,000 new ideas and feature requests from users during the past year"
Transparency Evidence & methodology 70/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value70/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    IBM Chief Analytics Office customer story

    First-party
    https://www.ibm.com/case-studies/assisted-idea-prioritization
    Source type
    Vendor-published customer story
    Published
    May 14, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.