222 lines
11 KiB
HTML
222 lines
11 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||
<meta charset="utf-8">
|
||
<meta content="IE=edge" http-equiv="X-UA-Compatible">
|
||
<meta content="width=device-width, initial-scale=1" name="viewport">
|
||
<link href="../../old/assets/style/styles.css" rel="stylesheet" type="text/css">
|
||
<!--[if lt IE 9]>
|
||
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
|
||
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
|
||
<![endif]-->
|
||
<script>
|
||
(function() {
|
||
var s, scheme, wf;
|
||
|
||
this.WebFontConfig = {
|
||
google: {
|
||
families: ['Amaranth:700,700italic:latin', 'Inconsolata::latin']
|
||
}
|
||
};
|
||
|
||
wf = document.createElement('script');
|
||
|
||
scheme = 'https:' === document.location.protocol ? 'https' : 'http';
|
||
|
||
wf.src = scheme + "://ajax.googleapis.com/ajax/libs/webfont/1/webfont.js";
|
||
|
||
wf.type = 'text/javascript';
|
||
|
||
wf.async = 'true';
|
||
|
||
s = document.getElementsByTagName('script')[0];
|
||
|
||
s.parentNode.insertBefore(wf, s);
|
||
|
||
}).call(this);
|
||
</script>
|
||
|
||
<title>Task management: Things vs. OmniFocus | eRambler</title>
|
||
<link href="https://erambler.co.uk/rss.xml" rel="alternate" type="application/rss+xml">
|
||
</head>
|
||
<body class="single-post">
|
||
<div id="container">
|
||
<header class="page-header">
|
||
<hgroup>
|
||
<div class="h1"><a href="../../">eRambler</a></div>
|
||
<div class="lead">Jez Cope's blog on becoming a research technologist</div>
|
||
</hgroup>
|
||
<nav><ul>
|
||
<li><a href="../../">Home</a></li>
|
||
<li><a href="../../about/">About</a></li>
|
||
<li><a href="../../blogroll/">Blogroll</a></li>
|
||
</ul>
|
||
</nav>
|
||
</header>
|
||
<section>
|
||
<div class="row">
|
||
<p class="archive-warning"><strong><em>Please note:</em></strong> this older content has been <strong>archived</strong> and is no longer fully linked into the site. Please go to the <a href="../../">current home page</a> for up-to-date content.</p>
|
||
</div>
|
||
<div id="content">
|
||
<article class="h-entry">
|
||
<div class="row">
|
||
<h1 class="post-title p-name">Task management: Things vs. OmniFocus</h1>
|
||
</div>
|
||
<div class="row">
|
||
<div class="post-info">
|
||
<div class="post-date dt-published">
|
||
<a class="u-url" href="http://erambler.co.uk/blog/gtd-things-vs-omnifocus/">Monday 11 February 2013</a>
|
||
</div>
|
||
Tagged with
|
||
<ul class="post-tags">
|
||
<li class="p-category"><span class="tag">GTD</span></li>
|
||
<li class="p-category"><span class="tag">OmniFocus</span></li>
|
||
<li class="p-category"><span class="tag">Things</span></li>
|
||
<li class="p-category"><span class="tag">Task management</span></li>
|
||
<li class="p-category"><span class="tag">Productivity</span></li>
|
||
<li class="p-category"><span class="tag">Mac</span></li>
|
||
<li class="p-category"><span class="tag">Apps</span></li>
|
||
<li class="p-category"><span class="tag">Reviews</span></li>
|
||
</ul>
|
||
</div>
|
||
<div class="post-body">
|
||
<div class="post-content e-content">
|
||
<p>It’s taken a while for me to realise it, but I’m a bit of a list-maker. Some years ago I read David Allen’s <a href="http://en.wikipedia.org/wiki/Getting_Things_Done">Getting Things Done</a> (often abbreviated as GTD) and found some useful tips that have had a big impact in how I manage my tasks and my time.</p>
|
||
|
||
<p>There are <em>heaps</em> of apps to help you Get your Things Done, but I generally seem to oscillate between two: Omni Group’s <a href="http://www.omnigroup.com/products/omnifocus/">OmniFocus</a> and Cultured Code’s <a href="http://culturedcode.com/things/">Things</a>. The choice between the two is closely balanced in my head, and I seem to end up switching every 12-18 months. Until recently, Things’ lightning-fast cloud sync had be, but now OmniFocus has tempted me back with its general feature-richness.</p>
|
||
|
||
<p>Some key factors for me:</p>
|
||
|
||
<ul>
|
||
<li>One system for everything:
|
||
<ul>
|
||
<li>One system that syncs across computers and mobile devices, so I always have it with me;</li>
|
||
<li>One system for work stuff and personal stuff, because sometimes I need phone my bank while at work and sometimes the solution to a work problem comes to me while watching TV;</li>
|
||
</ul>
|
||
</li>
|
||
<li>Multiple ways of structuring and viewing tasks:
|
||
<ul>
|
||
<li>When I need to check that I’ve captured all my tasks, I need to view them by project to see what’s missing;</li>
|
||
<li>When I need to actually do things, I need to see my tasks by context, i.e. what equipment/location is required to do them.</li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
|
||
<h2 id="aside-switching-is-not-inefficient">Aside: switching is not inefficient</h2>
|
||
|
||
<p>You might think that it’s a waste of time laboriously transferring all my projects and tasks from one system to another, but it’s really not. This only happens once every 12-18 months, and it’s a great way to do a full audit of everything I want to achieve, spot what’s missing and cull the dead wood.</p>
|
||
|
||
<p>Even if you have one task management system that works for you, I suggest you try occasionally printing the whole lot off (on real dead trees) and re-entering the important stuff. Because it takes more effort, it makes you more ruthless in what stuff you allow onto your todo list and sharpens your focus on what’s important.</p>
|
||
|
||
<h2 id="omnifocus-vs-things">OmniFocus vs. Things</h2>
|
||
|
||
<p>OmniFocus’ strength is it’s flexibility. Each task has not only a title and a checkbox, but a project, a context, a start date, a due date, an expected amount of effort and, if that’s not enough, a freeform note field. It has a rich, hierarchical structure for projects and tasks, and the ability to create customised views of the system or “perspectives”.</p>
|
||
|
||
<p>Things, on the other hand, strives for simplicity. It lacks much of the complexity of OmniFocus and replaces it with tags. Tags can be hierarchical, which is handy, and because you can assign more than one to a task, you can actually use them to replicate a number of OmniFocus’ detail fields.</p>
|
||
|
||
<h2 id="things-is-pretty-good">Things is pretty good…</h2>
|
||
|
||
<p>That simplicity means that there’s very little effort involved in using Things — just throw in your tasks and get started. You can assign one or more tags to each task and then filter on those, and that allows you replicate quite a lot of what OmniFocus allows.</p>
|
||
|
||
<p>The other area where Things beats OmniFocus is in synchronisation. Every time you make a change in Things it’s synced up to the cloud, and updating another app takes moments. There’s no need to manually initiate a sync, so everything is always available everywhere.</p>
|
||
|
||
<h2 id="but-omnifocus-is-winning">…but OmniFocus is winning</h2>
|
||
|
||
<p>Sooner or later, though, the lack of expressiveness in Things gets to me. OmniFocus panders to my desire for structure: I can have tasks from any project (or any part of a project) appear one at a time or all at once. That all takes a little more time to set up (though it soon becomes second nature), but it means when I actually want to get on with work I see only the tasks I need to see and no more.</p>
|
||
|
||
<p>OmniFocus’ perspectives are another example of where the extra power is useful. It’s trivial to set up one-click views that only show a certain set of projects (such as work stuff) or a particular set of tasks (such as things I can do offline), or even just group tasks differently (such as by due date or age).</p>
|
||
|
||
<p>Finally, the iPad app for OmniFocus has a killer feature: Review mode. This makes it trivial for me to sit down at the end of each week with a cup of tea and go through the entire system, finishing off loose ends and capturing next actions. This is central to the GTD way, and is the part of my routine that guarantees everything is in order and nothing gets missed.</p>
|
||
|
||
<p>Of course there are plenty of situations where you don’t need all of this complexity, and that’s fine too. It doesn’t force you into using all of the features to have a functioning system: you only have to use what you need for the current situation.</p>
|
||
|
||
<h2 id="what-about-you">What about you?</h2>
|
||
|
||
<p>So there you have it. I’d be interested in finding out how you use OmniFocus or Things, or if you have your own preferred system. There are even people who implement <a href="http://www.diyplanner.com/templates/official/hpda">GTD using a biro, a binder clip and a stack of 6x4” index cards</a>.</p>
|
||
|
||
</div>
|
||
<div id="disqus_thread"></div>
|
||
<script>
|
||
/* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
|
||
var disqus_shortname = 'erambler'; // required: replace example with your forum shortname
|
||
var disqus_identifier = 'tag:erambler.co.uk,2013-02-11:/blog/gtd-things-vs-omnifocus/';
|
||
var disqus_title = 'Task management: Things vs. OmniFocus'
|
||
var disqus_url = 'http://erambler.co.uk/blog/gtd-things-vs-omnifocus/';
|
||
var disqus_developer = 0;
|
||
if (window.location.hostname == 'localhost')
|
||
disqus_developer = 1;
|
||
|
||
/* * * DON'T EDIT BELOW THIS LINE * * */
|
||
(function() {
|
||
var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
|
||
dsq.src = 'http://' + disqus_shortname + '.disqus.com/embed.js';
|
||
(document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
|
||
})();
|
||
</script>
|
||
</div>
|
||
</div>
|
||
</article>
|
||
</div>
|
||
<div id="sidebar">
|
||
<div class="sidebar-box about-me h-card">
|
||
<p>Hi, I’m <a href="http://erambler.co.uk" class="p-name u-url">Jez Cope</a> and this is my
|
||
blog, where I talk about technology in research and higher
|
||
education, including:</p>
|
||
|
||
<ul>
|
||
<li>Research data management;</li>
|
||
<li>e-Research;</li>
|
||
<li>Learning;</li>
|
||
<li>Teaching;</li>
|
||
<li>Educational technology.</li>
|
||
</ul>
|
||
</div>
|
||
<div class="sidebar-box links">
|
||
<h2>Me elsewhere</h2>
|
||
<ul>
|
||
<li><a href="https://twitter.com/jezcope" rel="me">Twitter</a></li>
|
||
<li><a href="https://github.com/jezcope" rel="me">github</a></li>
|
||
<li><a href="https://linkedin.com/in/jezcope">LinkedIn</a></li>
|
||
<li><a href="http://diigo.com/user/jezcope">Diigo</a></li>
|
||
<li><a href="https://www.zotero.org/jezcope">Zotero</a></li>
|
||
<li><a href="http://gplus.to/jezcope">Google+</a></li>
|
||
</ul>
|
||
</div>
|
||
</div>
|
||
<div class="row">
|
||
<footer><a class="license" href="http://creativecommons.org/licenses/by-sa/4.0/" rel="license">
|
||
<img alt="Creative Commons License" src="http://i.creativecommons.org/l/by-sa/4.0/88x31.png" style="border-width:0">
|
||
</a>
|
||
<span href="http://purl.org/dc/dcmitype/Text" property="dct:title" rel="dct:type" xmlns:dct="http://purl.org/dc/terms/">
|
||
eRambler
|
||
</span>
|
||
by
|
||
<a href="http://erambler.co.uk/" property="cc:attributionName" rel="cc:attributionURL" xmlns:cc="http://creativecommons.org/ns#">
|
||
Jez Cope
|
||
</a>
|
||
is licensed under a
|
||
<a href="http://creativecommons.org/licenses/by-sa/4.0/" rel="license">
|
||
Creative Commons Attribution-ShareAlike 4.0 International license
|
||
</a>
|
||
</footer>
|
||
</div>
|
||
</section>
|
||
</div>
|
||
<script>
|
||
if (!/^http:\/\/localhost/.test(window.location)) {
|
||
var _gaq = _gaq || [];
|
||
_gaq.push(['_setAccount', 'UA-10201101-1']);
|
||
_gaq.push(['_trackPageview']);
|
||
|
||
(function() {
|
||
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
|
||
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
|
||
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
|
||
})();
|
||
}
|
||
</script>
|
||
|
||
</body>
|
||
</html>
|