One of the most important and useful applications many of us encounter every day are various productivity tools offered by Google, aimed at either the individual or to organizations (businesses, educational institutions, non-profits). The nomenclature around Google products is complicated.
In terms of the commercial offering from Google, I'm referring specifically to G Suite:

G Suite (formerly Google Apps for Work and Google Apps for Your Domain) is a brand of cloud computing, productivity and collaboration tools, software and products developed by Google, launched on August 28, 2006. G Suite comprises Gmail, Hangouts, Calendar, and Google+ for communication; Drive for storage; Docs, Sheets, Slides, Forms, and Sites for collaboration; and, depending on the plan, an Admin panel and Vault for managing users and the services. It also includes the digital interactive whiteboard Jamboard.

Many of the constituent products of G Suite are also available to individuals at various pricing levels (including a free tier). For example, I've been using the free tier version of Google Docs, Sheets, Calendar, and GMail.

A lot of people use Google Drive:

As of March 2017, Google Drive has 800 million active users, and as of September 2015, it has over one million organizational paying users. As of May 2017, there are over two trillion files stored on the service.

Just as I am planning how to help clients with Evernote automation, I've been learning how to automate G Suite, and when I get proficient at doing so, will be looking for clients wanting help to automate their use of Google services.

In the next days, I will write more about various aspects of the G Suite and the types of problems I hope to solve:

• the API of G Suite products, including Google Apps Script and its REST interface
• how to use G Suite products as part of one's own personal information management: calendars, contacts, collaborative editing of documents
• specific cases of programming the API in political organizing and small business collaboration
• what clients can do with G Suite with any programming at all -- for example, with GMail filters
• BigQuery and Sheets integration

When I set myself the goal of writing something coherent every day of November for #MyBizWriMo, I debated with myself whether to set the goal to every day, every weekday, or every day except Sunday. I consciously decided to choose every day (including Sundays and days around Thanksgiving and other particularly busy days) but was hoping that I would actually write enough articles ahead of time so that I wouldn't have to work on Sundays.

I'm letting myself off the hook a bit today to write this post about rest on this day of rest. As long as the writing process is smooth and I could keep myself from getting tangled up weaving together too many complicated ideas, I will take to heart what Jesus is reported to have said (Mark 2:27):

The sabbath was made for humankind, and not humankind for the sabbath

We rest from striving to be productive in order to lay our work down in joy and health. It's possible (and likely) that resting is even good for our productivity in the long term -- but that's not the ultimate point of this Sunday party. For someone who has been fortunate enough to love my work, ceasing my work is not easy. Observing Sunday Sabbath has been a on-again off-again affair over the years. But whenever I am disciplined in keeping Sunday as a day of rest, I have been the profound beneficiary.

