I am a Strategist from India, here to tell you my story!
Every professional achievement in my life is closely connected with my personal journey. And I believe it is very important that you know that story.
To that end, I can either write a well-crafted long-ish paragraph about who I am, OR I could just show you my Journey Map and Personal SWOT Analysis below.
You can always chat with me more here:
naisargi.shah18@gmail.com
Menu
CLIENT ENABLEMENT
LANDING PAGE (TS NEXT)
No Unified Entry Point
Users juggled multiple URLs, separate logins and disconnected systems daily
Green Screens Sunsets
Legacy green-screen access was phased out with no coherent replacement in place
Role-based Experiences
No single, role-based view of the tools and solutions relevant to each user
No Shared Vision
Every product domain had its own idea of what a landing page should be.
Lack of Collaboration
Product, technology and business units were working in silos.
No Single Leadership
No single owner of the overall client experience lead to lack of accountability.
Team Alignment
Align the team on what the Landing Page was, who it was for, & what it needed to do, bringing clarity to a problem that different teams had been interpreting in different ways.
Human-centered Process
Identified and prioritised personas, studied primary user scenarios and primary tasks to ground decisions in real user needs, not technology limitations or assumptions.
Landing Page Committee
Established a governance structure, where none existed, with representation across 12+ domains. Turning competing priorities into a single, aligned direction and vision.
Design Process Begins
Only once alignment was reached did we begin the design process: creating journeys, service blueprints, flows and wireframes with research-based iterations.
Design & Business Goals
Facilitated weekly workshops to define guiding principles and guardrails, review progress, ensuring design decisions aligned with business goals, turning outcomes into clear product requirements.
Consistency & Agility
Maintained alignment across teams for 2+ years, ensuring every design decision traced back to the agreed principle, enabling agility throughout a long and complex initiative.
Personas and Design Principles
We identified all potential user types across the organisation and prioritised BAU agents as the primary persona as their need for the widest access across clients, products and environments meant that designing for them would scale to everyone else. Stakeholder interviews and MoSCoW workshops informed the beginning of a feature set.
Both user types had one fundamental need: everything in one place, single sign on, no switching. The fragmentation of task on various screens became the primary problem.
Established through committee workshops, these principles governed every design decision across the platform.
Single-Sign on Across All Domains
Security and access are handled behind the scenes, users access what they need based on role, without repeated logins interrupting their workflow.
Most challenging (& non-negotiable) aspect. Shaped the entire access and authentication architecture.
Role-based Entry Point
Users access the platform through different entry points.
Personalized, unique experiences.
Contextual Navigation
Users should always know exactly where they are across clients, portfolios and environments, with navigation that is clean and clear.
Drove the decision to build persistent, hierarchical navigation throughout the platform.
Access without Friction
Users should never have to drill too deep. The platform prioritises breadth of access over depth of hierarchy.
Became the rule that governed every IA decision.
Consistency across Systems
Each application follows a consistent dashboard structure, the actions available at each starting point remain the same.
Reduced cognitive load and training time across products.
Brainstorming and Navigation (FVP)
We began with design the FVP vision, designing the ideal experience without technical constraints. This gave the team a north star to work toward, and a clear basis for the decisions made when we scaled down to MVP.
Exploring different entry points for different user-groups.
Sketching the layout, features and abilities in an in-person conference with all 12 domain leaders and product teams.
Exploring the layout and content. The screens shown here focus on the homepage. Supporting screens including solution page, configuration access, and customization abilities were also designed.
Role-based Access and Authentication
(the most complex challenge)
Role-based access is deceptively complex at scale. Each user type required a defined permission set governing what they could see, do, and access, across multiple products, clients and environments. Multiply that across dozens of role combinations and the matrix becomes enormous. SSO had to work seamlessly across all of it, without exposing users to the underlying complexity, and until that architecture was agreed across security, product and engineering, core design decisions couldn't be finalised.
Personalization vs. Consistency
Users wanted the ability to customize their view, like favourites, recently visited, quick-access links, but the platform also needed a consistent baseline experience across roles. The tension between personal preference and organizational consistency became a recurring design challenge.
Environment First
Workshop feedback consistently revealed that users think in environments before they think in products. The platform needed to surface environment selection earlier in the experience, not bury it within product views.
Defining the Vocabulary
A recurring source of confusion was the distinction between Solutions vs Products, and between cloud vs on-prem. Establishing a shared vocabulary across teams was a prerequisite to designing a coherent navigation structure.
Wireframe Iterations and Testing (FVP)
Our primary persona changed from Bob (internal BAU) to Claire (client BAU) to align with larger organization priorities.
Transitioning from FVP to MVP
FVP workshop feedback set the scope. What was technically feasible, what systems existed, what teams could deliver...all of it surfaced through the FVP process and fed directly into MVP decisions. Feedback from domain leaders, product, and engineering surfaced the technical and organisational constraints that shaped MVP scope.
Every feature was mapped across Phase 1 MVP, Phase 2: Fast Follower, Phase 3, Future State, and dependencies, before a single UI decision was handed to the development team. Three decisions from that process shaped the platform most.
Excerpt from the Feature Prioritization Matrix.
Supporting Artifacts and MVP Roadmap
Two supporting artifacts were created alongside the design process.
Service Blueprint: Aligned backend teams: engineering, product, & operations, on how the platform would actually be built and who owned what.
Client-facing Journey Map: Gave sales teams a tool to communicate the platform's value to clients during the rollout period.
MVP Hi-Fi Prototype
Following rounds of internal demos and stakeholder feedback, the hi-fi prototype was built on TSYS's existing design system, resolving what the MVP left open and translating months of organisational decisions into a production-ready interface.
Where TS Next Stands Now
(As of April 2026)
DEVELOPMENT COMPLETE. PRODUCT / SOLUTION ONBOARDING NOW.
The Landing Page (TS Next) is in its final pre-launch phase: development is complete and product teams are actively onboarding content onto the platform.
The MVP ships with three live products, a focused navigation structure, and a foundation model built to scale as additional products are added. SSO authentication is live, giving clients seamless access to work across various tools. Reporting, analytics, and other data-dependent features are planned for a subsequent release.
IMPACT
This was a systems design problem as much as a UX one. Before TS Next, clients had no single, unified entry point to access and operate their cloud-enabled products: they navigated fragmented URLs, separate logins, and disconnected systems daily. TS Next closes that gap: a role-based, SSO-enabled workspace that brings the right tools, products, and environments together in one place, for the right user, without friction.