watsonx Orchestrate - Agent Builder

Learn how I delivered the industry-first no-code multi-agentic builder experience that drove >1000% deployment growth, 8K MAUs, and $150M+ in revenue reaching millions of users

watsonx Orchestrate - Agent Builder

Learn how I delivered the industry-first no-code multi-agentic builder experience that drove >1000% deployment growth, 8K MAUs, and $150M+ in revenue reaching millions of users

watsonx Orchestrate - Agent Builder

Learn how I delivered the industry-first no-code multi-agentic builder experience that drove >1000% deployment growth, 8K MAUs, and $150M+ in revenue reaching millions of users

Awards & Recognition

Awards & Recognition

Awards & Recognition

Overview

watsonx Orchestrate is IBM's multi-agent orchestration platform. Agent Builder is its core experienceโ€”a no-code interface that lets business users build AI agents, connect them to tools and workflows, and deploy them across HR, sales, procurement, and customer care.

The platform bridges two worlds: a developer-focused ADK for code-first builders, and the visual Agent Builder for everyone else. My background as a former software developer let me translate complex agentic architecture into UI patterns non-technical users could master in minutes.

We shipped 0โ†’1 in 6 months, launching at IBM THINK 2025 in the CEO and GM keynotes.

My Role

Design Lead & Manager โ€ข Jan 2024 - Present

What I Designed

โ€ข Builder core experience โ€ข Deployment validation

โ€ข Knowledge integration โ€ข External import patterns

โ€ข Agent guardrails โ€ข AI Model picker

โ€ข Future scope & roadmap

โ€ข Builder core experience โ€ข Deployment validation โ€ข Knowledge integration

โ€ข External import patterns โ€ข Agent guardrails โ€ข AI Model picker

โ€ข Future scope & roadmap

Cross Functional Scope

60 Devs โ€ข 10 PMs โ€ข 8 Design Teams โ€ข Content โ€ข Research

I designed the highest-impact features while leading a team of 6 designers globally.
Read the leadership story โ†’

My Role

Design Lead & Manager | Jan 2024 - Present

Cross Functional Scope

60 Devs โ€ข 10 PMs โ€ข 8 Design Teams โ€ข Content โ€ข Research

What I Designed

โ€ข Core experience

โ€ข Deployment validation

โ€ข Knowledge integration

โ€ข Import patterns

โ€ข Model picker

โ€ข Future scope

I designed the highest-impact features while leading a team of 6 designers globally.
Read the leadership story โ†’

>1000%

Agent deployment growth since launch

8000+

Monthly active users building agents

<4 mins

Average agent creation time-to-value

$150M

Recognized revenue in Q3 2025

The Problem

Three products. Seven entry points. Zero clarity on where to start.

When I joined watsonx Orchestrate in early 2024, the platform was three products duct-taped together: Watson Assistant, Business Automation, and Orchestrate. Users told us they were confused. Our data confirmed it: 60% of users who started building never deployed. Five major clientsโ€”representing $300M in retention riskโ€”wanted to build agents but refused to migrate. We weren't just fixing UX. We were fighting to keep the business alive while making the leap into the agentic era.

Leadership committed to a new direction: rebuild the platform on LangGraph, IBM's agentic framework, and unify everything into a single Agent Builder experience.

That solved the strategy problem. It created a design problem.

Under the hood: LangGraph agents route, reason, plan, and call tools dynamically. The UI needed to expose this power without exposing this complexity.

LangGraph is powerfulโ€”but it's built for developers writing code. The architecture is non-linear: nodes, edges, state management, conditional loops that revisit earlier steps. There's no visual metaphor baked in.

Our target users weren't developers. They were the same HR managers, procurement leads, and sales ops specialists who'd spent years on Watson Assistant. They thought in linear flows: Step 1 โ†’ Step 2 โ†’ Step 3 โ†’ Done. They expected forms, wizards, deterministic outcomes.

The system was correct by architecture and unusable by cognition.

The Problem

Three products. Seven entry points. Zero clarity on where to start.

When I joined watsonx Orchestrate in early 2024, the platform was three products duct-taped together: Watson Assistant, Business Automation, and Orchestrate. Users told us they were confused. Our data confirmed it: 60% of users who started building never deployed. Five major clientsโ€”representing $300M in retention riskโ€”wanted to build agents but refused to migrate. We weren't just fixing UX. We were fighting to keep the business alive while making the leap into the agentic era.

