Think Like MacGyver
Using duct tape and baling twine, you can build almost anything you need. It won’t be pretty, and it’s a good metaphor for finding a way to create a solution for an unknown problem. The first step is to do whatever it takes to find a workable solution. The next step is to see how well your improvised solution works. And finally, if the problem still exists and your solution is directionally right, you’ll need to find a more scalable way to solve the problem.
Finding a workable solution may mean using a kind of hack. Start by imagining how the process should work if there were no impediments. Recently, I wanted items from a calendar to show up on an Agile board – the goal was to understand how many of each item showed up in each list. A perfect solution would be an automatic import from the calendar. An imperfect solution would be to copy each item manually from the calendar to the Agile board. The end goal is the same – understand which calendar items belong in each buckets.
Go for the “It’s Done” Solution
My duct tape and baling twine method in this case? A product called Zapier - a kind of “data glue” that allows you to connect events in one service to events and data in another. I started by connecting Zapier to the Google Calendar and I also authenticated against Trello, a simple solution to create Agile boards. Zapier connects products using recipes for events triggered by data in a service. My recipe matched data in the calendar events to particular buckets in the Trello board. Using the date/time of the event and translating it into the day of the week didn’t work, so I had to use a different method: adding characters to the description of the calendar to indicate a particular day (a manual solution FTW).
Did the temporary solution work? Absolutely. Events added to the calendar now show up on the Trello board, which is a big improvemen over the previous method. To get the results into Excel, I also added another bit of duct tape – a Chrome extension to export the Trello board items. As an end-to-end solution, it works. As an automated process, it leaves a bit to be desired.
Next Steps: Building a Feature
So where will this solution go next? It needs to scale to be usable. Events need to get added to the calendar automatically and coded in such a way so that they show up in the Agile board. They also need to show up in the right place. The feature version of this idea could be feasible if there are additional user stories, a documented process showing how these events “live” from start to completion, and some idea of when the manual process will break. Start with duct tape and baling twine and build a “fake it until you make it” version. Then, test that version and see where it breaks. Finally, compile the “must have” and “nice to have” items and pick the best ones.
Image may be NSFW.Clik here to view.
