I originally asked this question from http://ux.stackexchange.com/questions/28987/starting-responsive-web-design-from-desktop-planning-project-time-crunch, but was referred to here
Our product team has begun finalizing details for a user accounts project, which will be worked on in a fluid framework. But, responsive web design had just been brought up to the product directors, and now we're realizing it's important to start preparing for it.
Unfortunately, the high-fidelity layouts designed for desktops have just been created, and we haven't had enough resources and time to figure out if we can convert them to smaller layouts, so our directors are hoping we can develop the the whole project in the wide desktop layouts first, and then work backwards to smaller layouts. (Finish the project in the intended liquid/fluid layout, then do responsive web layout).
With the issue of us not being able to prepare this sooner, are there some best practices that we could do on this fluid layout so that, by the time we finish the fluid project, we can minimize the damages of doing responsive?
I understand that this is not ideal to be doing the responsive planning first, but we also had to get the core desktop webapp done first (slated to finish by Q1).