As a programmer, I tend to have times where I need to report to someone that isn't aware of how the entire design process may work.  There are times when I'd like to be able have them sign some big disclaimer or, better yet, hand them a guidebook on how a process is to work.

Thankfully, not all people I've had to report to are overly critical of what I do on a day-to-day basis

Right now I'm in the process of overhauling the reporting section of the web application that I maintain, and since this is day 3, it seems like I should be past the "create the plan of attack" phase, but I'm not.  I keep myself (somewhat) busy, as I'm the only IT guy at my job, but I'm also not just taking my time on making sure the implementation process looks correct.

If I wait too long, yeah, I could over analyze.  But, if I start coding too soon, there is the high probability that I'll end up having to redo areas that weren't fully thought out.  I don't like designing the process anymore than the next guy, but it saves a huge amount of development time if I know up-front how each aspect will work and how they will interact with each other.

So, while I'd rather be coding, I'd rather not be fixing my own mistakes either.  I just wonder if that's how the person(s) reading my reports see it...