For AI agents: a documentation index is available at https://idratherbewriting.com/llms.txt. Markdown versions of all pages are available by appending .md to any page URL.

Search results

InDesignSecrets » Learn InDesign One Feature at a Time

by Tom Johnson on Jul 15, 2009
categories: technical-writing

InDesignSecrets »  Learn InDesign One Feature at a Time. The author recommends setting aside 15-20 minutes a day to learn a complicated tool such as InDesign. I couldn't agree more. The same technique applies to exercise and anything else that is overwhelming in large amounts. Approaching it little by little each day, you find that it's not so overwhelming. However, this article has an even more profound implication for help authoring. If people really learn best in 20 minute increments, should we design help with a 20-minutes-a-day plan? What if we structured a "Learn X in 10 Days During Lunch" type of training deliverable, rather than giving them 30 video tutorials or help topics to slog through, which would take them all day? Intereseting approach. I just might try this.

Sponsored

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, agent skills, tech comm careers, and more. Check out my AI courses for more on the latest in AI and tech comm. If you're looking for info about documenting APIs, see my API documentation course.

If you're a technical writer and want to keep on top of the latest trends in tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me.

Finally, I want to note a couple of things. I usually write the first drafts of my posts myself and then use AI to improve accuracy, clarity, and detail in places, so my writing is a mix of human and AI. (Hopefully that's not too off-putting.) Also, the opinions I express on my blog are my own perspectives, not those of my employer.