Hello
Overall this video is really excellent! :^)
MLO for Android v2 is a big improvement and this explainer video does a
pretty good job of explaining what is an extremely poweful, complex system.
Have various constructive suggestions however:
1. Outline
I have now watched the whole through twice and although I thought the *first
half* was IMO, absolutely flawlesss... at about half way through I felt you
would start to lose/confuse any newbies in your audience, particularly if
they are mainstream / non-technical users.
The first problem is that a *lot* of your audience (and I would guess the
vast majority of mainstream users) simply will not know what the heck an
"outline" is. In this context, it is technical jargon!
You won't want to hear this, but my suggestion is that you change all
instances of the word from "outline" to "hierarchy". (Yes, I would do the
same thing to your entire system including the user-guide, btw!)
In this context both words really mean the same thing and every native
English speaker knows what a hierarchy is. Yes, I know that "outline" is
the more correct technical term, but frankly it is computer jargon. (Aside:
MLO is great but it has never been as accessible to mainstream users as it
deserves to be!)
To get clear - in normal use, "outline" means the shape of something. i.e.
a line or set of lines that enclose the boundary or indicate the shape of
something.
But does the shape of a couple of tasks change if the letters change - well
in normal usage... if this were a for example photograph speaking ... YES.
But in this context no - the "hierachy" i.e. the *relationships *between
then task would stay the same.
If you can't change "outline" to "hierarchy", maybe call it "hierachical
outline"
OR take the time to explain the jargon
"The overall hierarchy of tasks, and the way they are indented is called an
outline in computing."
But you have a lot of information to get over and personally I think it's
just a distraction. Why not use words everyone already understands?
2. At 3:49
"In conclusion we have demonstrated MLO helps you to create to-dos and
group them forming simple lists."
TBH, it's not immediately obvious EXACTLY what is meant by "to-dos".
Try "In conclusion we have demonstrated MLO helps you to enter your to-do
tasks and then group them into simple lists."
3.
"We can subdivide our tasks into sub-tasks if we need to and get a plan of
action."
Even this is slightly confusing. What precisely is mean by "plan of action"
- is this a special bit of jargon - a special for more view/output/report
or meant 'generically'. As Steve Krug woud say "Don't make me think!"
Try:"We can subdivide our tasks into sub-tasks so we can get a good
overview of our plans."
Or leave it out completely. The user can already *see* that there's a
heirarchy you're not telling them any thing new.
If you think you can tell them about how this heirachy can be used to
produce sophisticated views that show the first next action in every
project, then sure, go for it, but you need to take the time to do so
explicitly, otherwise all you will create is confusion.
4.
"Views automatically choose only your to-dos from the whole task list."
Yes, I know what you're saying and yes, it's a key aspect of MLO, however I
predict precisely 0% of new/virgin users will understand what you mean.
For one thing it sounds like some other user's tasks have suddenly arrived
("WTF?" !)
Try: "If you put a start date or dependency information into your tasks,
then MLO has views that will only show you those tasks that you should do
right now, rather than the whole list."
In summary, I think you should either take time to explain things properly
or keep things simple. And all I am suggesting is that if budgets allow, I
would recommend re-recording some of the sound track along these lines.
Anyhow, overall MLO Android is great. And the explainer video is great.
Trying to help
J
P.S. It may just be me, but personally I have always had a slight problem
with the word "view". Part of the problem is that view can mean "opinion".
I know it's less probably technically accurate, but I find "report" far
easier to understand! (So much so that if I find something in the MLO
instructions with the word "view" it in, I repeat it to myself using the
word "report" instead of "view" and usually it suddenly makes sense!
or "hierarchical outline"
I was with it
On Thursday, 29 October 2015 16:18:37 UTC, Marina Afanasenko (MLO Team, PR
Manager) wrote:
>
> Hi everyone!
>
> The release of MyLifeOrganized for Android V2 is very close. And you can
> already evaluate the new UI in our video tutorial:
> http://blog.mylifeorganized.net/2015/10/mylifeorganized-for-android-v2-video.html
> Enjoy!
>
> Sincerely yours,
> Marina
> On behalf of the MyLifeOrganized Team
>
--
You received this message because you are subscribed to the Google Groups
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mylifeorganized/0c538bf5-80a5-486c-84c0-4f7d13038f69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
