#Your docs in how to
#Your docs in update

It takes deliberate action to bring people together and to make every department accessible. Having a strong company culture isn't something you can just declare. Newcomers will connect the dots and start making an actual impact on the business faster. This is how we kick off projects at Zapier. Usually, a project manager's internal docs come with a list of project templates for company use. So when we need to solve a problem, we may shirk the obvious answer. If we're evaluating two solutions to the same problem, let's say, we tend to favor the more complex option. A lot of this tendency to overcomplicate is rooted in what's called complexity bias. If they fail to come up with a coherent answer, it's proof they haven't fully understood the concept. That's why, at Apple, engineers are asked to explain a complex technology or product in really straightforward terms. We humans have a bad habit of overcomplicating things.

Any abstract information about what we publish and why is kept inside our team charter to avoid confusion.

#Your docs in how to

In our team documentation, we break each topic down into sections so it's easily navigable, but each section is so short and to the point that anyone can learn how to use our CMS. Imagine having to go through 120 pages of documentation to find and eradicate any mention of the way you used to manage webinars.įor overarching processes, it's better to whittle down the writing to a digestible format, with enough detail for it to be comprehensible, but not so in-depth that any tiny change in the process would make the whole lot moot.Īt Zapier, for example, I help manage our monthly product newsletter, and it helps to outline each step in the process really simply. Say, for example, your team moves your entire webinar flow over to a new marketing tool to better track attendees and form submissions in one place.

#Your docs in update

You're also going to have a field day when something inevitably changes and you need to update your docs to match.

(Unless they're speed-reading champion Anne Jones, who can read 4,200 words per minute. If your internal docs are so convoluted that you break down every single process and concept within that process in agonizing detail, you and your readers are in for a rough time. Here, I'll share my tips for creating documentation that stands the test of time-and that people actually use. I've seen my share of bad documentation and have created plenty of (I hope!) good documentation. You're speaking either to people who sit outside your team and aren't privy to your department's lingo, or to the newbies who don't yet know their CRMs from their CMSs. However, for documents that are saved to OneDrive or another cloud service, you may need to use Save a Copy instead, depending on your version of Word.Remember: when creating documentation, you're not speaking to people with institutional knowledge.

If the document is saved locally, you can use Save As to save a copy of an existing document with a new name, format, or location.

If you’re saving a document for the first time, using the Save command will prompt the Save As window to open.

You can also use the keyboard shortcut F12 (in Windows) or ↑+ ⌘ Command+ s (on a Mac) to open the Save As window.

X Trustworthy Source Microsoft Support Technical support and product information from Microsoft. xml) from the drop-down menu at the bottom of the window. A window will pop up prompting you to name the file and choose a location on your computer or a linked cloud account where the file will be stored. Once you’ve created a new Word document, open the File menu and select Save As.

This function lets you name your file and choose its location.