Greg Dunlap: Designing Content Authoring Experiences – Episode 210
from Content Strategy Insights
Greg Dunlap Experience design for readers of online content gets a lot of attention. The authors who create the content and get it ready for publication aren't as well served. In his new book, Designing Content Authoring Experiences, Greg Dunlap addresses this situation, showing content-system creators how to design better interfaces, streamline workflows, and otherwise improve the lives of content authors and managers. We talked about: his 20-year history as a CMS expert and the launch of his new book, "Designing Content Authoring Experiences" the huge gap between the needs of CMS authors and the attention paid to them in CMSs and their implementation how he includes content author needs in his content strategy and CMS implementation processes and workflows the organizational dynamics that typically lead to the lack of consideration for author needs how a good authoring experience supports any number of business goals: better SEO, more efficient operations, better content, better content discoverability, etc. how to balance conflicting needs for structure and flexibility in content operations the importance of understanding and accounting for the differences between content creation and content publication possible issues that can arise from using collaborative authoring functions in CMS workflows the ever-evolving of authoring tools and practices in decoupled architectures the hazards of using page builders in content authoring how he tries to keep structured content top of mind in organizations some of the criteria he uses when evaluating content authoring projects: the org's content maturity, its size, the technical skills of the system users, etc. Greg's bio Greg Dunlap got started in content management in the early 2000s, building custom systems for small clients. In 2006 at the Seattle Times Company, Greg got involved in the Drupal community, eventually leading one of the eight core initiatives for Drupal 8. Since then he has focused on building large-scale publishing systems for clients around the world. Greg makes his home in rural Washington with his wife Nicole and a small menagerie of animal friends. In his spare time, Greg is an internationally ranked pinball player and loud-music concert goer. Connect with Greg online LinkedIn Bluesky Resources mentioned in this episode AuthoringExperience.com Authors are also users - a new book on designing content authoring experiences (review) Video Here’s the video version of our conversation: https://youtu.be/aX2S8KT0Mv8 Podcast intro transcript This is the Content Strategy Insights podcast, episode number 210. Five years ago at the Confab content strategy conference a speaker asked the audience of seven hundred to raise their hand if they loved their content management system. One hand went up. Greg Dunlap was the only person in the room with close ties to the CMS world. The other six hundred and ninety-nine were professionals routinely forced to use content systems that had failed to consider their needs. Greg's new book, Designing Content Authoring Experiences, aims to fix that oversight. Interview transcript Larry: Hi everyone. Welcome to episode number 210 of the Content Strategy Insights podcast. I'm really delighted today to welcome back to the show, Greg Dunlap. He was on, I can't even remember how many episodes ago talking about this same subject, but we're going to get deeper into it today. Greg is currently the director of content strategy at Bixal, a consultancy/agency, and he's also the author and the reason he's here today of the new book, Designing Content Authoring Experiences. So welcome Greg. Tell the folks a little bit more about what you're up to these days. Greg: Thanks, Larry. As you said, I'm a Director of Content Strategy at Bixal. We are a consulting company that focuses on work in the federal government space. I've been bouncing around in the CMS world for the last 15, 20 years, and one of the things that's been something that's interested me since I got started was not just the experience of the people who use the website on the front end that we work for, but the people who are doing the authoring experience on the back end. Greg: This started for me when I was working at The Seattle Times and we did a big CMS rollout and one of the people in the editorial team came to me and said, "Where is this piece of functionality that we used to have and we don't have anymore?" I realized that the reason why we didn't have it anymore is because nobody had ever asked the people who use the CMS every day what they do with it. We had done this gigantic rollout with everybody involved except for them, and it set a light bulb off in my head about how these people are often marginalized in the CMS development process. Nobody thinks about them. We can just dump our product on their plate and they can just use it without any consulting. That sparked this whole idea in my head, and it's something that I've been bringing into my work a lot for the last 10 years and eventually led to this book being written. Larry: You're reminding me. I think I met you about a year or so before this, but at the Confab, I think it was in 2020 [actually 2019]. Laura, what's her last name [Laura Robertson] from England, did that great talk. Greg: Yes. Larry: She asked, and this is etched in my memory, a room full of 700 people, and I'm sitting over to one side and she asked, "Hey, who in this room loves their CMS?" I look around, one person stood up and it was you because everybody else... Greg: I tell that story in the beginning of the book. Larry: Oh, good. Because that's the best story ever, but it also speaks to that was a room full of the people you were just talking about. Greg: Yeah, exactly. Larry: The people who were forced to use these systems. The need was clear for something like this. The other thing you say early in the book is that this is a lot of work. This isn't just tidying up some stuff. This is a whole parallel project to, you think you're building a website, but you're really building, you need to build along with it, this authoring system. How big is that disconnect among orgs getting that? Greg: I think it's incredibly large. I mean, because the book is basically outlines the process for properly designing for your content authors and treating them as users just as much as you treat the people who use your website as users. If you're going to treat them that way, then you go through the same process. You have to research them to learn about their use cases, you prototype potential solutions with them, and then you implement and test those solutions and support them over time. Greg: That very much parallels the different process that you go through when you're designing an actual front end for a website. It involves all of the same skill sets. It involves designers, it involves engineers, it involves content strategists, it involves executive stakeholders, and it really is like a parallel web development process. In most projects, it is very far from a parallel web development process. Greg: I think that a lot of that just comes down to this idea that these content people are just at the bottom of the chain of command at any given organization and that people view them as just like word pumpers. We see this all the time at organizations where people are like, oh, this person knows something about a topic. They can write the content for the website or whatever. I'm not the only person who have talked about that on your podcast for sure. Greg: This view that anybody can write, anybody can do this work, and so there's no specialization, there's no needs for it that need to be catered to. Part of me telling this story is just to say that that's not true. That if you do this work, you will make better content and you will get better ROI on the system that you've spent a lot of money building. I think that's a really important message to get out. Larry: We didn't plan it this way, but the episode right before this one, I don't know if you've listened to it yet, it just came out, was with Sarah Johnson who just wrote a book called Content-first Design. Starting with the content and a lot of parallel issues. I think this is going to be an interesting pairing in the sequence here. Larry: But when you talk about authors or users too, that's one of the things you talk about in the book and just talked about, and you have this parallel process to go through them, which has never done well. How close in your work, I guess, because you're probably doing as well as anyone. How close do you feel like you're getting and how do you carve out whatever bandwidth you can for these concerns? Greg: I mean, I say at the beginning of the book that I outline a ton of things that you can do to help authors in the book, but I admit that there's never been a project in which I have done all of these things. Usually what I'm doing is I'm taking the pieces that I can or that I can apply to the project that I have at hand and working them into the process. Greg: For instance, when we do discovery with a client, I always make sure that the content authors or someone from the editorial side is represented in the meetings. That's like a step one to make sure that they're involved and can make their voice heard, and that's easy. Well, it's mostly easy, and that moves a lot of what follows along and can say, well, who is this person and what are their expertises and needs? That leads to interviews with other content authors and that can feed into definition of functionality, into identifying pain points, and that leads in different directions depending on how it goes. Greg: I think it's more about we never carve out a bucket of hours for content authoring. It's more about how can we build it into our existing process and mak
Embed this episode
No transcript yet.