The best way to code faster is to know exactly what outcome the customer wants. I don't mean use cases, user stories, or traditional requirements (though all have their place), and not the output either, but the outcome. What do they want to be different as a result of your work? If they can't express that, you are on a hiding to nothing (or, if you are lucky, you are riding the gravy train).