UX Collective

We believe designers are thinkers as much as they are makers. https://linktr.ee/uxc

Follow publication

Journey

Delivering your work in layers

Getting used to sharing work in progress to make more efficient design decisions.

Fabricio Teixeira
UX Collective
Published in
3 min readJul 3, 2018

--

Illustration: Floortjes Artwork

Here is something I have learned in my career that has improved my efficiency quite a lot — and that whenever possible I pass on to the designers I work with:

Do your work in layers.

Not talking about Photoshop or Sketch layers. I’m talking about fidelity layers.

Some designers like to work on a product piece by piece.

They focus on one screen or feature at a time, and dedicate full days of work trying to make that one piece look as polished and finished as possible. Before sharing it with the rest of the team, they make sure visuals are pixel perfect, elements are precisely aligned, imagery and copy are as close to final as possible, and that they actually prototype how the elements in screen will animate together.

And they never share their designs with the rest of the team until they feel extremely confident about the work.

But those things take time.

Here are a few inherent risks with that approach:

  • The rest of the team is not aligned on what that particular screen should look like, from a visual perspective, and that might end up affecting their perception of the entire product idea.
  • The rest of the team is not aligned on how that screen will fit into the larger product structure. Their feedback will require you to go back to the drawing board or change the design quite structurally.
  • The rest of the team will be unable to fully agree with that one screen without understanding the rest of the flow.
  • Even if the team is onboard, when the designer moves on to the second screen, future decisions will largely impact the first ones. That high maintenance effort will progressively increase as new screens are designed.

In retrospective, the designer has spent a big chunk of the project timeline crafting one screen in isolation.

It doesn’t matter how important that screen is.

It doesn’t matter it’s the homepage.

That screen is always going to be part of a larger flow.

And that flow is always going to be part of a broader design system.

In 1 minute, you have a pretty good idea of what that nose will look like; illustration by Floortjes Artwork

Instead of spending two entire weeks designing the same screen and trying to turn it into a completely finished product, what if you tried to deliver your work in layers?

You can start from defining a conceptual model for your product.

Or from sketching out a navigational framework (quick and dirty wireframes of what each section of your product is going to look like).

Or from picking one key user flow in your product — the most important one from a business and user perspective — and taking a quick pass at designing a sequence of screens that people will experience.

It doesn’t matter where you want to start. But do it in layers.

Share your progress every day.

Every couple of hours even.

5 minutes might be enough for people to understand where you’re heading; illustration by Floortjes Artwork

One of the biggest benefits of that approach is keeping a birds eye view on the entire product, not just a single screen.

If your stakeholders, your manager or your client wants to see where you’re at, you will never have nothing to show. There will always be enough work to look at and trigger a fruitful discussion about. There will always be time to course-correct your designs. There will always be time to adjust the project plan to fit your designs.

Trust your peers. Get used to sharing work in progress. If they are smart, they will understand you’re not sharing something unfinished because you’re incapable of finishing it; you’re doing it because you’re senior enough to understand how to better utilize your time.

Your manager will appreciate it.

This article is part of journey: stories about the amazing ride of being a designer.

--

--

Responses (14)

Write a response