Wireframes; The Fine Line

There's a lot to say about wireframes, so let's start with the 'official' definition, but with all things UX, everyone has their own interpretation. So, I have not choice but to throw in my own two cents. I like to think of wireframes as the skeleton of your design, an opportunity to map out the flow and to iterate on it until you find the one that you and most importantly, the users are happy with. Of course, this definition of mine is bound to change over the next months, but we'll go with this for now.

Wireframes are crucial for a myriad of reasons, such as:

1. And this is the most important one, you can change it up!

2. You're able to explore various designs.

3. It's a fast process (for the most part).

4. You can pick the best versions of your wireframes and create a super wireframe.

It sounds quite perfect, it's the baby steps that lead you to your big jump. But hold on, what does your wireframe look like? Does it have enough data to convey the purpose of the design? Or, have you overdeveloped it and created a hi-fi prototype?

"It sounds quite perfect, it's the baby steps that lead you to your big jump."

Perhaps it's my over-analytical UX student mind that cares about the standardization of wireframes. Perhaps, all it is, is a beginner viewing this big new world through fresh eyes while trying to create consistent connections and a lot of times, well, there aren't any.

And while I wouldn't want to stifle anyone's creativity by adhering to rules as that would surely be the end of design. I can't help but be overwhelmed by the disorder. When the fine lines of wireframes spill over to thicker fully fledged designs it makes me feel as though I have gone about it the wrong way.