Enterprise Feature Launch

Enterprise Feature Launch

Designing Intelligent Session Timeouts to Prevent Security Risks and Build Trust

For copyright reasons, the featured UI screenshots are mockups created to represent the actual product.

Company

Amazon Web Services

Role

UI/UX Designer
Frontend Engineer

Duration

2 Months

Tools

Figma
React
AI Design Tools

The Challenge

The Security Vulnerability

AWS Wickr users frequently forgot to logout when switching between tasks, leaving encrypted sessions exposed on shared or unattended devices. This wasn't careless behavior—it was a realistic workflow problem: users opened the app, worked, switched tasks, and never came back to logout.

The User Insight

Through interviews with 12 users at a government organization, I discovered: "I forget to logout when I switch to other work, then come back hours later." The problem wasn't negligence—it was task-switching. Users were focused on their work, not session management.

The Business Opportunity: Solving this created a dual win: close a security vulnerability AND create a marketable feature that differentiates Wickr in the enterprise messaging market.

The Process

Understanding User Behavior

My user research revealed a critical insight: users didn't forget to logout because they were careless. They forgot because logging out existed at the end of a mental workflow that never completed. The action flow was: open app → work → switch tasks → (forget the app exists).

Reframing the Problem: We couldn't rely on users to remember. We needed to automate logout while giving users agency over their session. This shifted the problem from "remind users to logout" to "automatically logout without creating friction."

Design Exploration: From Warning to Gentle Reminder

I explored multiple approaches to communicating session expiration:

01

REJECTED

High Urgency Alert

  • Red warning icons

  • Large, prominent countdown timer

  • Urgent messaging: "Session Expiring!"

  • Goal: Maximize urgency

Result: Users felt "scared" and "panicked." The alert created anxiety, disrupted workflow, and backfired on testing.

02

SELECTED

Gentle Notification

  • Neutral clock icon (not red warning)

  • Smaller, contextual timing messaging

  • Calm tone: "Your session will expire in 5m30s"

  • Goal: Inform without interrupting

Result: Users appreciated the calm approach. Same information, completely different emotional response.

Visual comparison:

Initial design — high-urgency

Revised design — gentle approach

The Insight: Security doesn't require anxiety. The best security is invisible—something that works reliably without creating friction or fear. Users responded better to a calm, informative approach than to urgent warnings.

Iteration 2: Designing for Edge Cases

After simulating user scenarios, I identified a critical gap: what if a user ignored the modal, then later wanted to extend their session before timeout?

The initial design offered no path forward. I proposed adding a menu affordance that let users check session status and extend their session anytime. This small addition transformed the feature from "something that happens to you" into "something you can manage."

Menu affordance enables ongoing user control over session management

The Solution

A complete session timeout system with three interconnected components:

Timed Session Policy

  • Configurable by organization admins

  • Automatic logout after inactivity

  • Enterprise-grade control

Expiration Warning Modal

  • Appears 5 minutes before timeout

  • Calm tone and messaging

  • One-click "Refresh Session" action

Session Management Menu

  • User can access session status

  • Ability to refresh or logout

  • Ongoing control, not just warning

Component Consistency

  • Used existing modal components

  • Works within Wickr design system

  • Simplifies implementation

Session Management Menu

  • User can access session status

  • Ability to refresh or logout

  • Ongoing control, not just warning

Component Consistency

  • Used existing modal components

  • Works within Wickr design system

  • Simplifies implementation

Collaboration & Execution

This project required close coordination across teams. I worked with:

Product Management

Validated business case and user need; prioritized timeline for fast execution

Engineering

Audited technical constraints; suggested component reuse to reduce complexity

AI Design Tools

Used internal AI tools to rapidly generate modal variations for exploration

User Testing

Validated the gentler approach with beta participants before production

AI Design Tools

Used internal AI tools to rapidly generate modal variations for exploration

User Testing

Validated the gentler approach with beta participants before production

Result: Complete design and implementation in 2 months, with zero critical issues during beta testing.

Outcomes & Impact

Beta Testing Results

  • 2 weeks with real users

  • Minimal design issues

  • Enterprise-grade control

  • Preferred gentle approach

Business Impact

  • Closed security vulnerability

  • new marketable feature

  • Built customer trust

  • Differentiated Wickr

Deployment

The responsive web design was successfully deployed to the Beta environment on schedule.

Measurement

The real win was enabling a use case that previously didn't exist: mobile web access to a critical communications platform.

Strategic Opportunity

Established a reusable pattern for implementing security-critical features in consumer-friendly ways—a capability that became valuable as Wickr expanded into regulated industries.

User Feedback

Users appreciated that the feature protected them without creating anxiety or friction. The calm notification approach was specifically praised in post-beta interviews.

Key Learnings

1. Security Doesn’t Require Anxiety

The instinct is to make security warnings loud and alarming. But the best security is invisible—works reliably in the background without friction. Users trusted the calm approach more than urgent warnings.

2. Edge Cases Define Complete Solutions

The initial modal solved the primary use case. Designing for edge cases (what if a user wants to extend? check status?) unlocked a complete feature that gave users control, not just warnings.

3. Communication is Design

The successful outcome was the constant dialogue between product, design, and engineering. Regular reviews and iterations ensured everyone's concerns were addressed.

4. Constraints Drive Creativity

Rather than seeing limits as obstacles, I leveraged them to be more thoughtful about reorganization and hierarchy. Best design often comes from working within boundaries.

3. AI Tools Accelerate Iteration

Using AI to generate multiple modal variations compressed brainstorming. Instead of starting with a blank canvas, I had starting points for discussion—freeing energy for critical decisions.

4. Constraints Drive Clarity

Working within existing modal components wasn't limiting. It forced creative information hierarchy and messaging choices rather than distraction with novel UI patterns.

Session timeouts are a thankless feature—when they work well, nobody notices. But when poorly designed, they create frustration or anxiety. This project taught me that the best product design solves real problems in ways that feel effortless to users.

The shift from "alarming warning" to "gentle notification" wasn't a compromise on security—it was a better security solution. Secure systems that users trust are more secure than systems that create fear.