Published on | Prototyping: From UX to Front End — Medium UX Boot Camp

#29dayUXchallenge[Day 29]

Photo by Matt Duncan on Unsplash

It’s day 29 of the #30dayUXchallenge and we can’t describe how grateful we are to have you sharing this journey with us!

As any other Agile project in its own UX Cycle, the 30 day challenge was obviously a Minimum Viable Experience for a project that has been living in our hearts for a while.

From here, we will do what we would with any other project.

So let’s take it as an example of what happens after we ship our very first iteration of the project:

We observe.

We talked to a few people before starting, we had some insights from our users and we executed the project with the resources we had on top of our full time jobs. It was a big challenge already! Since then, we have been observing the community response’s and feedback.

From now, we will gather all this “knowledge” and we will then…

Reflect.

We will analyse what worked well and what didn’t (and a few things didn’t!).

We learned by making some mistakes, keeping track of feedback we received from the community and improving as we were creating — but we couldn’t improve on everything due to our lack of time. How does that sound for an MVP? Pretty realistic, right? 😂

Now we need to consolidate this knowledge and to understand, based on that, what can we do the increase the value of the 30 day UX bootcamp to our readers?

And then, prioritise.

From these big ideas, we then need to understand how much effort each one would require, what can we actually deliver? Do we have time? Do we have resources? Do we have the tools?

And then we keep going. One step at a time. Or not, actually. As we mentioned on day 28 (UX Documentation), we are rarely working on one thing then suddenly stop to work on another. Projects overlap and as we are delivering work on one thing we are often in the exploration phase of another.

So here are some takeaways for your next steps:

Refresh user research. Don’t rely on old personas and research. Leverage it, but update it. Things could have changed. You learned. Your user grew up. What needs to be updated?
Review your data insights to see if new problems or insights are emerging. Technology is changing, there is a new player in the market or a new tool in the industry… What needs to updated (yep! again!)?
Go back to your overall strategy, what did you have to de prioritise over a more important problem at that time? What can be done now? What worked well and what didn’t? What do we need to prioritise now?
Measure the impact of implemented concepts over time. Are we getting more positive feedback? Does conversion improve as new features are added? Is usage time growing? What are the indicators that the product is on track with our users needs?

Basically, start the cycle again as if a new project is just starting. And keep going. After all, that’s the magic of the UX Cycle, isn’t it?

But, wait. It is a 30 day challenge.

What about tomorrow?

We left the best part for day 30, of course!

We believe this challenge will be even more powerful if UX enthusiasts are able to act on it too, so we want to dedicate tomorrow’s post to UX Portfolios and how to make it 💥 !

Ps.: It’s valid for you too if you are like us and you only dedicate time to it when you are looking for another job 😅.

See you tomorrow?

<a href="https://medium.com/media/8d5e2c740a04faf463af9accfa7e3c31/href">https://medium.com/media/8d5e2c740a04faf463af9accfa7e3c31/href</a>

This post is part of the #30dayUXchallenge: you can read more about why we started it here, and don’t forget to follow us on Twitter and Instagram!

Starting the UX Cycle again was originally published in Prototypr on Medium, where people are continuing the conversation by highlighting and responding to this story.

Starting the UX Cycle again

Cool stuff, every week

More Articles