How to Use the MessageWorks Positioning Intelligence Hub as Your Single Source of Truth

Direct Answer

The Positioning Intelligence Hub in MessageWorks is the central system where your official positioning and messaging live—across organization, segment, and persona levels. It lets go-to-market (GTM) leaders govern messaging through versioning and manual promotion, so downstream work always pulls from one approved source. The outcome: fewer debates, less drift, and consistent narratives across launches and campaigns.

What This Feature Does

Inputs

• Manually authored positioning inside the hub
  
  
• Outputs exported from Positioning Discovery (creates a new hub version)
  
  
• Outputs created via QuickStart (also creates a new hub version)
  
  

Core Objects & Hierarchy

• Positioning Intelligence Hub (top-level container)
  
  
  • Organization-level positioning
    
    
  • Final positioning
    
    
  • Core jobs to be done (JTBDs)
    
    
  • Capabilities
    
    
  • Value pillars
    
    
  • Category options
    
    
  • Segments (2–5 per hub)
    
    
    • Name
      
      
    • Description
      
      
    • Segment messaging
      
      
    • Use cases
      
      
    • Value propositions
      
      
    • Buyer groups
      
      
    • Personas (2–5 per segment)
      
      
      • Role and type
        
        
      • Core narrative
        
        
      • Relevant solutions
        
        
      • Goals & KPIs
        
        
      • Jobs to be done
        
        
      • Struggling moments
        
        
      • Pain points
        
        
      • Emotional drivers
        
        
      • Social drivers
        
        
      • Value propositions
        
        
      • Preferred channels
        
        

Key Behaviors

• New hub versions are created via Discovery export, QuickStart, or grouped manual edits
  
  
• Versions are not live by default
  
  
• Manual promotion is required for a version to become production
  
  
• Downstream features always read from the currently promoted version
  
  

When to Use It

As the foundation of your MessageWorks workspace
When you’re setting up MessageWorks and need to define, in one place, the organization-, segment-, and persona-level positioning that the rest of the platform will rely on. Positioning Discovery is how you intentionally populate the Positioning Intelligence Hub before any downstream features are used.

Before using any downstream capabilities
When you want content generation, content testing, and synthetic focus groups to operate from a clear, approved positioning system instead of partial or improvised inputs. Discovery ensures the Hub is complete and coherent before it feeds the rest of the app.

When establishing a single source of truth for messaging
When messaging is scattered across decks, docs, and people’s heads and you need a structured workflow to turn that fragmentation into a governed system that teams can trust and reuse.

When leadership wants to explore or implement a new positioning direction
When management is considering a materially different narrative, category framing, or segment focus, you need a safe way to build and review a new positioning system without disrupting what’s currently live.

Whenever the Hub needs a deliberate refresh
When product strategy, target segments, or competitive alternatives have changed enough that incremental copy edits aren’t sufficient—and the Hub needs to be updated intentionally so downstream content stays aligned by default.

Prerequisites

• An organization exists in MessageWorks
  
  
  • Created by an account admin during onboarding
    
    
  • One hub is created per organization and inherits its name and domain
    
    
• Proper permissions
  
  
  • Org admins assign users to groups with read/write access
    
    
  • Only users with write access can complete Discovery workflows
    
    
• A promoted hub version is required for downstream workflows to reflect updates
  
  

Step-by-Step Workflow

1. Confirm your organization and hub exist

• Action: Ensure the organization has been created by the account admin
  
  
• Result: A Positioning Intelligence Hub exists for the org
  
  
• Notes: This is the very first step an account admin needs to take after the account is provisioned.

2) Choose how you will build out your hub (org, segment, and persona levels)

• Action: Select one of the following approaches to populate the hub. Each approach fills in the same underlying hub structure (organization-level positioning, segments, and personas):
  
  
  • QuickStart – ~3 minutes, fully automated
    
    
  • Positioning Discovery workflow – ~1–3 hours, AI-assisted
    
    
  • Manual build – direct editing of hub sections
    
    
• Expected result: Your hub is populated with organization-level positioning plus segment and persona narratives.
  ‍
  

3) Review and refine the populated hub structure

• Action: Review the populated sections across all levels:
  
  
  • Organization-level positioning (final positioning, JTBDs, capabilities, value pillars, category options)
    
    
  • Segments (2–5 per hub)
    
    
  • Personas (2–5 per segment)
    
    
