Platform Lite
The Workbench was designed to be powerful and flexible, but this openness came at a cost. For new users, the steps to build a project felt overwhelming. Even experienced users needed extra time to navigate long forms, map fields, and configure jobs correctly. Leadership wanted to lower the barrier for entry and attract a broader audience without sacrificing consistency with the Workbench.
Challenge
The task was to create a simplified experience for project creation, something guided, reliable, and approachable. Instead of many free-form screens, the flow needed to feel like a wizard: one clear step at a time, with guardrails and defaults to prevent errors. At the same time, each step had to remain compatible with the Workbench so advanced users could still transition between the two systems.
Flow Definition
The PRD served as the starting point. It outlined the major steps for an Integration (Hoovers) project: selecting data, mapping fields, and exporting results. Each step in the PRD was reviewed with engineering to understand dependencies and what could be simplified.
The outcome was a guided wizard flow. Instead of long forms with many options on one screen, the work was broken into discrete pages. Each page had one clear purpose and carried users forward to the next step.
This structure provided two advantages. New users could progress without being overwhelmed, while advanced users recognized a one-to-one relationship with Workbench tasks.
PRD Steps
→
Wizard Screens
Select data source
Filter record batch
Transformation
Select data target
Field mapping
Matching criteria
Data merge
Scheduling
→
→
→
→
→
→
→
→
1. Select Data Source
2. Filter Records
3. Transform Data
4. Select Target System
5. Field Mapping
6. Matching & Merge Rules
7. Data Merge
8. Scheduling
Early Wireframes
Initial wireframes were structured as strict wizard pages. Each screen contained one primary action with clear “Next” and “Back” navigation, and a progress bar at the top kept users oriented. This structure intentionally reduced distractions and helped first-time users build confidence.
Exploration of early wireframes. Multiple directions tested, from job-flow inspired pages to scratch wizard concepts.
Exploring Alternatives
Two models were explored. A flat navigation allowed users to skip between steps, while a strict wizard locked the order. Testing showed that the wizard approach produced fewer configuration errors, especially during field mapping and scheduling. The wizard model was chosen as the foundation for Platform Lite.
Transformation Step
Generic Integration projects required data transformations. To support this, a dedicated step was added where users could standardize countries or states, change attribute types, combine fields, or add prefixes and suffixes. Each choice mapped directly to existing Workbench task templates, but was simplified into a more approachable UI. Output attributes were automatically named using a consistent prefix system.
Iteration and Review
Prototypes were reviewed in working sessions with managers and engineers. Feedback led to refinements such as placing credential entry at the start to avoid errors later, defaulting attribute selection to all fields, and adding a “show differences only” toggle for field mapping. Empty states, loading states, and error messaging were also added to support edge cases.
Field Mapping
Field mapping emerged as the most complex part of the design. Users needed to map attributes between Hoovers and external systems like Salesloft or Outreach. Challenges included large field sets, data type mismatches, and the need for add/remove flexibility.
The design solution introduced two tabs, Contacts and Accounts, each pre-populated with default fields from D&B. Users could reset mappings to defaults, add new rows, or delete existing ones. If mismatched data types were detected, the system automatically created a tagging task in the background. These decisions reduced the chance of critical errors and aligned with familiar Workbench logic.
Scheduling
The final step allowed users to schedule recurring runs or configure manual runs. The interface was intentionally minimal, using a calendar picker and time selector. This matched the Workbench model while reducing clutter.
Outcome
Platform Lite allowed users to create an integration project in under ten minutes, compared to the longer setup times in the Workbench. Defaults reduced configuration errors, while advanced controls remained available when needed. The design preserved visual and structural consistency with the Workbench, ensuring that experienced users did not need to relearn familiar concepts.
The first release focused on Integration (Hoovers). Future versions were planned to expand into Data Quality and other project types, using the same guided model.