-
Tried the web app, couldn’t find the automation features you sell on the home page. Not bad for a team checklist, but still lacks communication features. Something like Asana but able to define template processes, automation and dependencies would rock.
-
Thanks rpc.
I agree with you that triggers and outcomes is hard to find.
Here’s how to use them.
To add triggers and outcomes to a template, go to your team, then click on the template you want to add triggers and outcomes to. On the top right corner there is a icon with three vertical dots, click on that to show a menu, there you will se two options, "Set triggers" and "Set outcomes". Use this options to add triggers and outcomes to the template.We are looking into how we can make this much easier.
-
-
I don’t know if you’re talking about outcomes for a howl checklist or the outcome of a task. So I answer for both.
It’s an awesome idea to be able to attach some content to the outcome of a checklist. Currently we support something called “Result outcome” for checklists, this means you can add a couple of results a user must choose from before marking a checklist as completed. E.g Approved or Not approved, or Successful or Failed and so on. But adding the ability to attach content, like a large text, url or file would make it much more powerful.
For individual tasks with a checklist we are working on adding the same “Result outcome” as for a checklist. So you can set a task as “On hold”, “Working on”, or “Completed” and so on.
And of course you add these results yourself, you can add up to 10 possible results for a task or checklist.
Thanks rpc for the good idea! I'l be sure to add it to our backlog.
-
Beware, that’s just an engineer view of task management! :D
Once and again, we find this two situations in Asana: We have a template, just a task list, with assignees in the titles (so tasks are not assigned until later). It’s very manual, and the “outcomes” that should trigger the next task don’t have a clear place to live in. There is some “task dependency” support in Asana, but it’s useless. Things like https://flowplane.com are too complex and external to be of use.
The ideal would be to have some kind of sequencial, outcome-based dependency that only sets a task as active when the previous one is complete. This might be easier to model visually, and the linear case covers most needs (for parallel you could use task group based dependencies).
-
I see, it’s ha tough balance between functionality and simplicity. So every new feature needs a huge amount of consideration.
As I see it, the automation aspect is “plugged in” to either the trigger (start a new checklist) or the outcome (complete the checklist) between this two there is the checklist with tasks that people have to complete. I'l focus on making better automation and 3rd party integration on the trigger and outcome side of the service, keeping the checklist part as clean and simple as possible.
This is the plan anyway. And if I get feature request from people using the product I will of course take that into account.
Thanks again for well thought out feedback!
-
-
-
-
-
-
Can’t you use federated authentication instead of forcing people to create yet another username and password?
-
-
This brings up memories. I created a checklist management app 5 years ago, when I was just starting to experiment with products. There was zero uptake (it didn’t have as many features but I don’t think that’s the reason). I hope that the OP has done better research and has lined up some customers before implementing the product!
-
-
I work in a grocery delivery service. We have teams that can use this type of product. For instance, every week we need to prepare the menu for the next week. This usually involves a number of steps, which can be taken by different team members. The have a checklist of sorts, but it’s mostly in their heads. If they miss a step, it may end up with an obvious problem (like no produce showing on the website), but it can also be really unobvious. Like, statistics are not gathered and the COO’s reports are empty. Having a shared checklist would be amazing. We’d totally pay for the authorization. We don’t want most of the staff to be able to change the steps needed, just to mark them as done.
-
-
Frej, welcome to Lobsters! Posting links to your own project is fine as long as you use the
projecttag (the ask tag is usually used for questions to the lobsters community). Don’t worry about the miss-tag, the moderators should clean it up.As for your service, first a disclaimer: I’m a team of one, so I don’t need to manage many processes between people.
When I was at my last job, we had something similar, but much lower tech. It was just a static checklist that was printed out when a new employee was hired. My experience was these lists became unmaintained, and eventually you had tasks on the lists that really didn’t make sense.
In the case of a new employee, would they be keeping track of their checklist themselves? Or are many team members editing the same checklist at once. I would be worried that a product like this would just eventually turn into a product-management product like Trello.
Lastly, you have a grammatical mistakes on your homepage
We have not yet launched but sign up above and we keep you in the loop!
should be
We haven’t launched yet but sign up above and we’ll keep you in the loop!
-
Hey, conroy!
Thank you very much for the greate feedback! I will definitly try to select the proper tag the next time.
As for the example of a new hire checklist, you can assign multiple people to the same checklist and they se eachothers changes and completed tasks. You might want to assign the new employee this checklist but it is not nessesary.
It is alwasy a risk that a product like this turns into something like Trello, project management software is a really crowded space, and there is very good products already developed.
My vision is to develop this into a product that manages all processes within a team, like new employees.
I'v created a quick demo of how the product works: http://www.youtube.com/watch?v=qIIPw2TBOJQ
Thanks for the grammar correction, it’s fixed!
-
Looks interesting. I use a daily checklist to help keep me organized, currently it’s all in a text file but it would be nice to have a more structured version of the same thing. I wrote a partial implementation but got busy with work before I finished it, what you’ve got here is the closest I’ve seen to what I had in mind.
As a business I think you’ll have a challenge getting paying users, this seems to be an idea that many people think is good but that doesn’t bubble up the list enough to spur action (ex: http://evhead.com/2008/09/processizer.html).
-
Thanks for the feedback!
I agree that it will be a challange to convert free users to paying, but with the right features in the payed plans it might just be enough conversion to be a viable business
I have also read Ev’s product idea, and one thing that worries me a bit is exactly what you point to, that the idea is not new but there is no product on the market that meets this suposed need.
-
-
-
I love this idea! A few years ago a friend of mine and I built this application called, “Managing the minutia.” The idea was that concepts were easy to get right, but most of the time was spent in the details. Similarly, most of our time isn’t usually spent on big things, it’s spent on thousands of small things. It made sense to us to build something to manage the thousands of small things. Cheers to you, looks good. p.s. we ran into too many details to make ours work ;)
Thanks bmercer!
I agree with you to be mindful of every new feature and change that could make the product more complicated. I have a clear vision on what I want Firesub to be, so that helps me when deciding on new features.