profile

The Daily HaiQu

Exercise: Let's automate something! Part 4

Published 28 days ago • 2 min read

We are in the middle of a group exercise to see if we can make some automation improvements to our own day-to-day tasks. Hopefully this process will give us some insights that we can bring to designing, validating or auditing our regulated processes.

Last time, we chose our platform and did some rewording of our simple task's SOP to specifically include links to the various input files, workspaces and websites that we will need to access while performing the task.

With that simple step, we should hopefully have a procedure that we can just click through, already saving us time and effort. Here's my example (modified to use the Google ecosystem for simplicity):

Notice that I've highlighted one nice feature of using the Google infrastructure - as I go through the steps of my task I can open a live preview of a linked file within Google Drive without even leaving my SOP. Similar features exist on many other platforms (as long as you're actually using their cloud and document format).

Adding Triggers

One of the things I asked you to do in Step 2 was to identify any triggers necessary. Let's start with whatever it is that triggers the task itself - in my case it's just a repeating daily task, but you may have something that's triggered by an email or some other event.

I wrote:

"Every weekday, no specific time. I usually let ideas percolate over the day, and then write either late afternoon or after the kids are in bed. Let’s say after 4pm."

Ok - so that should be familiar - we all use todo apps and calendars regularly, probably as part of our email service. Before jumping into the obvious choice, I do have some criteria to consider before choosing:

  1. The reminder needs to be in my face (don't make me check a random web page that I'll forget about), and can be snoozed without losing track of the task.
  2. For frequently occurring tasks like this daily one, you could just have a prominent shortcut, but for anything else the reminder should include a link to the SOP itself, to make it as easy as possible to start.
  3. It needs to allow recurring or re-triggering tasks without my having to re-set things. While most calendaring, note-taking and todo apps allow recurring tasks, sometimes they're limited in surprising ways. And when it comes to triggering on emails and events, you might need something entirely different like Power Automate, Zapier or IFTTT.
  4. And finally, I don't want frequent tasks to clutter my calendar view.

Other triggers that you might want include those linked to specific task steps, such as another reminder that’s automatically set in the future or an email that gets sent out.

In the end, you have lots of options, so try something simple and see how it works for you.

I've tried many options, but these days I find that what works best is a combination of a simple daily and weekly checkbox-led task lists in my journal, combined with Notion tasks for longer term and recurring calendar items.

Why Notion? Because it sends me an email when something is due, so it comes right to my inbox. Then I can use my webmail provider's snooze function to set it to come back when I have the time to deal with it. This works really well for things like tax installments and other reminders that I just don't want on my calendar.

Since my chosen SOP is a daily task, I added it to my daily task template. Now we have an automated trigger for the task, and easy "start button" to give us frictionless entry into our procedures.

Which brings us to the next topic: templates, text expanders and auto-complete.

Until next time, thanks for reading!

– Brendan

p.s. Enjoy this message? Read more at the Hyland Quality Systems website.

The Daily HaiQu

A newsletter about improving the systems we use in the GxPs

I'm Brendan Hyland. I help regulated facilities transform their software, spreadsheets, workflows and documents from time-consuming, deviation-invoking, regulatory burdens, to the competitive advantage they were meant to be. Join me every weekday as we take a few minutes to explore, design, test and improve the critical systems we use in our facilities.

Read more from The Daily HaiQu

Last time we left off with a cliff-hanger of a question: How do you prove you're you when signing a document? There are several ways I've seen that the 3rd party providers prove that it's you who's signed the document: You clicked a link from an email. You paid for the service with a credit card. You provided some government issued photo ID. Someone, such as a notorized public or your HR department, has verified it's you in person. Obviously these are very different levels of assurance. Then...

14 days ago • 1 min read

Last time we learned about the difference between an electronic signature - basically any way of signing a document electronically - and a digital signature, which is a cryptographic mechanism that can be used to implement electronic signatures, among other things. Modern digital signatures most often use the Public Key Infrastructure, or PKI, to generate and verify keys. So for you to properly e-sign your document (and I'm really simplifying things for illustration here) you need three...

15 days ago • 1 min read

There are several levels of 'signatures' that you can apply to an electronic document. The first and most basic is just an image of your written signature. One common option for this is to print the document, sign and scan it back in again. A more convenient version is to have an image of your signature saved that you can paste into documents. This is what many free versions of pdf software and word processors offer as a basic document signing option - a 'stamp' of your saved signature image....

17 days ago • 2 min read
Share this post