
If you’ve ever watched an episode of Hell’s Kitchen or Kitchen Nightmares, you have seen (and heard) the F-bomb machine that is Gordon Ramsay. It takes a lot of moxie to walk into someone else’s business and tell them they don’t know their a*$ from their elbow, but episode after episode Ramsay does it. While both shows are entertaining, Kitchen Nightmares showcases some quality project management and problem solving skills bloody relevant to content strategy solutions.
Here is the flow of the show:
1. Assess the problem as an outside observer—Ramsay inspects the restaurant, staff and food.
*Content strategists need to find the root of the problem. Is the design struggling due to limitations with the CMS? Is the CMS choking because of an IT issue? Is the content irrelevant because of usability issues?
2. Inspect the systems being used to manage the team/projects—Ramsay watches the way employees interact and inspects the physical and interpersonal ways they distribute information from management, to the front of the house staff, on to the back of the house staff and back to management.
*Content strategists often play the role of cartographers. They take migration maps, design specs, software limitations, internal politics, wishes-on-horses, the beggars-that-ride and put the puzzle pieces together. When they are one of many vendors on a project they must stitch together vendor and client systems from: Word, Excel, online collaborative tools, Visio docs, XML, forwarded emails, IM’s and phone calls. It ain’t always fun and it ain’t always easy.
3. Remove/replace unproductive team members. Simplify complicated systems. Create authenticity, transparency and accountability—Most of the F-Bombs and “you Donkey” comments are saved for this portion of the show, this is when Ramsay gets hands-on with the staff, operations and makes projectiles out of overcooked salmon and soggy veggies.
*Content Strategists are most effective if brought in at the outset of a project but often they parachute in during the middle of a project. When that happens, identifying your strong and weak links is essential. Create new transparent systems and get all vendors, team members and management focused on the same goal.
4. Give the new system a test run. Assess. Repeat—Chef Ramsay’s new menu is usually a struggle the first dinner service. There is usually push back from management and staff but in the end he reviews, adjusts and makes it work.
*The process of creating a content strategy is…a process. It is a living, fluid monster that learns and moves and occasionally leaves a little present in the middle of the room for you after a long day at work. The ongoing execution of a content strategy takes work, in our experience at least two cycles, before finding a balance between stakeholder/content creator/editor and end-user. Be patient. Execute one, cohesive strategy. Have lots of paper towels on hand.
A successful content strategy consists of many sciences, oftentimes multiple vendors and the ability to be both uber-macro and atomically micro. Though Information Architecture doesn’t embrace all categories it is incredible useful for the heavy lifting, “whose bucket does this go in”, decision-making. Here is a great outline and introduction to Information Architecture sans F-Bombs and cockroaches.
“In today’s fast-paced world, everyone’s looking for a shortcut. It can be very difficult to convince people, particularly senior mangers with little hands-on web experience, of the importance of taking the time to do research and develop a solid strategy…The immediate perception of progress feels good but often comes at the expense of overall efficiency and effectiveness. Since information architecture forms the foundation of the entire web site, mistakes made here will have a tremendous ripple effect.”
Morville & Rosenfeld
Information Architecture-for the World Wide Web
1998
—Ian