Reopen this thread
Reopen this thread. It was inappropriately closed, and I have reported the post announcing the closure.
And the topic of the conversation wasn't necessarily a feature request anyway, but rather how to accomplish something given the tools presently in use, and those discussions do not belong in a Feature Request thread.
Forcing everything into the Feature request thread is just going to create extra noise and this forum format is already unwieldy.
Closing the thread is stifling the discussions of the customer-base. Since there was no inappropriate discussion, there was no reason to close the thread.
seems to me, that two things are going on. 1) In YNAB's mind, there should be no work arounds. Rules are rules and therefore, you need to just do it "our way." and 2) YNAB is targeting people who have no money and therefore don't know how to deal with people who aren't living hand-to-mouth. In other words, it's a great tool that allows for people to get out of debt, but if you are out, and you have money in the bank, reimbursements use happen at the end of the month on a regular basis. Floating it is normal in accounting principles. (I find this the same with EveryDollar, and why I couldn't use it, because it really isn't set up to allow people who aren't in debt much flexibility.)
YNAB is targeting people who have no money and therefore don't know how to deal with people who aren't living hand-to-mouth.
This. Over a year ago, another user told me, "They [YNAB] are not aiming to be a financial service company for the affluent." At the time, I took his use of "affluent" to be a pejorative aimed specifically at me, and I suspect his idea of affluent involves a lot less money and income than my idea of affluent does. Nevertheless, this person captured a bit of truth that I was not yet ready to see at the time: Web-based YNAB is laser focused on the single use case of someone who is living paycheck to paycheck, possibly carrying credit card debt, possibly routinely using a credit card that still carries a balance, and potentially needing to add to credit card debt from time to time to make the budget work. The farther the budgeter gets from this situation, the more workarounds are needed to make the budget fit the user's needs.
Oh, it's possible to advance beyond living paycheck to paycheck and still use YNAB productively. But the sound track encourages behaviors that are useful for the fire-fighting mode when any unexpected expense might cause an overdraft if the budgeter is not vigilant. It encourages budgeting broke because you're living broke, and ignores the idea that there are better ways to manage money when you are no longer living hand-to-mouth.
Time was, prior versions of YNAB had a great vision and system for people who could get a month ahead of their bills. The problem was, people who weren't a month ahead struggled with a path to get there. With the web rollout, YNAB solved that problem by providing a system that works very well for people who are not a month ahead of bills. The cost is, YNAB expects people who are a month ahead to budget like they're still living paycheck to paycheck.
But hey, if you never get a full month ahead of your bills, most of the problems I see with YNAB cease to be problems.
The farther the budgeter gets from this situation, the more workarounds are needed to make the budget fit the user's needs.
Fascinating and articulate. I’ve just recently switched from YNAB4 because it’s dying on my Mac and my phone. Overall I’m fairly pleased with the new version. No real complaints. This is a bit of a frustration but I think I’ll get by.....
I appreciate your perspectives on this and am happy to take some time and consider your comments.
The second rule in our Community Guidelines has always been to reduce duplicate threads, but we've let that mostly go up until this point and it creates some major confusion for new users as they join into the Forum. The search feature in this forum could definitely use some help. We're going to try out keeping duplicate threads closed and redirecting feature requests into one place for a bit to see if that helps our team get more information on those requests and workarounds you're using.
I'm aware of all of the frustrations around how features are handled here in this forum and I'd like to make some moves on it. Will it work? I'm not sure, but we're all about trying things and we can always flip back if it doesn't prove helpful.
Perhaps more visibility into what our Forum team is working on would help with frustrations as changes start to come up. We're currently taking steps to make the feature request black hole feeling disappear, change the colors & fonts to improve readability, & reduce the clutter from Direct Import threads. I will post with more details on those items next week.
I'm just heading out to do some camping with my family for the weekend, but I'll be back in on Tuesday. If anyone has thoughts they prefer to share privately, you're welcome to send me a PM on here. Otherwise, I'll stop into this thread when I return.
Veronica at YNAB said:
redirecting feature requests into one place
Directing all features into a single thread is so unwieldy. As a reader, I won't know where to look because of how your forum software groups replies and such. "Feature Requests" as its own topic seems logical but 1 single thread for every single is basically illegible.
Hmm. Stifling discussion is the opposite of my intent on that other post. If there is any regrouping, perhaps a topic area that other people can post to would make more sense.
I don't think that a post about a SFTF fix and SFTF workarounds are duplicates, because forums usually have brief answers/convo segments. Even more so, SFTF and any other feature should not be seen as the same topic or reduced to such.
Besides, I wrote essays. Long ones. That makes finding anything even more unwieldly. Again, the intent was to spur discussion.
Thanks to everyone who jumped in here & for the couple folks who sent me messages regarding this. My team and I are still working through some discussions on this topic before we can make any moves. I will post later this week (separately) with more details on upcoming changes regarding the other points I mentioned.