The first step of a content- or knowledge related project is to organise your existing assets. These are likley to fall loosely into the following categories, depending on the business area and current workflows:
- Assets that have already been published but are not performing well
- Assets that have been published but are now out of date
- Published assets that are performing well
- Published assets that contain up to date content
- Draft content created by AI that is still somewhere in an AI chat
- Draft content that has been reviewed and should continue through the publishing workflow
- Draft content that has been reviewed and should be archived.
Performance clearly depends on the purpose of the content and the KPIs will reflect what “performing well” actually means.
The easiest way to approach this, assuming we are operating in a startup or solopreneur environment is to create a Notion database.
For many of us, this category, “Draft content created by AI that is still somewhere in an AI chat” presents quite a headache; I know I have a draft landing page rewite, and I rememeber thinking it was pretty good, but I have no idea which model I used, or even what the title of that chat is likley to be. I wish there was an easy solution to this, but so far I haven’t found one. While you can ask an AI to repost any posts it’s created earlier in a conversation, this in not reliable.
The best solution, it have a Google Doc or equivalent open when you’re working with AI to capture any content it writes and then link the conversation to the post you paste into the document.
