Navigating wa as a newbie

I'm embarrassed to admit that getting started on WA has me somewhat flummoxed. The volume of data and the vast number of forks from every step of the process is, for me at least, unnerving. The way the training process is now designed a person can go off on endless tangents collecting bits and pieces of information and, as a result, impede their own progress.

There's an old concept and project management system that some might remember, "The Critical Path" approach to organizing and controlling a complex project composed of many interrelated paths. The controlling system allows the project manager to list all of the tasks needed to get to the goal of the project, define how each component is linked to other tasks, enter the estimated time to complete a particular component and the system automatically defines the critical path, the tasks that when linked together comprise the longest time it will take to complete the project. As the estimated time frames of particular components change the system automatically defines a new critical path and overall time frame to reach the goal. However, we find ourselves in a multi-tree process with no way of staying on track to reach our goal in the fastest time.

For me a training model that contained a single string of tasks that if followed in sequence would guarantee the creation of a revenue producing web site, with all forks eliminated, would be far easier to follow and it would eliminate the "Information Overload Shock" of the model presently being used. If I'm the only person in WA with this view that would be good for me to know. If there are others who share my opinion in part or whole that would be a useful thing for Kyle and Carson to know by sharing your responses with one or the other of them.

Gene Laka