What was broken?

Three products. One Frankenstein.

Automation + Assistant + Orchestrate duct-taped together

60% never deployed

Users abandoned, no guidance, total overwhelm

$300M retention risk

5 major clients wanted agents, refused to migrate

"No-code" requiring developers

Pro-code disguised as simplicity

Weeks to configure basics

Every domain needed months of custom implementation

" This manual work was a huge obstacle of time and effort standing in the way of our real work."

โ€” IBM HR Business Partner

" This manual work was a huge obstacle of time and effort standing in the way of our real work."
โ€” IBM HR Business Partner
The old homepage: 7 entry points, no clear path

The old homepage: 7 entry points, no clear path

Leadership committed to a new direction: rebuild the platform on LangGraph, IBM's agentic framework, and unify everything into a single Agent Builder experience.

That solved the strategy problem. It created a design problem.

LangGraph is powerfulโ€”but it's built for developers writing code. The architecture is non-linear: nodes, edges, state management, conditional loops that revisit earlier steps. There's no visual metaphor baked in.

Under the hood: LangGraph agents route, reason, plan, and call tools dynamically. The UI needed to expose this power without exposing this complexity.

Our target users weren't developers. They were the same HR managers, procurement leads, and sales ops specialists who'd spent years on Watson Assistant. They thought in linear flows: Step 1 โ†’ Step 2 โ†’ Step 3 โ†’ Done. They expected forms, wizards, deterministic outcomes.

The system was correct by architecture and unusable by cognition.

What user knew (Watson Assistant)
What we were building (Agent Builder)

Linear, deterministic flows

Non-linear graphs with state

One assistant at a time

Multi-agent orchestration

"If user says X, respond Y"

"Agent decides based on context"

Build โ†’ Test โ†’ Deploy (sequential)

Configure pieces that interact dynamically

Design Challenge:

How do you represent a non-linear, stateful graph in a linear UIโ€”without lying about what's actually happening?

Design Challenge:

How do you represent a non-linear, stateful graph in a linear UIโ€”without lying about what's actually happening?

The Exploration

Three approaches. Two rejections. One insight.

1

Node-Based Canvas: Rejected โŒ

I explored a visual canvas matching LangGraph's architectureโ€”nodes, edges, drag-and-drop. Competitors were doing it. It felt architecturally honest.

I rejected it after user tests. Users froze. The empty canvas problem paralyzed them. HR managers didn't know where to start.

I saw merit in visualizing agent relationships, but shelved it for post-MVP. The 2026 Canvas Builder roadmap revisits this.

Canvas exploration: architecturally honest, cognitively overwhelming.

Canvas exploration: architecturally honest, cognitively overwhelming.

2

Rigid Stepper Wizard: Rejected โŒ

I swung the opposite direction. Step 1 โ†’ Step 2 โ†’ Step 3 โ†’ โ€ฆ โ†’ Done. Maximum guidance.

I rejected it too. Too rigid. Users couldn't jump back to test. Couldn't iterate in realtime. Worst of all, it lied about how agents actually workโ€”they're not linear.

Stepper exploration: maximum guidance, zero flexibility

Stepper exploration: maximum guidance, zero flexibility

3

Anchored Tabs: Shipped โœ…

Anchored Tabs: Shipped โœ…

Four tabs: Profile, Knowledge, Toolset, Behavior.

Free navigation. Scroll-based progression. Configure pieces that interact dynamicallyโ€”matching how agents actually work.

I killed the cool thing to save the outcome.

What shipped: Anchored tabs with free navigation and live preview.

What shipped: Anchored tabs with free navigation and live preview.

The Transformation

From seven entry points to one. From weeks to configure to minutes to deploy

New watsonx Orchestrate homepage with a very familiar chat interface that also helps onboard a new user & guides them towards building
A true no-code, intuitively guided AI agent builder experience that we pioneered

Design Principles

Guided without force

4-tab structure, auto-scroll

Guided without force

4-tab structure, auto-scroll

See what you're building

Live preview, split screen

See what you're building

Live preview, split screen

