DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
Securing Your Software Supply Chain with JFrog and Azure
Register Today

Trending

  • Grow Your Skills With Low-Code Automation Tools
  • Revolutionize JSON Parsing in Java With Manifold
  • Navigating Digital Assurance With a Scrum Master: Maximizing Quality in Agile Projects
  • What Is Plagiarism? How to Avoid It and Cite Sources

Trending

  • Grow Your Skills With Low-Code Automation Tools
  • Revolutionize JSON Parsing in Java With Manifold
  • Navigating Digital Assurance With a Scrum Master: Maximizing Quality in Agile Projects
  • What Is Plagiarism? How to Avoid It and Cite Sources
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. 6 Tips for Designing a Roadmap to Connect Your Marketing Apps

6 Tips for Designing a Roadmap to Connect Your Marketing Apps

How is the methodology for prioritizing marketing integrations like refining a menu for an established restaurant? Read on for the answer.

Ross Garrett user avatar by
Ross Garrett
·
Dec. 01, 16 · Opinion
Like (1)
Save
Tweet
Share
2.42K Views

Join the DZone community and get the full member experience.

Join For Free

the methodology for prioritizing marketing integrations is like refining a menu for an established restaurant. at the foundation, you must understand what drives customer loyalty and improve upon it, all while attracting new customers. without a thoughtful plan, you’ll wind up adding sushi, hamburgers, and fried chicken to the menu.

today, marketers are expecting applications to work in sync to automate once error-prone manual tasks. if your application is powering these automations, your churn rate will likely decrease. thus, your goal is to identify what integrations are crucial to your customers’ workflows to increase functionality and stickiness.

integration roadmap

this thoughtful plan, an integration roadmap analysis, starts with the customer, external inquiry, and ends with a cross-departmental collaboration, internal inquiry. below are six steps to enhance the decision-making process.

1. get to know your customers and potential users

of course, every new feature starts with the customer; but do you really know what your customers need? start by considering common marketing integration use cases by breaking down the customer into three life cycles: past, present, and future. here are a few examples:

  1. past: use customer data to understand customer behaviors and to determine successful marketing funnel programs.
  2. present: automatically enroll new contacts to drip marketing campaigns from multiple sources.
  3. future: notify sales teams of potential opportunities based on subscriber behavior.

secondly, tap your present customers for insight. use a multi-touch approach to gain an accurate representation of their needs and interests. begin by creating a standardized process for collecting and rating feedback. next, consider the customer touch points you can employ to gain the intelligence needed to prioritize integrations. here are some possible feedback touchpoints:

  1. enlist your account executives to speak with your top customers.
  2. include customer questions at the end of customer support calls.
  3. employ the business development teams to document what features, competitor product gaps, and use cases prospects are mentioning.
  4. consider adding an exit survey. this is a great way to build understanding about what workflows and features are missing, resulting in churn.

2. research the competition

one huge bonus of offering pre-built integrations is staying ahead in today’s competitive landscape. consider what companies are leading the way in integrations and extract best practices.

ask yourself the following questions:

  • what integrations are your competitors offering to their customers?
  • can you glean information about their roadmap from their blog and product feature subpages?
  • if they’re offering integrations, can you identify gaps in their catalog?
  • how are competitors currently offering integrations (marketplace, add-on, free)?

3. brainstorm with those on the frontline

new product integrations should never be validated in a silo. once you have gathered a sizeable amount of customer feedback, collaborate with every department to paint an accurate picture of your users’ needs. identify common themes to avoid the mistake of creating an integration for a sole customer.

4. understand internal and external bandwidth

developing new product features impact every department, from marketing to devops. fully vet the time needed to skillfully execute an integration strategy.

5. crunch the numbers

a true cost-analysis requires more than recognizing the immediate cost of a build. essentially, implementing new integrations entails four degrees of costs and each demand time from nearly every department:

  1. the cost of building and continuously testing functionality.
  2. the cost of maintaining and adapting to changing apis.
  3. the cost of marketing the new integrations to ensure usage.
  4. the cost of product support.

6. determining the integration strategy

once you’ve run through the analysis phase, there are a few directions you can take to implement an integration strategy.

  1. build your integration marketplace gradually by implementing connections to a few identified elements that are crucial to keeping your customers happy.
  2. power your go-to-market strategy by implementing connections to key elements that can round-out your product.
  3. gain the competitive advantage by implementing a suite of connections that will give your customers a robust, sticky user experience.

want more? we asked two product experts for their take on the top takeaways every product manager should know about marketing integrations. check out our guide with their top seven tips here !

Integration

Published at DZone with permission of Ross Garrett, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Trending

  • Grow Your Skills With Low-Code Automation Tools
  • Revolutionize JSON Parsing in Java With Manifold
  • Navigating Digital Assurance With a Scrum Master: Maximizing Quality in Agile Projects
  • What Is Plagiarism? How to Avoid It and Cite Sources

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com

Let's be friends: