Case Study — Product Ownership at IBM
Empowering IBM Sellers: A UX-Driven Guidebook for Sales Enablement
IBM's Cognitive Sales Advisor platform was meant to enhance the sales process, but sellers saw it as an added burden and managers lacked the resources to demonstrate its value. I led the Digital Sellers Guidebook — a centralized, WordPress-based resource built from stakeholder research to close that gap.
The problem#
IBM's Cognitive Sales Advisor platform was designed to enhance the sales process, but adoption rates were low. Sellers, focused on closing deals, viewed the platform as an additional burden rather than a helpful tool. Managers, despite incentives to promote it, lacked the engagement and resources to effectively demonstrate its value — a barrier to adoption across the organization that a comprehensive, user-friendly resource was needed to close.
Process#
I conducted stakeholder interviews with sellers and managers to understand the barriers to adoption, which surfaced the real constraint: high cognitive load and limited time for training, not a lack of awareness. WordPress was the deliberate technical choice — it allowed easy integration with existing IBM tools rather than adding another system for sellers to learn.
Research and analysis
Stakeholder interviews with sellers and managers surfaced the real barriers: high cognitive load, limited time for training, and a lack of clear, accessible resources. Existing workflows and tools were analyzed for integration opportunities.
Content strategy
Built around three pillars: product pages (features, benefits, seller testimonials), a knowledge base segmented by role (general users, enterprise sellers, other specific roles), and a video library organized and searchable by user goals.
Prototyping and testing
Wireframes and interactive prototypes were tested with sellers and managers; feedback shaped navigation, content layout, and search functionality before launch.
Development, launch, and iteration
Built on WordPress in collaboration with developers for seamless integration with existing IBM tools, then launched after QA testing. Post-launch, content continued to expand to support new initiatives and evolving user needs.
WordPress was chosen for tool familiarity and integration, not for being the most powerful platform available — the tradeoff was accepting its constraints in exchange for a resource sellers and managers could actually adopt inside their existing workflow.
What it surfaced#
This case study reports what the source material claims, not an independently verified figure: no adoption percentage was tracked, and none is claimed here.
Increased platform adoption
A noticeable uptick in Cognitive Sales Advisor usage among both managers and sellers, per the original case study — not a measured percentage.
Executive recognition
The guidebook was praised as IBM's most comprehensive internal resource for sellers.
Sustained engagement
Content expansion after launch supported new initiatives and adapted to evolving user needs.
Lessons#
Cognitive load, not awareness, was the real barrier
Sellers weren't unaware of the platform — they were focused on closing deals and had no bandwidth for anything that felt like extra training. Simplifying the path to value mattered more than promoting the platform harder.
Content strategy is a design decision, not an afterthought
Segmenting the knowledge base by role and organizing the video library by user goals, rather than shipping one undifferentiated resource, is what made the guidebook usable across a diverse seller and manager audience.
Iteration kept the resource relevant after launch
Continuing to gather feedback and expand content post-launch — rather than treating launch as the finish line — is what let the guidebook adapt to new initiatives instead of going stale.
FAQ#
Did the guidebook measurably increase adoption?
The original case study reports a noticeable uptick in usage and recognition as IBM's most comprehensive internal resource for sellers, but no specific adoption percentage was tracked or verified — this case study does not claim one.
Why WordPress instead of a more specialized platform?
Tool familiarity and integration with IBM's existing systems — sellers and managers could adopt a resource built on a platform their teams already knew, rather than learning something new on top of the platform they were already resisting.
Want the details?
Happy to walk through the stakeholder research, the content strategy, or how the guidebook evolved after launch.