Content Mapping Template

Hi, Steve from Ludi here.

Just wanted to give you a little bit of context about the content mapping template and also a quick overview of how to work through it with your team.

So this template came about when we were looking at building a, host of new landing pages for our marketing site.

And I was at the time just working through the role based pages.

So we have these solution pages for each role type who might use Ludie.

So Scrum masters, engineers, delivery managers, product owners, et cetera.

And while working through this list, this pattern sort of organically developed of assigning the jobs to be done because that's the framework that we wanted to use, and then going, okay, so if this is a job to be done, what would be the most pertinent bit of information to share with them?

Templates are a big part of our product.

So the first thing to do was to align templates to specific role types.

And you can see here, if I go into the time machine, which will play back how the board was created, you can see how it just sort of slowly evolved.

It started with me going, these are the roles we want to focus on.

And then I started writing a few, bits of information about each one and then going, okay, this template aligns with that person, this template aligns with that person, et cetera, et cetera.

And I went through this process and eventually just sort of formed, formed the basis for what that core content is going to be for each of these pages.

Obviously there's more to a landing page than just showing the templates, but this was specifically around mapping our product and product features to role types.

And then from that we thought this could be a good workflow or process to share with our customers who might be facing the same challenges as what content do I share from my product with the sort of ICPs or roles who might be coming to look at my marketing site to make a purchase decision.

So if we go back to the template, I'll give you a overview of how we see it working and hopefully how your team can use it.

The first thing you'll notice is this section here.

This is literally just an example of what we put in ours.

Delete this.

You don't need it.

It was some context for the first time you opened this template.

Otherwise you would just see a bunch of empty boxes.

And this shows the issue that we were trying to solve or the challenge that we were trying to solve.

It outlines what we identified as the jobs to be done of a Scrum master.

And then the templates from our product that might best suit them.

So the idea here is that you come and you go, okay, what is my page focus?

Yours might be role based landing pages, they might be feature based landing pages.

You just have to think about what is the purpose or what is the job to be done either by my page or the person who's viewing my page and then how do I reply to that Jobs to be done challenge with some content about my product or feature, which makes sense.

And I would say delete these because they are just to give you an idea of the left, right, split and then start adding your sticky notes of this is the challenge or the job to be done and this is our response to it.

and then just work through the process like that.

There's four here to start with.

Obviously it'll be as few or as many as you need for your specific use case, but the idea here is you go through that, you get a high level overview.

it's to help you make sure that you're not being too repetitive.

So for us, we didn't want a delivery manager and a Scrum manager to or Scrum Master to come to our website and go between pages and see the exact same content.

We wanted to make it feel like an individual experience to the challenges of that particular specific role type faces in their job and how Ludi can help to solve those challenges.

And then the last part of this template is very simply an area to place some actions.

So say we've worked through this, we've identified some content gaps, or we've identified some areas that we want to research further.

Come here, make a sticky note for it, turn it into an action, assign it to the person who might want to work on that.

I'll give this one to Jamie.

He's got three days to do it and now we have a trackable action.

He would have been notified about this and we can see it in our actions dashboard.

So, yeah, I hope you find this helpful.

It's a very lightweight template, but for us it really helped us give a high level overview of where we needed more content, where we were repeating ourselves too much and allowed us to work through each page that we wanted to create so we could clearly see the workload that we had ahead of us.

hope you enjoyed.

Cheers.