Sign up to save your podcasts
Or
Share Tips for New or Simply Worn Out Partner Ops Hires
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Tips for New or Simply Worn Out Partner Ops Hires
Send us a text
Day 4️⃣ New #PartnerOps Hires - Tips for Success
If you're new to #PartnerOps or just feeling a bit lost in your current role you might benefit from a few tips on getting started that can also help an established role get re-centered in an off season.
✅ Map the Partnership Processes. Go find every process tied to Partnership, write it all down, get it reviewed, and collect it into a single SOP to build from.
✅ Map the Relationships. Sign up for Lucid or another charting tool and start mapping all the people that are in any way connected to Partnerships. This helps you keep up with names/roles but also clearly demonstrates the company-wide culture of Partnerships.
✅ Map the Data. Part of process mapping will be figuring out the data model, during which time you can build out some basic reporting to check for quality issues like "Do we know how many partners are in X program?" or "Do we have a definitive list of Partner Contacts for event marketing?" Find all the gaps in process and data quality that need filled up.
✅ Map the Technology (are you seeing a trend here?). How does the tech stack support or, more likely, not support the larger partner ecosystem? Do they have a PRM? Do they offer SSO for partners? What's the LMS for enablement? How are they managing integration projects? What are they using for contracting? Just ask questions - every process likely has or needs supporting technology. Write. It. Down.
✅ Find the Reports. Pretty straightforward - find them, bookmark them, figure out how they are made, look for innovation.
✅ Ask about program prioritization. Which program matters most to the org, and why, so you can properly set your own agenda and work effort. Something will eventually have to give and you shouldn't have to make that call on your own.
✅ Setup Recurring Meetings. Program leads will appreciate regular touchpoints to share grievances an ideas. Start with bi-weekly half-hour sessions if the schedule affords it and then shift to monthly once the meetings close out in less than 15 minutes. Ask all the questions you think of throughout the week in this space to help drive the agenda. Listen listen listen.
✅ Define the process for change. If you want to drive change you'll need to know the who and how behind it. Do they have a well established framework for requests tied to CRM updates, data changes, etc? Do you do that work or do you write up requirements? If not you, who does and where do you send it? You may find they don't have anything like this, super flexible org, etc. so be prepared to offers ideas. IT/Systems will need to be your best friend here.
Looking for a place to connect with other experts in #partnerships? Then join Partnership Leaders , the home for the home for everyone in partnerships!
Aaron Howerton
www.linkedin.com/in/aaronhowerton
www.partneropspartner.com
View all episodes
By Aaron HowertonSend us a text
Day 4️⃣ New #PartnerOps Hires - Tips for Success
If you're new to #PartnerOps or just feeling a bit lost in your current role you might benefit from a few tips on getting started that can also help an established role get re-centered in an off season.
✅ Map the Partnership Processes. Go find every process tied to Partnership, write it all down, get it reviewed, and collect it into a single SOP to build from.
✅ Map the Relationships. Sign up for Lucid or another charting tool and start mapping all the people that are in any way connected to Partnerships. This helps you keep up with names/roles but also clearly demonstrates the company-wide culture of Partnerships.
✅ Map the Data. Part of process mapping will be figuring out the data model, during which time you can build out some basic reporting to check for quality issues like "Do we know how many partners are in X program?" or "Do we have a definitive list of Partner Contacts for event marketing?" Find all the gaps in process and data quality that need filled up.
✅ Map the Technology (are you seeing a trend here?). How does the tech stack support or, more likely, not support the larger partner ecosystem? Do they have a PRM? Do they offer SSO for partners? What's the LMS for enablement? How are they managing integration projects? What are they using for contracting? Just ask questions - every process likely has or needs supporting technology. Write. It. Down.
✅ Find the Reports. Pretty straightforward - find them, bookmark them, figure out how they are made, look for innovation.
✅ Ask about program prioritization. Which program matters most to the org, and why, so you can properly set your own agenda and work effort. Something will eventually have to give and you shouldn't have to make that call on your own.
✅ Setup Recurring Meetings. Program leads will appreciate regular touchpoints to share grievances an ideas. Start with bi-weekly half-hour sessions if the schedule affords it and then shift to monthly once the meetings close out in less than 15 minutes. Ask all the questions you think of throughout the week in this space to help drive the agenda. Listen listen listen.
✅ Define the process for change. If you want to drive change you'll need to know the who and how behind it. Do they have a well established framework for requests tied to CRM updates, data changes, etc? Do you do that work or do you write up requirements? If not you, who does and where do you send it? You may find they don't have anything like this, super flexible org, etc. so be prepared to offers ideas. IT/Systems will need to be your best friend here.
Looking for a place to connect with other experts in #partnerships? Then join Partnership Leaders , the home for the home for everyone in partnerships!
Aaron Howerton
www.linkedin.com/in/aaronhowerton
www.partneropspartner.com