For sometime now, I have observed the classic example of developers vs users mindset mismatch, with the Frappe team. Though its quite commendable how the dev team toils on to get the working product out to users as quickly as possible, however there is a gap for beginners, start-ups, entrepreneurs, MSMEs to get straight right up and clinch their first sale. Instead, what has been observed so far is that the first-time user/entrepreneur is bogged down with technical issues getting the code to work, then further confused as to how to get the business logic setup. Even the ERPNext Academy videos aren’t that helpful or completed, as of today. It is painfully evident that the dev team assumes that the first-time users are well-versed businessmen or Chartered Accountants, or even worse - technically savvy people.
In comes Dinesh Panchal, who has made an excellent set of 8 video tutorials, gets straight to th point ensuring there is no roadblock in recording, enhancing and closing a sales cycle.
Perhaps the ERPNext/Frappe team, @rmehta and @umair, should look into creating more videos/tutorials of such kind, rather than just compiling fat user manuals.
@abbas At this point any type of manual that leads to easy deployment will be appreciated. Currently, sometimes you have to query different search results and mesh ideas from several to achieve a single objective so having a straighline process in a text document will be a welcome relief.
Greattt job !!!
This is absolutely fantastic …is it possible to divide the job into sections so that each n every one can pitch in where he/she has a better understanding
Yes please…please if it is possible write the complete cycle in heading …e.g. if you are expalining sales invoice …please write the complete cycle first as it’s get confusing so as to what Direction to follow
Can it be done ?
Just today i was making a company n it took me such a long time to add bank account to it …i am still not sure if i have done it properly…so any input from you would be a great help
I Agree with the methodology of explaining processes not features.
If I want to implement an ERP I have a specific requirement to fulfill(payment for example). A guide, step by step, showing me which doctypes I need to use to complete my assignments is more useful than manuals explaining each doctype.
Don’t get me wrong, we need manuals for each doctype however I don’t think they are required for the initial implementation and we are lacking those materials.
Hi,
Learning by example is the best approach, starting by preparing master data for the full cycle, then showing required transactions included in the cycle.
By cycle I can say procure to pay, order to cash,…
What topics r you working on …is it ok if i work on creating compAny ,generating bom,quotation,sales order,delivery note ,sales invoice…shall i go ahead
Well, I have a process document I created for installing ERP on a VPS including setting SSL and swap etc… Then I have adding a few fields and changing naming series to import some existing supplier data…
That is mostly redundant as we are starting from scratch… you could go ahead if you have time and start working on some sections, but you kinda need to start from the beginning… in which case, you could create the document???
Thanks for the great job you’re doing. It’s really appreciated. Any chance you could add mysql/mariadb optimization steps to this list? I found that many newbies leave the default configuration and it works at first, and then down the line database queries force sytem slowdown and sometimes system freeze.