• Expected result: A complete, structured positioning system covering who you serve, what you offer, and why it matters.
  
  

4) Create a new hub version from your changes

• Action:
  
  
  • Click Edit (top right) to enable editing.
    
    
  • Make one or more changes across any hub sections.
    
    
  • Click Save (top right).
    
    
  • Add a version label and summary.
    
    
  • Click Save new version.
    
    
• Expected result: A new hub version is created and stored in version history.
  
  
• Notes/constraints: Discovery exports and QuickStart outputs also create new versions automatically; none overwrite the production version.
  
  

5) Review versions and align with stakeholders

• Action: Share the newly created hub version with leadership or key stakeholders for review.
  
  
• Expected result: Agreement on which version represents the intended positioning.
  
  

6) Promote the approved version

• Action: Manually promote the selected hub version.
  
  
• Expected result: The promoted version becomes the production/live hub version.
  
  
• Notes/constraints: Downstream features only read from the promoted version.
  
  

7) Generate content from the promoted hub (optional)

• Action:
  
  • Go to Content → Lab.
    
    
  • Choose a content type (Blog, LinkedIn post, Web copy, Email).
    
    
  • Select a target audience (Entire Hub, Full Segment, or Single Persona).
    
    
  • Provide additional instructions and guidance for the AI, as prompted in the UI
    
    
• Expected result: Content is generated using the currently promoted hub version.
  
  
• Notes/constraints: The system automatically pulls relevant narratives, JTBDs, value pillars, proof points, pain points, KPIs, and emotional/social drivers - and much more - from the hub.
  
  

‍

Example Walkthrough

A VP of Product Marketing prepares for a multi-product launch:

1. Confirms the organization and hub exist
   
   
2. Runs Positioning Discovery and exports results
   
   
3. Refines organization-level positioning manually
   
   
4. Saves edits as a new version
   
   
5. Gets leadership sign-off
   
   
6. Promotes the approved version
   
   
7. Demand gen generates emails from Content → Lab
   
   
8. High-stakes landing page is tested against hub via Content Validation against Hub (future capability)

Outcome: one narrative, reused everywhere, without firefighting.

Troubleshooting

Content doesn’t reflect recent changes
→ Likely cause: new version not promoted
→ Fix: promote the version and regenerate content

User can’t export complete or export Discovery workflow
→ Likely cause: no write access
→ Fix: admin assigns write permissions

Stakeholders reviewing different narratives
→ Likely cause: multiple versions exist
→ Fix: ensure all parties are working off the same version, and understand which is production

Unclear where to store messaging
→ Likely cause: hierarchy confusion
→ Fix: map content to org → segment → persona

FAQ

1) What is the Positioning Intelligence Hub?
The Positioning Intelligence Hub is the system where your official positioning lives, structured and governed across organization, segment, and persona levels.

2) How is the Positioning Intelligence Hub created?
It’s created automatically when an organization is provisioned during onboarding and inherits the organization’s name and domain.

3) What types of positioning information live inside the hub?
The hub contains organization-level positioning, value pillars, JTBDs, capabilities, category options, plus structured segment and persona narratives.

4) How do I create a new version of my positioning?
You can create a new version by exporting outputs from Positioning Discovery, using QuickStart, or saving a set of manual edits together as a new version.

5) Does exporting from Positioning Discovery overwrite what’s live?
No. Discovery exports always create a new hub version and never overwrite the currently promoted version.

6) What does it mean to “promote” a hub version?
Promotion makes a specific hub version the production version that downstream features read from.

7) What happens if I update the hub but forget to promote the new version?
Downstream workflows will continue using the previously promoted version, which can make it appear like changes didn’t take effect.

8) How does the hub influence content generation?
When generating content, MessageWorks automatically pulls narratives, value props, JTBDs, proof points, and drivers from the currently promoted hub version.

9) Can I compare or roll back positioning changes over time?
Yes. Multiple hub versions can exist in parallel, and full version history is always available for review or rollback.

10) What’s the difference between testing content and governing positioning in the hub?
The hub defines and governs what your official positioning is, while content testing evaluates how a specific asset is likely to perform with a chosen audience before it goes live.