Last month I was at DevLearn in Las Vegas. As usual for a really good conference, I left with a stretched mind and new perspectives (and, as is regrettably common in a conference, there was little about documentation, or templates, or any of the other themes that I’ve recently been discussing). One thing that caught my eye was what seemed to be a recurring theme of technological determinism. That is,[…]READ MORE about Technology Drivers & Elearning|Takeaways from DevLearn 2019
“A foolish consistency,” Ralph Waldo Emerson said, “is the hobgoblin of little minds, adored by little statesmen and philosophers and divines.” I have, it seems, a very little mind. I adore consistency. And documentation, especially documentation surrounding expectations, enables a consistent approach, not only in training design, but also in working with training teams. If team members know the expectations, they also know what they need to achieve. We use[…]READ MORE about The Positives of a ‘Foolish Consistency’
Yes. Until next time, Kevin Okay, perhaps a bit more explanation. A style guide is just one form of documentation that I talked about last month. And I’ve mentioned style guides here and there in the past. I’m a big believer in style guides. This admiration isn’t universal. Several people I’ve met think they’re too restrictive. Shouldn’t the designer have the ability to use whichever font, whichever color, whichever layout,[…]READ MORE about Should My Training Team Use a Style Guide?
Do you hate documentation? You have to create it, keep it up-to-date, use it, make sure that other people use it. And there’s always the risk that you spend more time maintaining it than you spend working on the actual project. And yet… I adore and (attempt to) follow the Chicago Manual of Style (16th edition—we’re a bit behind the times). I know it’s 1026 pages on topics like when[…]READ MORE about The Case for Documentation