So far today, I observed All Saints' Day at my church this morning. I was blessed to be a reader of names of those people dear to parishioners that died since the previous All Saint's Day. I got to speak the names of my three beloved recently departed (Anthony Jerome Smith, Walter R. Hearn, and Virginia K. Hearn) before the congregation and shed tears of sadness, joy, and remembrance. Once I post this piece, I will back away from the keyboard to cook lunch, read Alias Grace, glance through the Sunday New York Times, and laugh with my Sweetie. There is no end of work to do (and many more articles to write for #MyBizWriMo), but those are concerns for tomorrow and the day after.

I've been trying to define my business for a while. As a way of getting help to create a business that will be truly useful and have some staying power, I decided to ask my friends on Facebook for help. Here's what I wrote:

I'm about to launch a consulting/training business to help people use their digital technology (computers, phones) more productively. As I start out, I need help myself in figuring out how to be truly useful to others.

I'd like to focus on helping people to manage and automate their entire range of information: email, to do lists, notes, files, photos, and calendars to complex documents and datasets. That work includes getting people unstuck with whatever computer problems they may have so they can accomplish their productivity goals. I've loved working with teenagers to seniors, the most to the least computer savvy. No problem is too trivial or too grand for me to see what I can do to help.

I hope that you won't mind my reaching out to you individually to ask about the computer challenges you face and ways in which I might be of service to you. I'm starting out by providing some free consulting to friends and family. We'd actually be helping each other because you would be letting me understand the problems you deal with in your lives. So please don't hesitate to contact me.

My friends have been very supportive, and I've started having specific conversations about my business. I am very grateful.

Yesterday, I wrote about how I use Evernote to support my use of David Allen's Getting Things Done (GTD) methodology. I also mentioned how I plan to help others to use Evernote with whatever organizational or productivity schemes they use, especially GTD. Today, I write a bit about what GTD actually is, why I use it, my genuine struggles with GTD, and the reasons why I stick with it in spite of the challenges I've had with GTD.

What is GTD

I use GTD to manage the flow of information in my life, especially information that requires action on my part. The GTD method guides what items to put on my to-list, how to categorize those items, and how to sequence the actions. The Wikipedia article on Getting Things Done highlights a distinctive element of GTD:

The GTD method rests on the idea of moving planned tasks and projects out of the mind by recording them externally and then breaking them into actionable work items. This allows one to focus attention on taking action on tasks, instead of recalling them.

To enact GTD, you don't need to use a computer, tablet, phone or any digital technology; paper probably works fine. I've long embraced using a computer to manage my tasks. I use Evernote as the substrate for my GTD system. (Since I started using GTD in 2004, long before the launch of Evernote in 2008, I started using GTD on Ecco Pro.) One reason I use Evernote for GTD is that Evernote runs on my all of my devices: my MacBook Pro laptop, my Android phone, my iPhone, on the Web, and as a data service via its API. Evernote is also scriptable, which allows me to write programs to compute on the information I have in Evernote. Computing on my GTD system is of great interest to me, something I'll write about later this month.

Once I get my stuff into the "Inbox" of Evernote, I then apply the GTD decision tree/workflow, summarized in the following diagram:

I present this diagram to give a flavor of the workflow. Don't worry if it doesn't make sense by itself. The Wikipedia article from which I borrow the diagram actually narrates the workflow. For someone like me who read the first edition of the GTD book (published in 2001) and is now reading the second edition (2015), the diagram serves as a memory prompt for the questions used to process items in a GTD system.

Even though I first learned about GTD 13 years ago, I can still remember how eye-opening it was for me. That I should work bottom-up instead of top-down was an important change in how I managed my commitments:

Unlike some theories, which focus on top-down goal-setting, GTD works in the opposite direction. Allen argues that it is often difficult for individuals to focus on big picture goals if they cannot sufficiently control the day-to-day tasks that they frequently must face. By developing and using the trusted system that deals with day-to-day inputs, an individual can free up mental space to begin moving up to the next level.

It was also from GTD that I learned to think of a project as a sequence of two or more tasks with a defined outcome. For example, getting a new mouse for my computer is a project because I need to not only order the mouse but then pick it up from the UPS store -- making for at least two steps). A project doesn't have to be a grand production. Once I grokked that I actually had dozens of projects on the go, I no longer neglected to explicitly manage commitments that I had previously thought as too trivial to track.

GTD has not been a panacea

As much as I love the GTD system, I have not yet realized the level of organization that I believe is produced by a more disciplined application of GTD. I see this month as a prime opportunity for me to scrub down and fix up my GTD implementation, which has been running like an unturned car.

Even though I've been unsatisfied with how GTD has been working for me, I was still shocked when I reviewed for my past writings about GTD. To wit, in Feb 2005 I wrote in Getting back to GTD and the desire to be visibly productive all the time:

Last year, I found the Getting Things Done system very helpful in getting me on track. I will focus some hours on getting my GTD system back on track.

and in the same month (Don't overdo the GTD):

It was nice to be reminded by The New York Times: To Do More. Or Less. Or Something, that in the end, I should not take any system, letting alone the very useful Getting Things Done approach too seriously!).

By the end of 2005, I wrote:

The Getting Things Done system is supposed to keep me on top of tasks large and small, but I need to intervention of a higher power and intelligence to get me back on track with GTD.

And in early 2006 -- you can hear the sighs -- I wrote:

GTD has certainly helped me get better organized, but it hasn't been a panacea. I don't blame GTD for my problem since it never promised to let me squeeze five elephants into a clay jar. Instead of aspiring to grow large enough to envelope elephants, I need to accept that I am just an ordinary clay jar.

Eleven years later, while still finding great value in GTD in tracking my personal information, I still struggle with taking on too much work in progress. Earlier this year, I wrote in Don't be WIPed:

Do you struggle with having more projects than you can productively work on simulatenously? I certainly do. That's why I have been attracted to the Personal Kanban productivity system, which puts a lot of emphasis on visualizing, pruning, and limiting one's "Work in Progress" (WIP). I've not been sufficiently serious about setting realistic limits on my WIP: witness my overflowing list of projects started but essentially zombified. How many projects survive on my list when I have neither the energy to advance them nor the will to kill them?

A natural question to explore soon is: how can one make GTD and Personal Kanban work together?

Blame the implementation not the system

After trying a system for thirteen years without accomplishing the level of mastery I had hoped, perhaps I should abandon the "cult" of GTD and look for a system that works. I won't until I push myself to implement GTD with the rigor to which I aspire. To that end, I've already identified some of the areas that need work:

• I have been far from "Inbox Zero" in GTD, let alone my email system.
• The notes I have written to myself alone take up significant room in my Inbox. Surely, I should be able to control that flow of materials coming in for processing!
• I find conducting periodic weekly or monthly review difficult to pull off systematically.
• As mentioned above, I have too much work in progress. What does GTD have to say about this problem?
• I've not clearly articulated my desired outcomes for all the projects in my GTD system. I certainly have many projects without next steps identified.
• I also have many "orphans": actions without associated projects and projects without any actions identified.

I hope to explore is whether software such as OmniFocus - task management for Mac, iPad, and iPhone that has been designed specifically for GTD enforces some systemic integrity that would obviate some of the problems I've encountered. My GTD on Evernote system is a bit freeform; I am searching for a better balance between rigor and regimentation.

Spreading the OK News of Productivity

As a consultant searching for clients wanting help with Evernote and GTD, I might have an easier time if I could claim loudly that the combination of Evernote and GTD has worked miracles for me and that it will work miracles for you too. Just let me show you. But it's good to read what Warren St. John in early 2005, concluded about productivity books, including GTD:

Not that nothing is to be gained from reading, as I did, a pile of contradictory self-help literature. The exercise can lead to all sorts of conclusions about how to live and perhaps even New Year's resolutions. Here are a few I came up with. Following Mr. Tracy's advice, I am writing them down, to imprint them on my subconcious mind.

1. I will not tell people I have all the answers. It's annoying, and people don't believe you anyway.

Nonetheless, I hope to teach GTD to others because GTD has a lot to offer even if you pick up only parts of the system. There is nothing like teaching to deepen one's own understanding of a topic. I'm longing to apply GTD in greater depths to benefit own life and work and to serve the ambitions of others.

In a month, my subscription to Evernote Premium is set to renew for another year. Since I've been an Evernote user for almost ten years -- and an active one for the last seven -- I'm almost certain to pay the $70 to retain the Premium account. Save for the web browser, my email client, and the core utilities of the operating system, Evernote is the most important application in my digital world. It is also the closest thing to being my personal information manager. It's where I make to do lists, plan my business, clip receipts, track my commitments. Evernote is also the first application I turn to draft any document small or large.

As part of my consulting, I plan to help people with Evernote: how to set up Evernote, how to organize notes using tags and notebooks, and how to integrate Evernote with other applications (perhaps with custom programming). I'm particularly keen to work with others on using Evernote to implement various productivity methodologies, such as David Allen's Getting Things Done. I'm currently running a GTD system on top of Evernote, a variant on The Secret Weapon: Evernote and GTD smoothly integrated into TSW. My system is a bit of a homebrew and likely doesn't match TSW exactly. It probably also doesn't match how The David Allen Company would say how to use Evernote. But it would be useful to describe exactly how my system works -- as part of my formalization process at the very least: more later.

I've joined the Evernote Community Program and will figure out whether to move up the tiers to become an Evernote Certified Consultant. I hope to get to know other members of the Evernote community, to learn from them about what it takes to be helpful to Evernote users in general.

For years now, I've thought that November, the month for the National Novel Writing Month, would be the motivating prompt to write my next book. Not a novel -- yet -- but I did want to draft another computer book under the #NaNoWriMo-inspired #pragprowrimo umbrella.

This year, I'm in the middle of launching a consulting/training business to help people use their digital technology (computers, phones) more productively. One of the most important part of that work is to write clearly and consistently about what my business is about: what's its mission, whom do I plan to serve, and the specific services I will provide.

To that end, I'm committing myself to write something coherent every day of November for what I'll playfully call #MyBizWriMo. The pieces don't have to be grand, but they do need to be coherent. So this simple post serves as my first installment.