1. Getting Started
Getting started sections are key in building user confidence in using your product. They can introduce new features, link to other documentation resources and highlight cool examples. Note the distinction between start and get started; start implies ongoing actions while get started simply means beginning. Having this distinction within your documentation adds meaning and adds impactful words that your users can understand more readily.
4. Getting Around
Get Around can mean both physically traveling to various places and using it figuratively as an adjective, such as Max who enjoys getting around town to stay informed on everything that’s going on – thus getting around refers both literally and figuratively! Our example sentences reflect current usage of this term from various online sources; please send us feedback!
These examples have been generated programmatically and do not require review by Merriam-Webster editors.
5. Getting Things Done
David Allen developed the Getting Things Done (GTD) productivity system. His central thesis is that your brain was never intended to store information; so the more stuff we try to keep in our heads, the less capacity is available for higher-impact activities. Allen describes five crucial steps in his GTD workflow: Capture all your ideas and to-dos; Process/Clarify; Organize; Schedule; Delegate; and Reflect.
Once your system is in place, you can rely on its system rather than your memory to remember everything – relieving stress and freeing up mental space for higher-impact tasks. Once this step has been taken care of, projects can move forward more smoothly while you delegate tasks to others, store reference material away in files and conduct weekly reviews of your system (this flowchart shows these steps).
