4
12 Comments

How do I get users to understand that what I built is not a todo list?

I built intray so that I could use it, not with a clear business strategy in mind but with a very clear idea of what it should be.
I meet people that I think could benefit from using Intray (genuinely, it's free to use anyway) so I suggest them to do so.
Invariably, they get back to me asking why a certain anti-feature doesn't exist.
For example, listing all the items in your intray is the opposite of how an in-basket is supposed to work (it defeats the purpose).
I realised that people are trying to use it as a todo-app, and that's very much not what it is.
How do I get users to instantly understand what intray is for?

https://intray.eu

  1. 1

    You need to understand what your users want, and build to that.

    What you want actually doesn't matter as much as you are only 1 user.

    If you want to build a tool for yourself, go for it. Otherwise what your users think your product does, is what it does.

    Have you interviewed any of them?

  2. 1

    A couple of points.

    Why would I use this and not just the notes on my phone?

    When i'm on your website, I can't see how my "tray" will look. This adds a certain layer of friction when it comes to signing up

    The copy on your FAQ is confusing because it assumes people have already used the app. Me, as a newcomer isn't thinking "Why can I not modify items?" because i haven't even seen the app in progress.

    Relating to the FAQ section, there are a LOT of questions to go through. I think you should minimize this to have some on this page and some on the page after you've signed up.

    Also to reiterate what others have said in this thread, you might buuld something for X reason and others might use it for Y. You have two options, follow down the path of Y, or continue along X. It all depends on what you hope to get out of this project and where you want it to go.

    1. 1

      Why would I use this and not just the notes on my phone?

      That's in the FAQ :(

      Notes and intray Items serve a fundamentally different purpose. Intray items are meant to be short term, ephemeral and for prosessing. Notes have an indeterminate life-time and do not lend themselves well for processing. Intray incorporates the best-practices for processing and is not cluttered by unnecessary features. Moreover, Intray items will persist beyond eventual damage to your phone. This is not the case for all notes apps.

      When i'm on your website, I can't see how my "tray" will look. This adds a certain layer of friction when it comes to signing up.

      That's a really good point, thanks!

      Relating to the FAQ section, there are a LOT of questions to go through. I think you should minimize this to have some on this page and some on the page after you've signed up.

      Great idea!

      Thank you very much for the feedback!

  3. 1

    A getting started guide with explanations?

  4. 1

    I have no idea what an intray is, I do understand to-do apps and it seems like the people you tell about intray expect an to-do app.

    You can spent a lot of time to try and convince people that intray is different, or you can make it look like a to do app/ link to-do app features with intray and make it useful so people will actually start using it and then discover the added value of using an 'intray'.

    You don't have to create this in the same app, you could also create for example 'intray for trello' to link an intray 'box' to trello actions. Then at least the difference will be clear.

    Please also realize you are biased, don't let this stand in your way when you want to create a product out of this. What you call anti-feature might actually be useful for many. (I can think of many cases where getting an overview of all items is useful), so keep an open mind.

  5. 1

    I would try to demonstrate the benefit of a strictly enforced first-in-first-out queue of tasks. This is differentiating feature of it. For me, you need to prove true that "the processing does not allow you to see more than one item at a time, which is a proven strategy to improve your processing efficiency" given all the disadvantages of not being able to pick which task to deal with.

    I like the GTD example but is it the only way to use it?

    You seem to be speaking to 3 different audiences in the same text when you speak of an app, API, and CLI.

    I recommend the book "The Decision Book - Fifty models for strategic thinking" by Mikael Krogerus and Roman Tschappeler. Perhaps you could provide multiple guides for making the decision e.g. Eisenhower Matrix, GTD, Pareto Principle. This to me is a stronger value proposition.

    1. 1

      Hi! Thank you for your feedback, this is really valuable to me.

      A few points:

      given all the disadvantages of not being able to pick which task to deal with.
      You don't put tasks into intray, only pieces of thought (that may be tasks), and you never work out of your intray.

      I like the GTD example but is it the only way to use it?
      It's a pretty tiny app, so I think so.

      You seem to be speaking to 3 different audiences in the same text when you speak of an app, API, and CLI.

      Right, is that bad? (honest question)

      Perhaps you could provide multiple guides for making the decision e.g. Eisenhower Matrix, GTD, Pareto Principle. This to me is a stronger value proposition.

      I'm not sure what you mean by this. What decision?

      1. 1

        You don't put tasks into intray, only pieces of thought (that may be tasks), and you never work out of your intray.

        OK, but you have to deal with the piece of thought according to the GTD flowchart.

        I'm not sure what you mean by this. What decision?

        The GTD flowchart is a decision tree. Alternatives could be e.g., deciding with the Eisenhower Matrix (determine which combination of urgent/not urgent + important/not important it is, and dealing with urgent+important first, then important+not urgent).

        You could give some guidance how to deal with the intray item - do it now, put it back in the intray, put it on the calendar, move to inbox, file it for reference - make the flowchart more specific to your app.

        You seem to be speaking to 3 different audiences in the same text when you speak of an app, API, and CLI.
        Right, is that bad? (honest question)

        Yeah sort of bad. A non-developer would be confused by API and CLI, and open-source.

  6. 1

    You are describing your product but you are never demonstrating it! That is why it is hard to communicate what it is about!

    I immediately got that it is not exactly a to-do list but more of a personal log. You have to convince me it is a better idea than using a plain text file (or any number of similar tools I might be using already)

    1. 1

      Thank you so much for the feedback, this is exactly what I'm looking for.

      It's also definitely not a log, though.
      The idea is that you empty your intray into your todo list daily. (You'd delete the items while going through them). The reason that your intray and your todo list are seperate, and you don't just put things into your todo list immediately is that your todo list requires you to think about what needs to happen with this new piece of "stuff" that you have allowed into your life.

  7. 1

    Can you provide a link to your landing page?

    1. 1

      Absolutely! I couldn't add the product via IH yet because it hasn't been approved. (I'm very new here.)

      https://intray.eu

      1. 1

        This comment was deleted 6 years ago

  8. 1

    This comment was deleted 7 years ago

  9. 6

    This comment was deleted 4 years ago

    1. 1

      This comment was deleted 7 years ago

      1. 1

        This comment was deleted 4 years ago