Right now I'm designing integration guides for 3 major cloud platforms, one with multiple languages, and each docs how-to will have a corresponding video version. But they are not exactly the same, the videos are beginner-oriented and targeted at 5-8 minutes and the docs are more comprehensive so
You've determined the scope of the problem your lasagna strategy is intending to solve, now you uncovered different bits of info: * It's 3pm and lasagna takes at least 2 hours * There are no tomatoes at home * Can't shorten the recipe * It's Carla&
In 2005, a flock of 1,500 sheep jumped off a cliff to their wooly doom. How come? Because sheep follow the leader. One started it and the rest followed. So... If your competitor jumped off a cliff, would you follow? No? Then how do you know they aren'
Umami is a Japanese word for an off-the-wall taste experience – to say it's simply "savory" is to sell it short. It's umami. If your content is food (which it must be because we consume it), then you want your content to have that umami
When you're cooking, recipes assume you have prerequisite knowledge – they don't explain every little technique ("Put it in the broiler for 5 minutes" vs. "Put in the broiler, which is a mode your oven can go into that heats food with a flame
Yesterday I said that communicating a strategy without including the actual challenge being targeted is like asking, "What's for dinner?" and the answer is, "Lasagna. And it has to be ready by 6pm sharp." But... why? Articulating the why is part of diagnosing the
