Redesigning Something? Two Questions to Start With


“Have we measured this, and if so, what does the data tell us?”
“Have we talked to our users?”

If you’re redesigning something, whether it’s a simple feature or your entire site or app, you need to start with these two questions.

Both of these questions are designed to stop you in your tracks, and make sure you’ve got the evidence you need before you start working to redesign something. Redesigns take time and money, and you shouldn’t do it based on gut - you need evidence.

It’s easy to come to the conclusion that you need to do some kind of redesign. Either something doesn’t feel like it’s working right, you’re just tired of the current approach, or something else has cropped up that makes you uneasy. The problem is, going with your gut can cause a few problems, not the least of which is the fact that more often than not, your gut is wrong.

By starting with these two questions, you do two things. First, you slow down the process, and prevent yourself from acting reactively, which allow you to evaluate if a) you should actually do this, and b) if you do, what the best approach is.

Secondly, asking these questions lets you set a starting point, a beginning state, on which you can measure the effect of the redesign. If you know your current conversion rate, or average transaction amount per sale, then you can compare your redesign work against those benchmarks, assuring that your work has actually improved the condition, not worsened it. The same goes for talking directly to users - understanding their experience now can be measured against how they talk about their future experience, giving you a feeling for how successful the change was.

It’s easy to jump in and start changing things, based on your intuition and gut. You get a feeling that something needs to change, and rush right in to start fixing it. Next time, try stopping and answering the two questions above (to which the answers should be “Yes”). You’ll end up with a much more pointed redesign effort with real measures that can help you gauge effectiveness.

Never forget, sometimes, the answer to “How should we redesign this?” is “We shouldn’t”.

Related Posts

Review: Keto Diet

I recently gave the Keto (Ketogenic) Diet a try. Suffice to say...it works.

You Don't Need to Get it All Correct Immediately

Too many people wait on shit to be perfect. Get it close, leave out some stuff, and set yourself up to quickly iterate.

Using Foundation 6 in Angular 4 (or 2)

How to use Foundation for Sites 6 in Angular 4 (or any version 2+)

Great Products Need Great DevOps

In the quest for shipping great products, DevOps is often overlooked, and that's a mistake

How I Increased my Water Intake by 500%

We all need to drink more water, but it's hard to get in the habit. Here's a simple trick I used to get a 5x improvement on my intake.

Three Secrets That Made Cutting The Cord Easy

After decades of being attached at the hip to cable, I finally cut the cord, and it's been amazing. Here are three secrets that helped me get the most of it.

How to Onboard a Product Designer

If you're bringing a product designer or UX designer in to help you design your product, there's a bad way to do it, and a good way to do it. Here's how to make sure you're doing it right.

Review: Slicing Pie

Slicing Pie is a new way to think about company equity splits, and it blows away the old methods you've probably used.

When Troubleshooting, Follow the Process!

When you're trying to troubleshoot something - a car that won't start, or a business that isn't working - follow the right process.

The Art of Finding a Way

Being resourceful and relentless is one of the keys to being successful (and a great shipper). When in doubt, find a way.