CT No.202: The boring tasks that make brilliant content possible
Events next week! An intro to content administration! And the difference between the tech and media approaches to the content business
newsletter
CT No. 201.5: One foot in the door, the other one in the gutter
Bottle episode: Funeral for a friend
CT No. 201: Redefining "keyword"
What if keywords aren't what you think they are?
CT No.200: New dimensions for shaping organizational content strategy
Content powers many businesses, but decision-making about content strategy is rarely elevated to the leadership level. These five continua will directly connect content strategy decisions with budget fluctuations and tangible results.
CT No.199: Content strategy research tools that won't break your budget
A team-oriented thought-starter, brand new courses, and oodles of links and resources for your team
CT No. 198: Content strategy is not content planning
How can we better elevate content strategy at the business level so that our roles, our passions, our work, and our brains are not considered replaceable?
CT No.242: What's your vector, Victor?
How to understand tokens and vector embeddings, for word people.
CT No.241: TF? ID(GA)F: The old faithfuls of language processing
Even in the face of "black box" algorithms, the history of artificial intelligence—natural language processing, more specifically—has left plenty of clues. While we can't understand the full equation, we can see how building blocks create common patterns in how current algorithms process language.
CT No.240: Mad inconvenient infrastructure
Infrastructure, no matter how solid or planned or continuously improved, gets messy. Observing humanity in July feels like the ultimate UX research experiment.
CT No.239: Please automate the tedious part for me
July is prime chart-making season. July 2025 is one more chartmaking season that will not be powered by artificial intelligence, and here's why.
Processing your application...
Please check your inbox and click the link to confirm your subscription.
There was an error sending the email