same here, i've got
[2019-03-14 10:42:19 AM] : same here, i've got every last step of the 30x500 process on a task card on leankit.
1 Reply
[2019-03-14 10:45:25 AM] : mind sharing a pic or somethin? :slightly_smiling_face:
[2019-03-14 10:47:52 AM] : theres a chunk. its mixed in with personal stuff and some i think i archived some on accident. then i also have weekly cards for safari and ebombing. [File hidden by Slack limit]
[2019-03-14 11:06:29 AM] : aweomse, thanks for sharing!
[2019-03-15 09:47:28 AM] : ohhh this is interesting, joe.
[2019-03-15 09:47:44 AM] : i want to put the 30x500 steps in Pep (http://pep.cards)… would love to hear more about how you use this in LK
[2019-03-15 12:24:51 PM] : Yeah essentially i turned all the steps of the course into task cards at a level of granularity where a card can be completed in 0-2 hours. The part 1 cards are recurring each week like doing the different parts of safari (keywording, thread collecting, 3x painstorming sessions) and ebombing (outlining, writing, publishing, dropping, watering hole hangout sessions).
Cards for part 2 of the course are also recurring but over a longer term because sometimes they go into a paused lane while i just focus on part 1. They are made up of the interrogation steps, plinko, SKW, bullets of gold, pitch writing, product creation, launch (all of which are broken down into tiny task cards).
i've taken a couple stabs at switching to pep because all my 30x500 cards are recurring, so when I complete them I manually drag the card to an earlier lane in leankit (or i duplicate the card so i can leave record of its completion in the done lane). And about 50% of my cards are 30x500 cards. But the other 50% of cards are one-time cards that are either generated within the same week that i need to do them, or they are put into a holding pattern (a > 1week "eventual" TODOs). A lot of those are more like big projects or future goals that will need to be broken into smaller cards. It's almost like a junk drawer because i dont know when i'll get to them, but they are things i dont want to forget and usually do try to grab at least 1 card from there each week if possible.
[2019-03-15 12:31:30 PM] : interesting and useful, thank you
[2019-03-15 12:31:56 PM] : we plan to create and share (copyable) workflows with more granular steps for, e..g, A Safari Session and Writing an Ebomb and Dropping an Ebomb
[2019-03-15 12:32:14 PM] : since Pep has the functionality for sharing workflows built in, we haven’t promoted it yet
[2019-03-15 12:32:34 PM] : is it the “junk drawer” tasks that have kept you from using pep, or something else? you said you tried a couple times, i’d love to know what’s stopped you.
[2019-03-15 12:36:33 PM] : yeah it was that. ive used LK for so long that its my comfort zone and i didnt want to abandon the looseness of those lanes, and because of how many one-time tasks i have. i couldnt justify switching only for the better experience of managing my 30x500 cards. The pain wasn't strong enough for me to put in the effort to learn a newer flow model
[2019-03-15 12:38:14 PM] : thanks!
[2019-03-15 12:38:20 PM] : are you planning a card import feature? kinda like how android has a "switch from apple" feature?
[2019-03-15 12:38:49 PM] : does leankit do any kind of post-mortem feature? like, if you have a series of recurring cards, can you view all the past results and notes from specific instances?
[2019-03-15 12:39:03 PM] : i think i also remember feeling too overwhelmed wanting to copy all my leankit cards over.
[2019-03-15 12:39:28 PM] : re: import - hadn’t occurred to me at all, actually. but that’s definitely an idea. i’ll have to do more research to see if the potential cross-grade market is big enough
[2019-03-15 12:39:44 PM] : so far none of our early adopters have mentioned LK at all
[2019-03-15 12:41:11 PM] : re: post-mortem. They have stats like how long a card was in a specific lane for, and status history changes, but i dont use them for my personal kanban (my team doesnt either). they are stuffed away in the corner and dont provide enough value IMO
[2019-03-15 12:50:14 PM] : interesting, good to know, thanks
[2019-03-15 12:50:46 PM] : in Pep, you can add a “commit message” every time you complete a card, and view a complete record of those messages… like notes to yourself, etc.… in the log. so you can see how you’ve done over time, or what observations you made, etc.
[2019-03-15 12:51:09 PM] : in the future, we’ll be adding custom forms for steps in a workflow too. so you can build a “report” of whatever it is you’re doing with no extra work. and refer back to it any time, or share it
[2019-03-15 12:56:06 PM] : actually i recall using pep for a window of time and i really liked that feature. i had a recurring daily journal card and used those commit messages as the journal entries.
[2019-03-15 12:59:17 PM] : awesome, that’s exactly our goal
[2019-03-15 12:59:26 PM] : but yeah the “it takes time to set up” is a real hurdle.
[2019-03-15 01:00:14 PM] : i also want to do first class support for one-time tasks, which are kinda shoe-horned in atm. but it’s gonna take a lot of design work and that itself is not a feature that makes pep stand out
[2019-03-15 01:03:02 PM] : well esp. since i have a lot of existing cards i had to port over. if i was a newbie with no existing personal kanban board i imagine i would have stuck it out. but that, plus the number of one-time cards i have, and having that visibility of my "future desires" cards is what ultimately kept me from switching.
[2019-03-15 01:04:59 PM] : i think having a board for “ideas” or “someday” would do the trick for the last thing, but yeah, i think a lot of our best customers will already have SOME system. even tho none of them do recurring as thoroughly as we do, and certainly not with the logging