Use this three-step process to create your user stories.
1. Identify Your Audience by creating User Personas
Think about all the different types of people who use your app. To understand what integrations and configurations are needed, you should identify all the key users of your product.
For example, a CRM (Customer Relationship Management) system is used by marketers, salespeople, business developers, and developers. An Applicant Tracking System is used by recruiters, HR executives, hiring managers, and benefits administrators.
Your product and marketing teams have likely already created user personas, which describe the different types of users. So, talk to them and ask for their insights.
Also, collaborate with your tech partners to find out if they have any additional user personas to contribute. This will give you a clear picture of who your app serves and what they need.
2. Write the Use Stories
Once you know who your users are, write down what integrations they need and why they need them. Work together with product, sales, customer success, and product marketing teams to create these user stories, treating them like new product features.
Keep in mind that these stories may change based on feedback from customers after they're launched.
Start by writing high-level stories using the format "As a [role], I need to [task] to accomplish [goal]."
3. Define Your Master Acceptance Criteria
The final step is to define acceptance criteria for each user story. This describes what users need to do in order to achieve their goals.
For example, When using a CRM and an email marketing platform together, it's essential to keep contact segments synchronized and track email performance within the CRM. To achieve this they system must:
Regularly sync contacts
Sync audience segments
Log emails sent from the marketing platform in the CRM
Capturing reporting metrics at the audience level
Also consider any API limitations that may affect the integration, including those with your partners.
Here are elements to consider when drafting acceptance criteria:
Timing: Assess whether real-time data syncing is necessary for critical notifications, or if daily syncs are sufficient for certain tasks like moving invoices.
Data Volume: Take into account any limitations on data transfer capacity within specific timeframes as defined by the APIs.
Field Mapping: Review the field structures and relationships in both systems to ensure smooth information transfer. Account for any variations such as different field structures for names or variations in handling groups or enrollment.
User Experience: Prioritize a seamless and practical experience for users by incorporating user-friendly features for setup, updates, syncing, usage monitoring, troubleshooting, and disconnection.
After defining your user personas, stories, and acceptance criteria, collaborate closely with the engineering team to align the integration design with as many criteria as possible. You can refer to a sample integration user story and acceptance criteria by downloading it here.