Sponsors often open a rebuild conversation with screenshots. The homepage looks dated; the mobile layout frustrates members; a competitor launched something cleaner. Those observations matter, but they rarely describe the failure that will stop a cutover.
In several Bangkok programmes we have seen the same pattern: a portal can receive a new front end while still depending on a brittle login path shared with an older claims or billing system. When that path fails during peak season, the new homepage is irrelevant. Users cannot reach anything.
What to inspect first
Ask for a walkthrough that starts at unauthenticated entry and ends at a completed authenticated task. Note every redirect, every cookie assumption, and every vendor library involved. If that path cannot be explained by one owner, identity work belongs early in the rebuild sequence.
What can wait
Visual redesign, content reorganisation, and non-critical self-service features can often sit in later phases once identity and session recovery are stable. Programme boards sometimes resist this order because it is less photogenic. Document the risk in plain language: a pretty portal that locks members out during renewal week is a larger reputation cost than a delayed redesign.
Practical next step
If your team is arguing about homepage concepts while login incidents remain open, pause the visual debate long enough to commission a short architecture look at authentication alone. Portal Riverpoint’s assessment work frequently begins there for exactly this reason.