The org member list used to load users one at a time — every member on the page triggered its own database call. If you had 50 people in your org, that's 50 separate round trips. Now it batches everything in one go. Pages with large member lists load noticeably faster.
Member list errors now explain themselves. If the list fails to load, you'll see why — and get a retry button instead of staring at a blank screen.
Drawers that open before data arrives handle it gracefully. The teams drawer no longer flashes stale state if you open it mid-load. It waits for fresh data and offers retry if the fetch fails.
