On 4 Aug 2023, at 19:13, Andrey Tkachuk (MLO) <mlo.andr...@gmail.com> wrote:
Hi Steve,
--
You received this message because you are subscribed to a topic in the Google Groups "MyLifeOrganized" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mylifeorganized/uUSiIbINQxc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mylifeorganiz...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/84558886-4e8e-435d-af56-d62cd9e91898n%40googlegroups.com.
On 5 Aug 2023, at 23:23, imajeff <ima...@gmail.com> wrote:
Steve could you enlighten me on what is less managable? I simply put unrelated tasks in separate folders. The only reason I have two actual files is because one is for my employer and the other is personal, on my devices at home.
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/241c60e3-d068-4afe-b2fa-f651f7b3a86fn%40googlegroups.com.
On 6 Aug 2023, at 21:25, Dwight <mlod...@gmail.com> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/492F6AC4-8327-447F-803D-3458F822126E%40gmail.com.
I guess I’m no different to anyone else. I have developed a way of working that works for me and that I am comfortable with. MLO helps me achieve what I want to and does it very well. I see no need to change for the sake of change or to fit in with an artificial constraint. Especially as MLO have the will to remove the constraint – not all companies are willing to do that, so credit to MLO.
Looking at mural.co, it appears to be more of a drawing/whiteboard tool. That’s great for designing a UI but I find the structured style of an outliner easier for clients to expand their thoughts. A client will typically come with a request “I want the software to do X and this is how you do that”. Their thinking is limited to the feature they want and they have decided how your software is going to achieve it. That gives me a starting point of “I want X” – the how is nothing to do with them; that’s my problem.
Once I have a requirement of “X”, I can map out the consequences of delivering it, so we’re all clear on what it is exactly they have asked for (most clients typically have a very narrow view of change requests). I can also map out potential extensions that make “X” more productive (which also lets me make it more generic and less focussed on a specific client need). I can explain why “X” is good but why “Y” might be better and more flexible. That can’t be done effectively in diagramming tools (well, not by me).
I’ve found in the past that clients get a clearer understanding when they can see the cause/effect in a hierarchical form. It also prompts more in-depth thinking. I’ve lost track of the number of times I have presented a potential extension to a client idea and they have run with it and expanded out their thinking to a more comprehensive change. It’s a game – not to deliver precisely what they asked for but to try and tease out that additional functionality that you know they’re going to come back for. It makes for a happier client and that’s what we’re all after at the end of the day (isn’t it?). MLO does an excellent job of that.
Regards a single file, yes, I could package all of this up into a single file. I’m sure the 99% of MLO users who do not reach the limitation are managing perfectly well with one or two files. That just doesn’t work for me. I’ve always introduced separation into my projects, mainly because of the focus it gives me. If, at some stage, MLO decides the limit is 10 and strictly 10, then I’ll move to another tool. Dynalist gives me enough functionality and the cross platform abilities I need and does not limit me. It also does not charge me. I prefer to pay for MLO because it’s a better tool.
Steve
Hi Steve,
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/c9aeccea-7328-4f89-bad0-363b0b08e674n%40googlegroups.com.