08/25/2024 | News release | Distributed by Public on 08/25/2024 20:57
It's deadline day.
Users who have not moved to the new log-in system cannot access Podme services. They must follow the on-screen instructions to transition to the new system.
This affects about 70,000 users. While this seems low compared to our 1 million users, it becomes significant when senior management reports they received e-mails about the new log-in system but got stuck in a loop when clicking the provided link.
The team at Podme thought it had considered all possibilities, but there was still a hiccup that needed to be resolved.Let's take a step back: Exactly 30 days ago, we released an update on our Web site and apps urging users to start using the new log-in system. They were also given a deadline in the app, but that's how deadlines work for humans, isn't it?
As a project manager, I believed we had covered all bases, especially with the planned e-mail communication. I expected we would transition 50%-60% of users, acknowledging there are always inactive users and late adopters. We were all set to launch and succeed!
What happened?
The flow worked on the Web and in the app as intended. However, when users clicked the e-mail link, the only thing they got was an anti-climactic state of an infinite spinner.
But we tested everything before the launch, right? Yes, we did. We tested the flow on the Web and apps, and we did integration tests. We tested the e-mail link, and it directed us to the screen where the Web flow initiates. It was the same link we agreed on with the marketing team.
Everything seemed in place … but was it? After digging through the code and multiple scenarios, and almost on the verge of deciding to roll back, we found the culprit. The e-mail link!
What we had missed was testing the entire flow from the e-mail. While the e-mail link did initiate the Web flow, the moment the user clicked on the preferred log-in method, the screen went into an infinite loop.
For my tech nerds, the problem was that our Web recognised the suffix as a routing parametre, which obviously had no page mapped leading to an infinite loop. Eventually, we fixed it. I love my team for their perseverance on this.
Surprise, surprise!
While the marketing team and I discussed the link to be added, we never discussed what happens when it's in an e-mail. The customer relationship management (CRM) programme we use to send e-mails adds a tiny suffix for tracking. It was routine for the marketing team and for us, but together it created an issue.
While we quickly resolved the issue and it sounds petty, it could have meant users wouldn't be willing to try it again. So, a petty-looking issue could have become a huge pain.
While this wasn't the only challenge in moving our users to a new log-in system (I'll perhaps write many more learnings from this project), it provided a significant learning experience.
Test the flow from all platforms, end to end, even from an e-mail that appears to use the same URL as the Web/app flow.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bhawna Gulati is product manager at Podme in Stockholm, Sweden. Bhawna can be reached at [email protected] or @bhawnabhanu.