I couldn't tell from your question whether you already have a good product:persona written down. If not, that's the first thing you want to do, before even thinking about how to visually represent it.
I usually think about personas using the methodology laid out in this answer– basically, what problems do your users have, and how does your product solve those problems differently for each user type? Goals/needs/problems are the main piece, but you also want to think about thinking style, technical ability, etc. T
Once that's sorted out, I'd start by just adding the applicable persona(s) as a spreadsheet column, piece of wiki metadata, or something else you can pivot on or look up later.
How you actually visualize or share those mappings will vary based on your audience.
If the goal is to simply visually represent the persona / product relationship, I'd attack it from two ends:
- On your Persona profile page, show or list the products they use, and
- On the internal page for your product, show or list the personas that use it.
At the end of the day, this (or any persona-based exercise) is useless if nobody actually uses it, and ensuring that internal stakeholders see the relationship on both the product and the persona will help with that.
The below mockup is not a suggestion about how you should lay out or structure your persona page, but an example of how to show a product relationship on a persona. You could visually show product logos (1) somewhere on the page, and I'd also also recommend (2) making sure there's a clear mapping between the persona, the problems they're trying to solve, and which product solves them. A nice bonus is how frequently they use that product, and how well it solves their problems.
On the product side of things, I'll assume you have some kind of wiki page or internal representation of the product. There, I'd go through a similar process, making sure the faces of the relevant personas are visible somewhere (and linked to the personas as well). Additionally, if you have your product mapped to specific user stories or use cases, you can indicate the relevant persona with each use case. For example:
- "Lucy uses the email-o-matic daily to organize her hectic email inbox, because she gets hundreds of messages a day and can't organize them manually."
- "Fred uses the email-o-matic weekly, because he often forgets about important emails and the tool helps remind him about them."
I'd obviously adjust this to however your organization lists the use case / user story / jobs to be done for a particular product, but the main takeaway is that whenever you're internally describing what a product does, everybody should know who uses it for that, and why.