Trust Through Transparency

Reasoning traces, guidelines

Trust Through Transparency

Reasoning traces, guidelines

Open Yet Secure

Private knowledge + external integrations

Open Yet Secure

Private knowledge + external integrations

The Solution

One builder experience. Agentic platform from the ground up

I partnered with product leadership to reimagine watsonx Orchestrate from first principlesโ€”building a truly no-code agentic platform on LangGraph. Instead of seven entry points, we created one. Instead of weeks to configure, we designed for <10 minutes to deploy. My role extended beyond UI: I drove alignment across product, engineering, and business while personally designing the core experiences.

Four principles, one screen.

Below, see how each of the four design principles came to lifeโ€”all in service of one North Star: <10 minutes to productive agent.

  1. Guided without Force

The 4-tab structure guides users naturallyโ€”Profile, Knowledge, Toolset, Behavior. Instead of rigid steps, users scroll through tabs filling out sections as they go. Before they realize it, they've built a complete agent. No manual. No training videos. Just intuitive progression that aligns with the underlying agent architecture.

Design Decision: Intuitive Flow, Zero Training

Auto-scrolling page anchors instead of forced step-by-step wizards. Builders maintain control while getting clear direction and are not exposed to the underlying complex technical architecture.

  1. See What You're Building

"Seeing is believing" drove a core layout decision: I wanted the preview chat to occupy 50% of the screen, equal to the builder itself. Every change instantly reflects in the preview. Builders test as they build, eliminating surprises at deployment.

Design Decision: Real-Time Preview

Live preview on right, builder on leftโ€”not hidden in a separate tab or modal. Constant feedback loop builds confidence.

  1. Trust Through Transparency

Enterprise users need to understand how agents make decisions. I wanted the interface to expose reasoning traces, data sources, decision paths, and guidelines enforcementโ€”making AI logic comprehensible to non-technical users. No black boxes.

Guidelines give builders full control over agent behaviorโ€”preventing off-topic responses and enforcing compliance rules. Reasoning traces show exactly what the agent did: which guidelines it followed, which tools it invoked, and what data it used. End users see simplified responses; builders see complete execution details.

Design Decision: Trust Through Transparency & Control

Detailed reasoning traces + guidelines system. Expandable reasoning steps in preview chat showing tool invocations, input/output, and guideline enforcement. Critical for governance, compliance, and builder confidence.

Reasoning traces: see exactly what the agent did

Reasoning traces: see exactly what the agent did

Guidelines: control agent behavior and enforce compliance

Guidelines: control agent behavior and enforce compliance

  1. Open Yet Secure

Customers want agents grounded in their company data while connecting to external systems. Knowledge integration is a core tabโ€”upload and preview in seconds. I built import patterns to bridge UI and code, letting external agents and tools integrate seamlessly. Privacy-first, yet fundamentally collaborative and open for future scale.

Design Decision: Open Architecture with Private Context

Knowledge as core tab, not advanced feature. Import patterns supporting external agents (Langflow, A2A, MCP). Enterprise privacy without sacrificing extensibility.

Knowledge tab: upload private docs, agent cites company sources

Knowledge tab: upload private docs, agent cites company sources

Toolset: connect external tools and agents securely

Toolset: connect external tools and agents securely

See It In Action

Agent Builder Demo: Watch me build a "Cat Facts" Agent under 4 mins demonstrating guided build, knowledge grounding, realtime testing & guardrails in action.

The Impact

We shipped in July 2025. The numbers told the story.

Average build time is 3m 49s, 62% under our goal (<10 min)

Improved NPS by 71 points, from -28.7 in 2023 to +42.6 in 2025

What the data showed

  • 11K unique users over 6 months

  • Daily active users steady at 200-400

  • 30+ enterprise customers deployed

What users told us

  • "Easy to use but lacking some features"

  • Model selection still confusing

  • Deployment failures surfaced too late

  • Wanted more 3rd-party integrations

Business & Product Impact

$150M

recognized revenue in Q3 2025

$300M-$500M

at-risk accounts retained

30+

enterprise customers deployed

8K

monthly active users building agents

<4 min

average agent creation time-to-value

75%

reduction in visual/UX bugs

40%

faster dev cycles

