I was having an interesting conversation with a friend-of-a-friend last weekend, discussing the need for pre-CMS content workflow tools (classic lad banter). More specifically, said friend-of-friend was contesting the idea of decoupling content management systems : having platforms separate from the publishing CMS that focus purely on editorial and production workflows. He believed you could do all of this work directly in the CMS. While this is a fair point (technically at least), I've since been plagued with the arguments I could have given against this idea of doing everything in the CMS. At the time, I just criticised the general user experience of writing and managing content production in a CMS, and mumbled Karen McGrane's analogy about printing presses (about the difficulties of having one tool that attempts to do everything). I’ve since realised that my answer totally failed to confront the most blatant problem with his point: it implies that content production doesn't require a dedicated process. You Can't Sketch in a CMS The funny thing about this conversation was that the man actually worked at a UX consultancy; a place where process is obviously a huge deal.
↧