I quite often find myself on the controversial side of a modern UX axiom – the Mobile First manifesto, which basically dictates that design of responsive experiences need to start with mobile layouts.
While I have long considered and fully understand the benefits of this approach from a development perspective, I don’t agree with the Mobile First tenet from a visual design and spatial segmentation perspective. I think it is over-simplifying the process of design at the cost of a universally functional responsive site experience, across all viewports and breakpoints.
Basically, I don’t think sacrificing a functional Desktop experience on behalf of a Mobile experience is necessary or even meaningful. Mobile designs can always benefit from the process of laying out Desktop pages. Desktop designs, however, rarely benefit from Mobile design considerations in my experience.
To do this, you need to see as much of what’s designed in one glance, not view it piecemeal, as if through a keyhole. Otherwise, you will lose context and cohesion.
The complex cannot always be a mere repetition of the simple, or an indefinite combination of many simple elements, but the simple is always by necessity a reduction of the complex.
Mobile can be considered within the whole of a Desktop layout.
The opposite is not true.
Mobile typically contracts to a single column, where spatial structure is linear and vertical.
Desktop introduces another dimension – the horizontal – which adds complexity, and this needs to be accounted for early on in the design process. Focusing only on Mobile, and thereby ignoring possible spatial complexities on Desktop, means you’re designing with one eye closed.
As long as your design will also be rendered on a Desktop device, you will at some point have to account for both the vertical and horizontal dimensions. Leaving that consideration for later, because you’re starting with Mobile, is likely to cause unforeseen difficulties. Just because a Mobile viewport dictates it doesn’t mean that all things can or should be separated vertically – some need to be displayed side by side, or benefit from such an arrangement.
A single Mobile column can be kept as one on Desktop (which is a very common lazy practice these days, leading to swaths of content that are unscannable and excessive line lengths that are essentially illegible).
But a single Mobile column can also be split up into two, three, four etc on Desktop. Columns may not be identical – one may need a background, a box or a border for horizontal separation and contrast. One may need bullets, one may consist wholly or partially of an image, etc. Multiple columns require the creation of and adherence to a grid (with gutters, indents and ragged vs. justified columns), but this need and these complexities largely disappear on Mobile, where elements simply stack, and you want to avoid anything that restricts usage of the full column width.
This creates an illusory simplicity which is often deceiving.
Furthermore, text alignment matters on Desktop. Not as much on Mobile. You can center a column on Mobile and it will still not be perceived all that differently, since the column width is restricted.
A single centered column across the full Desktop width, however, will make for a very tiring reading experience, with line lengths that may vary greatly. This also holds true for very wide, single column left justified text, where the eye will need to travel much too far from the end of one line to the next.
The considerations of line length can and often do get lost when basing an entire layout on a Mobile single column visual structure.
3. As a designer, you always seek to reduce, never add.
All design is largely a process of reduction, to arrive at an ideal level of necessary detail. Never more than what is needed. In the process of reduction, it is easier to determine when you have gone too far, and you have lost cohesion. In the process of addition, however, you are always tempted to add more, even when that is unnecessary. It is generally easier to determine what is not enough as opposed to what is too much.
Designs generally need to avoid clutter. Composition and overall visual cohesion requires that shapes and visual structures are shaped and whittled down from a greater whole, not by adding multiple smaller components together and build outward.
You don’t build a house brick by brick – you need a blueprint first, to ensure that all spatial considerations and proportions are weighed before they’re locked in, and create possible dependencies. If you don’t resolve such dependencies on the planning stage, when you lay out the entirety of your design, you may find that you’ve painted yourself into a proverbial and sometimes quite literal corner, when you’re exposed to the actual, full size and proportions of that which you’re designing.
4. As a designer, you always consider visual patterns, repetitions and rhythm, in order to assess if elements are given sufficient contrast to guide the eye, or if the content is rendered too repetitious.
On Desktop, this is a necessity, to ensure you’re creating both cohesion/adherence and contrast across a larger space of which elements are a part.
On Mobile, you don’t see enough of the design in one glance to achieve that overarching balance: a section can be over- or under-emphasized compared to another, but because you don’t see them together, you can’t make that holistic assessment.
5. As a designer, you always want to spend the majority of your design time upfront, to ensure that you’re not hit with any unforeseen delays later on.
What needs the most time to design is what you should start with, so that finishing the design is less time consuming, and can be given an accurate commitment date with increasing precision.
Given the added horizontal dimension, Desktop layouts are almost unequivocally more complex than Mobile ones.
The more complex issues you leave for later, the harder it is going to be for you to accurately predict when you will be done, and you may even find at the very end that complexities have compounded to such a degree that you need to start over, to rework the layout.
Delaying all these critical design decisions, if you hold off on fleshing out the Desktop view until last, only kicks the can down the road.
Design thinking is not:
- A new way to design things
Design thinking is:
- Thinking about business through the lens of design
Design Thinking is not the same as the act of Designing.
Design thinking means applying design as a methodology to work through strategic issues in a clearer way.
Design thinking means using design to organize and visualize thoughts.
When thoughts and ideas are properly visualized, they are much clearer to everyone involved, and much easier to have concrete discussions about.
They are also easier to iterate productively on.
Each update to the visualization of the thought, the idea, or the organizing principle, means the update has a tangible outcome, and is easier to quantify.
In that sense, Design Thinking can very effectively bridge the gap between Strategy and Execution.
As a side note: when people say: ”I’m a visual person”, what they typically mean is that they are visualization deficient. They are unable to see for themselves what you are describing, and need YOU to visualize it FOR them.
(A truly visual person would be able to visualize something without paint-by-numbers instructions).
So, what people really should say is: “I can’t visualize this. Can you show me?”
And what you would apply in order to do this is (you guessed it):
Because you’re helping them to think about a concept through the use of design.
You’re helping a group of often visualization-deficient people process their thoughts collectively by feeding those thoughts back to them in visual form, and thereby helping them be more deliberate and effective.
And that is much more than a buzzword.
Never just create a one-off asset when you can construct something reusable
Never just create a reusable single template when you can design something modular
Never just design modular components when you can devise a framework
Never just devise a framework when you can architect a design system
Never just architect a design system when you can define a user experience
Never just define a user experience when you can plan out a user journey
Never just plan out a single user journey when you can improve lifetime value
One of the most stressful and painful experiences in my professional career has been to watch up-close the attrition of valuable experience and the dissipation and squandering of considerable, hard-earned intellectual capital, because of passive handwringing and a mystifying unwillingness to lead.
Immense value is lost simply because people in leadership positions simply will not stand up and assert ownership of the disciplines which are under their stewardship, or step up and drive from a position of real and tangible subject matter expertise. Such delicate assets are so very easily lost in the cracks of, or ground to dust by, the wasteful and inconsiderate machinations of corporate politics.
Ultimately, the biggest responsibility of business leaders is to realize, champion and harness the capabilities of the human capital placed under their control.
A failure to own this responsibility is nothing short of a betrayal of the promise that talent brings.