11k unique users over 6 months, daily active users steady at 200-400

11k unique users over 6 months, daily active users steady at 200-400

Customer Outcomes

The platform now powers enterprise AI across Fortune 500 companiesโ€”from HR automation to procurement to customer care. Client feedback consistently cited the intuitive experience, flexibility, and reliability as key value drivers.

IBM HR (AskHR)

94% of 10M+ annual inquiries resolved, >1M HR transactions processed

View case study โ†’

Dun & Bradstreet

360ยฐ risk supplier assessments, 10-20% Estimated reduction in time for procurement tasks

View case study โ†’

Lockheed Martin

Agentic AI ecosystem for 10,000 engineersโ€”replaced 46 tools with one platform

View case study โ†’

Wimbledon

16M fan interactions with 'Match Chat' agent โ€” processed 2.7M data points

View case study โ†’

These insights drove our next improvements.

Principle-Guided Improvements

1. Transparency: Model Selection

Users struggled understanding model differencesโ€”cost, deprecation, performance impact hidden behind tooltips. I designed a detailed modal with plain-language descriptions, pricing, and status indicators.

  1. Trust: Deployment Summary

Users deployed blindโ€”no way to verify agents would work. I designed a pre-deployment summary showing configuration details, connection status, and errors. Users fix issues before deploying, ensuring success.

I designed and launched the pre-deloyment summary for trust building

I designed and launched the pre-deloyment summary for trust building

Impact: >80% increase in successful agent deployments

Impact: >80% increase in successful agent deployments

  1. Open and Scalable: Dynamic Import Pattern

Dev and runtime teams wanted external connections (A2A, Langflow, MCP, custom APIs), but each had different credentials and config. Adding individual tabs would've created many tabsโ€”chaos.

I designed categorized selection with dynamic forms that load the right fields per connection type.

Impact: Scalable pattern that accommodates future integrations without UI bloat.

External import pattern in action

External import pattern in action

  1. Guided Without Force: IA Strategy

As UX owner, I pushed back on Voice and Channels teams wanting to add features directly in builderโ€”would've killed our <4 min goal.

I introduced "Manage" as a new top-level IA section for advanced configs. Kept builder focused on core creation flow.

Impact: Maintained <4 min build time, removed clutter, scalable for future

Before: Voice configuration cluttered builder, adding friction.
After: Split enablement (in builder) from configuration (in Manage). Pattern scaled to Phone, Connectionsโ€”maintained <4 min while adding features.

Before: Voice configuration cluttered builder, adding friction.
After: Split enablement (in builder) from configuration (in Manage). Pattern scaled to Phone, Connectionsโ€”maintained <4 min while adding features.

  1. Governance: Agent Analytics

Post-deployment monitoring was a top customer request. We designed analytics dashboard showing usage, success rates, tool invocations at a tenant level as well as individual agent level including accessing traces for maximum governance and control. Users could confidently monitor their agents post deployment and identify issues as soon as they occur.

What's Next

2026 Vision - Canvas Builder & AI Assisted Agent Builder

I led both these initiatives based on customer requests and competitive analysis. Pitched to leadership, driving exploration of visual agentic workflow canvas based on earlier explorations for complex orchestration, relationship visualization and AI-assisted agent generation.

Currently in development.

Exploration of a canvas based visual agentic workflow builder

Exploration of a canvas based visual agentic workflow builder

Exploration & Pitching of an AI Assisted Agent generation experience

Exploration & Pitching of an AI Assisted Agent generation experience

Want to reach me directly?

Email me at hello@sampattnaik.com or connect on LinkedIn

Working Remotely ๐Ÿ‘จ๐Ÿปโ€๐Ÿ’ป

ยท

Austin

ยท

Made with ๐ŸŒฎ, โ˜•๏ธ , curiosity, and a lil help from a friend named Claude

Want to reach me directly?

Email me at hello@sampattnaik.com or connect on LinkedIn

Want to reach me directly?

Email me at hello@sampattnaik.com or connect on LinkedIn

Working Remotely ๐Ÿ‘จ๐Ÿปโ€๐Ÿ’ป

ยท

Austin

ยท

Made with ๐ŸŒฎ, โ˜•๏ธ , curiosity, and a lil help from a friend named Claude