Discuss Home · Bootstrapped Podcast · Scribbleton Personal Wiki · HelpSpot Customer Service Software

Hi, I'm Marcus and (slowly) building an app to build and share checklists


#1

I work full-time at Automattic and building my app in the evenings/weekends. I have had the idea for a few years of an app to build and share checklists to help make processes consistent.

Time and again I run across the issue of repeatable processes getting bungled because people (me) are relying on their vague memories of what they did last time, which may have been a month ago. I hope to have it live in the next couple weeks, just a splash page now at chklst.co

I came across the bootstrapped podcast and binged through all the past episodes in a week or two and it is just getting better every podcast, keep it up @ian and @andrey. I’ll be a little sad when I have to wait a week to hear the next one.

Looking forward to reading and hearing more from everyone here.


#2

Welcome to the forums Marcus! Out of curiousity, have you read The Checklist Manifesto? It makes a great case for why checklists, when written well, can be an awesome tool helping battle complexity.


#3

Thanks @JaapRood for the link, I haven’t read the book but saw a bunch of articles when it came out, I’ve ordered it and will read soon. This was one of the reasons I like my idea, though relatively simple, it does have significant impact in improving process and can be really useful.


#4

Interesting idea, I’ll be interested to see how that goes. @JaapRood books looks cool, definitely going to check that out.


#5

I remember I was first introduced to the power of checklists by this educational article in New Yorker:

From that time on, I always try to make a checklist for my repetitive tasks, though the tools are not always available.


#6

@rfctr - can you expand a little on tools not available? This is the crux of the issue I’m trying to solve and curious what you might have used or found lacking in tools.


#7

Welcome @mkaz! Have you thought about “building in” a bunch of checklists? Seems like that could be an awesome scaleable SEO strategy a la @patio11… things like checklist for deploying, checklist for completing a sprint, checklist for camping… Nice thing is, you can get started now, perhaps try to use that to get email signups and see if there’s some interest.


#8

Max, my boss at Pusher is a big fan of checklists and highly praised this book. He wrote a pretty good summary and put it on his blog, you can read it here. This might something useful for @mkaz too.


#9

Yes, this is an idea that I’ve been thinking of trying as a strategy. I’m working on the base functionality and setting up of lists and then the next step is how to share, public/private lists and cloning of lists. I’ve been waiting for this functionality before attempting creating lists for others to clone.

I hadn’t thought of trying it before and using it to drive signups / interest.


#10

Nice. Guess it depends how far away you are from that core functionality, and how much extra effort it would take to build some static lists. The sooner you get the lists up though, the sooner you’ll start getting traffic, of course :smiley:


#11

I was leading a deployment team, something that nowadays often referred to as DevOps; though many activities were scripted, much more were not, which consistently lead to human mistakes. We have tried to implement the checklists, but generally failed. The checklists (e.g. “how to configure specific domain for specific application”) change with time, sometimes very fast, and have variations per environment. We needed one and only one copy for each activity that can be shared and concurrently updated by many people. Given that some people worked in Windows, some in Unix and some even in ancient mainframe environment, we couldn’t use neither Word nor Google Docs (though Google Docs would be pretty close to what we want, but security wouldn’t let us).

We end up documenting steps where possible with scripts, i.e. went DevOps way. At least half of the applications in our environment though were not scriptable.