" "

Applications

Personal Kanban using Google Calendar, LeanKit and Zapier

This is the second post in the series by Chris Hefley of LeanKit showing how to integrate tools many of us use everyday with our Personal Kanban. You can read the first post - Killing Email Interruptions: Personal Kanban using LeanKit, Gmail and Zapier here.

This time, we’ll look at how to integrate Google Calendar with LeanKit via Zapier.com. We’ll look at two different ways to use Google Calendar and LeanKit together.

Creating a Zap Trigger

Setting up GCal with LeanKit

Search Term for GCal Trigger

Creating a new card type in LeanKit

Matching GCal event to LeanKit

Adding Summary and Event Fields to LeanKIt Description Field

Creating an Event with LeanKit in the Event Title

Testing Zap

New LeanKit card on Personal Kanban board

Alternative way to add event cards to your board - Event Start Trigger

Setting up new trigger parameters

New Calendar Event Setup

Testing and naming the new Zap

New Event Card on the LeanKit board

First, let’s create a “Zap” based on the Google Calendar “New Event Search” trigger. This will allow to create a Google Calendar event and a corresponding LeanKit card at the same time.Zapier will prompt you to set up your Google Calendar account and you can use your already set-up LeanKit account.After setting up the accounts, set the Search Term for the Google Calendar trigger. I used “(LK)”. If I create an event with “(LK)” in the title, this integration will create a LeanKit card for that event. That way, I can easily control which events from my calendar get a card.Now, I want to create a new card type on my LeanKit board, for “Event”.Now that we’ve taken care of that, we can set up the target LeanKit board, lane, and card type.Use the “Summary” field from the list of fields available from Google Calendar for the LeanKit Card Title field.Not all my calendar appointments actually have a description. Since Description is a required field in the LeanKit integration, add the “Summary” and “Event Begins (Pretty)” fields to the LeanKit Description field, in addition to the Google Calendar Description field, as shown below:We’re nearly ready to test the integration. First, though, let’s go to Google Calendar and create an event with “(LK)” in the event title:Finally, test and name the Zap:And you should get a new LeanKit “Event” card on your personal kanban board:There’s one other way I’d like to integrate my Google Calendar with LeanKit. I’d like to create a new card on my LeanKit board one day before a scheduled event, instead of immediately when I first create the event. So, if I’m using my personal kanban board to keep track of things I have to do on a given day, I will get the next day’s events added the the board each day.For this integration, I’m going to use the “Event Start” trigger from Google Calendar.When setting up the trigger parameters, I chose 1 day, and used the Search Term “(LKF)” (for “LeanKit Future”). The Search Term is optional, if you want this trigger to fire for all events.For the LeanKit parameters, set them up the same as in the previous example, then create a new Google Calendar event. The event needs to be in the future, within 24 hours of the current time in order for our test to work. And I’ve added “(LKF”) to the event title:Test and name this Zap:...and we should now have a new Event card on our LeanKit board:There you go! Now you can create a card and event at the same time, or mark a calendar event to have a LeanKit card created in the future, when the event is 1 day away.

The "Man, That Was Awful" Approach to Personal Kanban

Keep Track of Tasks that Hurt

Kanban is meant to be epiphany heavy, but process light. These approaches are meant to provide simple means to visualize how your work actually flows. Some tasks are going to be horrible. They are going to take longer than you expect, be harder to complete than anticipated, or even just really annoy you.In life, you want to do things that make you happy and not do things that don't. So why not start noticing what you don't like to do or what takes you away from doing the things you like?The MAN THAT WAS AWFUL approach is simple. When you finish a task and it was in anyway unpleasant - set it aside. Then, later, take a look at the tasks that were unpleasant and look for patterns. Were the people involved the same? Was it a resource issue? Do you just hate doing those kinds of things?After you see the patterns you can make choices like:

  • when to delegate

  • when to refuse work

  • what processes you might want to recreate

  • if you want a new career

  • to cry

Again, the point here is to make what you are doing explicit. Hopefully bad things will initially fall into some patterns that you can consider and reshape. Awful tasks should become less and less common as you can spot them coming and learn ways to deflect them.Photo by _Boris

" "