One of my first year Engineering courses, "Engineering, Society, and the Environment", was complete BS and an utter waste of time, but I did end up retaining exactly one thing from it: the course made the distinction between "Knowledge separated from experience" and "Knowledge embedded in experience".
While working on my first startup, I was reminded over and over again of that distinction. Near the beginning, I read - and understood, I thought - many blog posts and comments here about the startup experience. Many times, though, I got to a point where I experienced something I had read about - and found that I understand it on an entirely new level.
What I'm getting at is that you're looking for written resources - "Knowledge separated from experience" - while asking for "The best way to learn", which IMO is to "just do it". You can't learn programming just by reading books, I would be surprised if business skills are any different.
I realize this might not be very helpful, and if there are any good resources I'd love to see them too, but... step 2) really is "keep trying until you succeed and figure it out along the way".
While working on my first startup, I was reminded over and over again of that distinction. Near the beginning, I read - and understood, I thought - many blog posts and comments here about the startup experience. Many times, though, I got to a point where I experienced something I had read about - and found that I understand it on an entirely new level.
What I'm getting at is that you're looking for written resources - "Knowledge separated from experience" - while asking for "The best way to learn", which IMO is to "just do it". You can't learn programming just by reading books, I would be surprised if business skills are any different.
I realize this might not be very helpful, and if there are any good resources I'd love to see them too, but... step 2) really is "keep trying until you succeed and figure it out along the way".