Writing it. Creating a compelling, well written storey around what you achieved, that people actually want to read, is always hard.

I had this happen again today actually. I wanted to change my password on ring.com, as somehow the one in my password manager was out of sync. I tried 2 or 3 times first using the incorrect password manager stored credentials, then did a password reset via email, after which I was still locked out. Surely once a password reset has been confirmed the lock should be lifted automatically? Instead I need to wait an undefined period of time before trying again.

A lot of these decisions come down to how much friction can you afford introduce in order to enforce good security, relative to what you product is and how much value it delivers.

The rest of the UX outside of the locking itself comes into play, such as how do you unlock the account once locked, do you offer 2fa, what other details about a person to do you have to authenticate if they loose access to their registered email account, how much personalised support can the business afford to deliver, etc...

Its never a 1-size-fits-all answer and depends on the service, what it offers and what it's user expect.

Nice design and some good thinking behind it for a limited scope exercise. Be interesting to see if this scales to a version of the app with feature parody.

Trying a new longer form of case study, based around a recent project we undertook. A descriptive and open account of the project, our successes and failures, and how we came together as a team to solve some interesting problems.

Hoping others find this interesting, and also provide insight to any possible future recruits about what a typical large project looks like at MyBuidler.

Indeed. It's constantly shifting, which is why I was curious to take a dip test today, see where peoples heads are at...

Results are in. 52% were happy to work on a single product for a longer period of time. The rest where pretty evenly split between not liking the idea and being unsure. Intend to write blog post about this, I find it very interesting, especially as I'm recruiting a lot at the moment.

For one I'm very happy to see that majority Product Designers seem to relish the opportunity to iterate and improve a product (assuming there's enough interesting work to hold your attention).

Thanks everyone for your participation

Want to know where people stand on the 'Grow/iterate one thing' – 'move around and work on a wide variety' spectrum. I'll post the results back here.

Very much looking forward to speed improvements. The rest is a bit meh for our use case, but is this delivers on performance it will a very welcome update.

Does a good job of capturing Huge's personality. I'm sure their clients would recognise what they know & love about the company in it. I fear however few will get past the homepage as the navigation is completely undiscoverable. Bounce rate on the homepage must be sky-high. Have the nav open when landing and collapse on scroll.

Echo the dislike of scroll-jacking, but it makes the kind of big brand impact their clients will want to see. It has a limited target audience who they're trying to wow. Impressive speed!

Case study carrousels? Let me scroll please. One way ticket to ensuring most of your work is never seen.

I like how everything is HUGE :) Looks pretty gorgeous though.