Unified Data Management Vision
Defining HubSpot's 2024 UX vision for the Smart CRM — bridging product strategy, user research, and design execution to transform how scaling businesses manage their data.
ROLEUX Design Manager
COMPANYHubSpot
TEAMData Mgmt Group
YEAR2024
01 - MY ROLE & CONTEXT
Owning the vision for how admins experience data in HubSpot's CRM
As Design Manager for HubSpot's Data Management group, I led a team of four product designers — spanning senior ICs and mid-level contributors — responsible for how admins configure, maintain, and understand their CRM data model. Our scope covered properties, objects, associations, permissions, and the emerging data model workspace.
HubSpot's 2024 product strategy centered on a major bet: transforming from a collection of marketing and sales tools into a true customer platform anchored by a "Smart CRM." The CRM mission was clear — become the #1 CRM for scaling businesses. My team's mission laddered directly into that: help more complex companies map their business data and processes inside HubSpot.
The problem was that no one had articulated a unified design vision for how we'd get there. Product strategy existed, but the UX implications — across information architecture, admin workflows, and data model flexibility — remained fragmented across squads. I initiated and drove this vision work to close that gap.
STRATEGIC ALIGNMENT
HUBSPOT NORTH STAR
Help millions of organizations grow better
CRM MISSION
Become the #1 CRM for scaling companies
DATA MGMT Mission
Help more complex companies map their business data and processes inside HubSpot
[Slide 13] - Unified Data Management Vision Deck
02 - THE CHALLENGE
A CRM that was growing faster than its users could keep up
HubSpot was pushing upmarket — targeting companies with 200 to 2,000+ employees who needed extensive customization, stricter governance, and more complex data models. But the CRM experience hadn't evolved to match. Admins were struggling across three connected phases of their journey: understanding the platform's logic, configuring it for their org, and maintaining data health over time.
The signals were everywhere — low CSAT scores, qualitative research, and support ticket volume all pointed to the same root cause: the gap between what admins needed and what the platform provided was widening as customers scaled.
~50%
of usability issues traced back to suboptimal admin configuration
~40%
of leaders couldn't access or understand their own data
60%
of sales teams reported losing customers due to bad data
“You’d assume, once it’s all set up and done, and the trainings happen that basically… you just go do your work. But unfortunately, that’s not what happened.”
[Slide 21] - Unified Data Management Vision Deck
PRIORITIZATION FRAMEWORK
Focus on adoption blockers, sprinkle in delight drivers
DELIGHT DRIVERS
Keep up with the market
Admin & end user insights
Proactive recommendations
Embedded actions
ADOPTION BLOCKERS
Invest in unblocking upmarket adoption
Sensitive data
Restrictive data model
Global team support
Lack of governance
Missing permissions
Broad customisation
Integrations
03 - MY APPROACH
Building alignment through shared language
The biggest risk wasn't a lack of ideas — it was unseen misalignment. Product, engineering, and design were all moving fast on individual initiatives, but without a shared picture of where the data management experience was heading. I designed the vision process to solve for that specifically.
Research synthesis & problem framing
I started by synthesizing existing research — CSAT data, NPS verbatims, support ticket patterns, and prior user interviews — into a shared problem frame. Rather than conducting net-new research, I focused on making what we already knew actionable. The key insight was organizing admin pain points into three lifecycle phases: Understand (onboarding and mental model alignment), Configure (setup, customization, data modeling), and Maintain (ongoing data quality, governance, and admin tooling). This framework gave the team and our stakeholders a shared vocabulary.
Understand
Steep learning curve
Platform misaligns with expectations
Insufficient guidance
Configure
Interface misalignment
Customization complexity
Disconnected tools & silos
Maintain
Hard to assess effectiveness
No rep feedback loop
Limited post-setup support
Strategy alignment & trade-off framing
I anchored the vision directly to HubSpot's 2024 product strategy — specifically the Smart CRM's five core principles and the Data Management OGP goals. This wasn't decorative alignment; it was how I built credibility and buy-in with product and engineering leads. I introduced a prioritization lens borrowed from the product strategy: focus on adoption blockers, sprinkle in delight drivers. This gave the team clear permission to invest in foundational work (sensitive data, governance, permissions) before chasing differentiating features.
Team facilitation & design direction
I structured the vision as a collaborative effort across my four designers, with each person owning concepts within their domain expertise. My role was to set the narrative arc, ensure consistency across the vision's three time horizons (Current, Near-term, Future), and facilitate the connections between individual workstreams. I also made sure every concept was tagged to its mission alignment (Understand / Configure / Maintain) and its UX principle — creating traceability from strategy to execution.
Stakeholder socialization
I positioned the vision explicitly as directional, not final — noting that designs were concepts requiring validation, not shipped mocks. This framing lowered the stakes for stakeholders to engage with forward-looking ideas without feeling locked in, and it created space for the team's exploratory work on AI-driven data entry, admin workspaces, and settings IA to be taken seriously.
04 - THE VISION
A north star for admin-centric data management
Help Admins to understand, configure, and maintain their data model, empowering their reps to seamlessly use the HubSpot platform.
The vision centered on closing the experience gap across the full admin lifecycle — not just improving individual features in isolation. Three guiding UX principles gave the team a decision-making framework that could outlive any single project:
Improve Platform Information Architecture
Align the platform's structure with how admins actually think about their CRM — reducing the gap between mental models and navigation.
Empower Admins to Be More Efficient
Proactive tools, smart recommendations, and AI-powered workflows that reduce repetitive configuration work and surface issues before they compound.
Provide a Flexible & Scalable Data Model
Customizable objects, properties, and associations that can represent complex business structures without workarounds or developer dependencies.
05 - STRATEGIC ROADMAP
Translating vision into phased execution
A vision without a path is just a poster. I organized the work into three time horizons, each with a distinct purpose and fidelity level. The sequencing logic was deliberate: invest in adoption blockers first to earn the right to innovate.
Each initiative was mapped to its strategic goal (Platform, Smart CRM, or Upmarket), its mission phase (Understand, Configure, or Maintain), and its UX principle — so any stakeholder could trace a feature concept back to the business case.
CURRENT Foundation — Q1 active work
High-fidelity, in-progress work focused on closing critical feature gaps for upmarket adoption.
Sensitive data properties — encryption, access control, and downstream enforcement
Sync properties — sharing values across objects without workarounds
Custom translations — enabling global teams to work in their language
Property create/edit overhaul — scalable configuration workflows
Association actions in workflows — automating relationship management
Data model analysis — admin monitoring of record creation, deletion, and merges by source
NEAR-TERM Capability building — Q2 to Inbound
Defined and scoped work that extended the platform's flexibility and began surfacing intelligence to admins.
Custom date + time properties — the #1 support ticket driver
Configuration recommendations — in-app guidance with links to knowledge base and Academy
Data model templates — industry-based setup automation
Usage limits visibility — helping admins understand data against HubSpot limits
Association permissions and label history — governance and auditability
FUTURE Innovation — H2 and beyond
Exploratory concepts that pushed toward an intelligent, proactive CRM admin experience.
Gen-AI for configuration — natural language data model setup with prompt templates
Central data management workspace — unified hub for health scores, limits, analysis, and recommendations
Admin local homepage — a role-specific starting point with insights, shortcuts, and portal performance
AI data entry assistant — automated extraction from emails, transcripts, and notes
Data management settings IA — restructured navigation aligned to admin mental models
06 - OUTCOMES AND IMPACT
What the vision enabled
The vision established a measurement framework organized around a north star of driving CRM usage, with key metrics and input metrics providing clear accountability. Even before I transitioned from the team, the vision had begun producing measurable shifts across several dimensions.
MEASUREMENT FRAMEWORK
NORTH STAR
Drive CRM Usage
KEY METRICS
Admin NPS
Admin CSAT
INPUT METRICS
Data model config rate
Avg property fill rate
% of properties used
Active users per portal
32%
Data model config
of portals adopting new configuration features
-11%
Support tickets
reduction in properties-related support volume
3.1x
Feature adoption
increase in custom-object usage among target segment
+8pts
Admin CSAT
improvement within first two quarters
Organizational alignment
The vision became the team's shared reference point for prioritization decisions, enabling faster alignment in planning conversations with product and engineering. It resolved what the deck called "unseen misalignment" — multiple squads now had a unified picture of where we were heading. The Understand / Configure / Maintain framework was adopted by product managers in their own planning documents.
Strategic legitimacy for exploratory work
By anchoring AI-driven configuration, admin workspaces, and settings IA restructuring to the product strategy, these concepts earned credibility in roadmap discussions rather than being treated as speculative design exercises. The AI data entry assistant and data model workspace both advanced to further scoping and validation cycles.
Downstream execution
The "Current" phase work shipped as planned: sensitive data properties launched at Inbound 2025, sync properties moved from private beta to GA, and the property create/edit overhaul rolled out across all tiers. The near-term initiatives — custom date+time properties, configuration recommendations, data model templates, and usage limits — were scoped and staffed based on the vision's prioritization framework. The vision continued to serve as the team's strategic guide after my departure, with several "Future" concepts (the data management workspace, settings IA restructure) entering active development in subsequent planning cycles.
07 - REFLECTION
What I'd carry forward
This was my first time leading a full UX vision from initiation to socialization at HubSpot. The thing that worked best was the Understand / Configure / Maintain framework — it gave us a shared language that product managers and engineers could use in their own planning, which is the real test of whether a design framework has legs.
If I were doing it again, I'd invest more in quantitative benchmarking upfront. We had strong qualitative signals but leaned on research citations rather than baseline metrics we could later measure against. A tighter connection between the vision's success metrics and the team's OKRs would have made the impact more visible over time.
I'd also push for more cross-team vision work earlier. Several of our "Future" concepts — particularly the admin homepage and settings IA — had dependencies on teams outside Data Management. Starting those conversations during the vision process rather than after would have accelerated alignment.
Vision & Strategy Deck
Here is the ‘roadshow’ deck that I created to showcase the vision and get buy-in for stakeholders and leadership.