Design analysis paralysis

It was the start of (yet) another project. The requirements were in. The database table design was done, subject to changes if the final code needed it.

So I sat, arms on the arm rests, slumped slightly in my comfy chair. Leaning slightly backwards, I had my eyes on the ceiling, looking for inspiration, gently rocking on the chair. Shapes and colours formed and dissipated, words and numbers just barely clear enough to see.

I was visualising my user interface design.

After I had the general idea that the imagined web application user interface, required business logic and database tables were going to match, I started drawing. I pulled a few blank pieces of paper from my stash of trash paper, and drew an outline of how it would look on the web form. Panels, textboxes and dropdownlists. Datagrids, buttons, checkboxes and radio buttons.

Should the textbox take in only input of “dd/MM/yyyy” format? Restrict only numeric input? I scribbled my notes beside the interface controls on the paper.

Finally, I’m done. I’ve got arrows denoting process flow with notes on input and display output. Then I went back and thought again. Would this interface design work? Could it fulfil the business requirements? Could it support insert, update and delete operations to the database tables?

After half an hour, something inside of me screamed, “Stop this!” I’m in design analysis paralysis. I heaved myself out of my reverie, and started actually coding.

Has this happened to you before? You want to make something perfect, so you think about the design, planning it this way and that. You chew over some of the decisions, “oh that’s not gonna work well”, and rearrange some parts.

There comes a time where no more designing can help you. The only way to see if your design works is to actually start writing some code. With working code, you can test. With tests, you get feedback, with which you can correct your code.

Let me give a non-programming example, my writing of a sestina (of the poem category). Its rules are simple. There are 6 stanzas (or paragraphs), each stanza consists of 6 lines. Each of those lines must end with a word from a group of 6 words. Every stanza must have lines ending with one of those words. The words must not repeat within a stanza and they must be in a certain order. The seventh and last stanza has only 3 lines, but each line must have 2 of those special words, and one of the words must end each line. I probably confused you more than explained how a sestina works, so you might want to read it up yourself.

So what I did was come up with the 6 words first. Analysing the sestina requirements, the obvious observation was that every one of those words would be used 7 times (7 stanzas). Instinctively, I knew I needed words preferably with more than one meaning, so I don’t keep repeating the same theme.

Then I realised that if the words could be both a noun and a verb, then it’s easy to describe it with more than one meaning. So “code” can be programming code, or cryptographic code, or code as in writing code. I was stuck in a mental quagmire coming up with those 6 words, trawling through my vocabulary for words with ambiguous meanings and double entendres.

Obsessed with fitting the words, a theme and sestina rules, I got that “Stop it!” scream again. I needed to just start writing the sestina. I needed to stop designing in my mind, and start doing something.

So on my computer, I just typed out the 6 words first, one on each line.

sun
code
water
tree
two
force

Then slowly, I filled in the details,

Just like the life giving warmth of the sun
You can create a better world through your code
Even something as simple and mundane as water
This element of old courses the veins of a tree
With earth and air, ancient elements the other two
They fuse together, becoming a beautiful force

Each line gives inspiration for the next. Then I typed out the 6 words for the next stanza in the order required.

force
sun
two
code
tree
water

And I filled that as well. Some stanzas I had a theme to work with, and the words seemingly flow and automatically end with those words I chose. Some lines required a bit of nudging here and there. Some lines required changes so the whole sestina still reads smoothly.

Then it’s done. I proofread it, checked the visual look on screen and recited it for cadence testing. And it’s done. If I had still been stuck deliberating over my choice of words, I’d never be able to get anything done.

The only way I could move forward was to break out of design mode and do something. So how do you break out of design analysis paralysis? Have you ever been in one?

[To the Chinese readers out there, have a happy Chinese New Year (7 Feb)! Check out some of the decorations in my office.]

  1. Aaron

    Another great post. I find your articles very useful and as a beginning programmer, they’re just what i need. Keep up the good work and promote your site more, you’ve got all you need – great content.

  2. Steve

    Yes, I’ve done this almost every-dang-day … 🙂

    Sometimes, I’ll just back away and continue my notes and diagrams later. I guess I liken it to the way a writer approaches a story … get too close to the subject, back away, then attack again later when fresh.

    OK, there are tons of analogies here … pickin’ one … well, lemme diagram out the decision process … one sec while I … ARGGGHHHH 🙂

    Take care, love your stuff!

    –Steve

  3. Vincent Tan

    Sometimes diving fully into your focus is easy. It’s extricating yourself that takes discipline. I like your writer-story analogy. Thanks Steve! Here’s another: photography and subject.

  4. Ben Barden

    You can definitely design too much. I remember being caught in a no-win situation; I was tasked with making some changes to a system I hadn’t worked on before. If I over-designed, it took too long; if I under-designed, I missed things; either way, I only really knew if it would work when I tried coding it. If you say that the design needs changing when you’re in the middle of coding… well, it doesn’t go down too well. And to really put the icing on the cake, the change was so small it didn’t even deserve a document, but the convoluted development process enforced one. What a joke!

  5. Vincent Tan

    Ahhh… the case where documenting and putting the change request into the established process overshadowed the actual amount of coding effort. Exceedingly frustrating for the programmer who don’t see the benefit…

Comments are closed.