Mistake #8 – Build – Not keeping Editor Organized
Mistake #8 – Build – Not keeping Editor Organized
Do you have Production content that’s in “Published and Modified” status?
Do you know what the changes are? Who’s doing them, when are they going to get published? If not, these are potential land mines.
I’ve been on the call with customers who come across something in “Published and Modified” on Production and they published without knowing what the changes were.
STOP! You have no idea! This could break your content!
Here’s the process I recommend:
Overall, you need to put some controls around who can build, what training they need to be able to build, how your folders are organized. Here’s what I recommend:
- 1-Drafts for WIP Projects – This is for any new content creation, test, everything starts here.
- 2-Published to Test – When an item has been published to Test, it needs to be moved here.
- 3-Prod UAT – When an item has been published to Production but is in a limited visibility due to segmentation, put it in this folder.
- 4-Published to Production – Once the item or Solution has passed UAT, move it here.
- 5-Archive – Move items here when they are archived.
This lets us see how many items are in what stage of the process. It also lets us investigate the dreaded “Published and Modified”. You need to be strict when publishing to PROD. (Note, these folders can mirror your Kanban process which is another topic).
Folder structure and keeping the Editor organized is very much related to Mistake #9...
Next Steps:
I hope you found this helpful.
Do you currently see any of these in your organization?
Or does this make you think of anything you need to check on?
Any corrective actions to put in place?
Let’s talk about what’s going on and try to find the best way to address it:
