I believe I mentioned this once upon a time, but will do so again. The key to OSCP if you ask me boils down to time management. You need to attack it with a gameplan as opposed to going at it blindly.
When I did the OSCP, I programmed an entire shell script to go through all the tedious tasks. In fact, my shell script (perl + python + shell) was designed to take the test for me. It was built to perform all the recon, bruteforcing, etc., prior to me even focusing on a machine. Problem was, my exam was a curveball. Never the less, I re-tailored my program to do everything BUT compromise the machines.
For example: You know you will be running network scanners, you know for certain services you will run hydra, etc. write a script that does something to the tune of this:
if [ output_of_nmap == 21,25,80,3389 ]
run hydra targeting those ports
Do this for specific hosts in the background while you do something else. This allows you to continue with other tasks as opposed to focusing on one thing (while time dwindles on) in which you have already targeted and started that goal.
If you're doing ONE THING at any point in time... Fail. Take a good day or even a week to create your framework:
1) I will need to run a scanner --> program that
2) Once the nmap output is done, I will need to try some brute forcing --> program that
3) Once the nmap output is done, I will need to need to run nikto/wikto/etc. --> program that
Right a script to take realtime nmap output and fire away the moment you get data back to you. These are three simple core tasks you will NEED to do anyway. Practice it up on a lab. Take the core tasks and script them. No one said you couldn't do so. What I also have had for a hell of a long time is an pre-prepped arsenal of local exploits on who knows how many different machines. This enables to me to find specific exploits without having to run online and find em. E.g.:
Another thing I am a stickler for are config files. Write a program to do the recon for you. Let's say you needed to escalate permissions... What is visible to you? You may NOT need to focus on root all the time. Can you sudo, are you in a misconfigured group? Can you find and read any configuration files? E.g. find / -name "*.conf" It is always good to have a game plan.