Sprinklr · Leading by influence
Emergent to Structured
Moving design a quarter ahead across 11 PMs and two time zones, without a team of my own
On Sprinklr Insights, design was pulled in when the sprint started. Eleven PMs and their engineering pods in India worked to just-in-time plans, and the design leads who signed off our work were in the US. I had no reports and no formal authority. Over three phases I moved us from firefighting to planned work: Kanban with our program manager and a PM, problem-first PRDs, reviews built for another time zone. By the 26.1 release, every requirement was done before the sprint started, a full quarter ahead, and Insights had moved from Emergent to Structured on the UX maturity scale.
Build stayed where it was.
Design moved a quarter earlier.
Challenge
The Insights workstream ran in firefighting mode, with poor visibility into work in progress, priorities and capacity. Tickets described UI features, not the user problem behind them, so clarification meetings piled up and reviews waited on US hours. The job was to change design's role from the team that slows the sprint to a partner in planning it, without any authority to make that happen.
Impact
- 1 quarter
- Ahead: all 26.1 requirements done before the sprint
- 40%
- Faster design sign-off, on average
- ~40%
- Fewer clarification meetings, estimated
- 11
- PMs aligned, across core and AI pods
Collaboration
I was the Lead Product Designer on the Insights workstream, working with 11 product managers across the core and AI pods, their engineering teams in India, UX research, and design leads in the US. I had no team, so everything here was done by influence. Our program manager, a PM and I set up Kanban together; the design director, the US design leads and UX research each became part of the change.
Design arrived when the sprint did
The core problem was loss of context. Requirements, release planning and user stories all happened before design saw them, so we joined at execution and inherited decisions we couldn't question.
Weeks of planning without design.
Then everything landed in the sprint.
UI ticket arrives02
Clarification meetings03
Design starts in the sprint04
Review waits on US hours05
Late scope changes
- 01
Firefighting
Just-in-time planning left no room for strategic thinking or clear requirements.
- 02
No visibility
Nobody could see work in progress or real capacity, so delivery was hard to predict.
- 03
Time-zone lag
Sign-off came from the US, so every round of feedback waited on their hours.
From Emergent to Structured, in three phases
On Nielsen Norman Group's six-stage UX maturity scale, Insights was Emergent: design worked, but it was inconsistent, inefficient and pulled in late. No single fix would move that, so I worked in phases: earn trust by making delivery predictable, then raise the quality of what came in, then use the room we had made to shape the work.
We started at Emergent.
By the time I left, we were Structured, reaching for Integrated.
Stages: Nielsen Norman Group, the six stages of UX maturity
Phase 1: Changing the narrative
Design was seen as the team that slowed the sprint. With our program manager and a PM, I moved the Insights workstream to Kanban, sizing design work against development capacity so each release was scoped realistically. The board gave the design director real-time visibility of every workstream, with less time spent chasing updates. I also routed incoming work: I told PMs which designer suited the specialised AI tasks, and took the rest myself so the AI tiger team could stay focused.
Plan by capacity, not by urgency.
Illustrative board- 01
Predictable releases
Scope set against real capacity, before the sprint.
- 02
Live visibility
The design director saw every workstream without asking.
- 03
Less friction
The principal designer and the AI team could focus on long-term work.
Phase 2: From participants to partners
Requirements still arrived as UI tasks. I gathered the PMs and got them to adopt a Why-What-How PRD template, so nothing reached design without a problem statement, a user persona, a use case and clear requirements. In scoping meetings I reframed each ask around the why. Clarification meetings dropped by an estimated 40%, and development started sooner.
Reviews that don't wait for morning
For the US design leads, I split each Jira ticket into problem statement, use case and requirement, asked for feedback directly in Figma comments, left notes on the files, and posted a short summary in the Teams channel, so a review never needed a call. Sign-off got 40% faster on average. And I stopped treating the 11 PMs the same: topic and AI PMs got structured meetings, idea-driven PMs got informal working sessions, and with every one of them I pushed back early, as the user's advocate, so late-stage scope creep went down.
Before
Every round crossed the time zones again.
After
One crossing: the US leads had all they needed.
Illustrative: the shape of a review, not a log
Phase 3: A full quarter ahead
By the 26.1 release, every requirement was done before the sprint started: N-4, a full quarter ahead of where we had been. That headspace changed what design could do.
Before, requirements were still landing when the sprint began.
- 01
Questioning the requirement
The PRD treated an insight as one static item. I wrote research questions and took them to UX research, which confirmed the need for a multi-insight workflow.
- 02
Velocity on a flagship launch
I designed all four segments of the Use Case Hub and drew its illustrations to keep pace. It shipped on time, and the team won Sprinklr's CTO Award.
- 03
Aligning across teams
When the Action Plan module moved to the CFM team, I mediated the early disagreements on priority and scope, and it was built without major blocks.
What moved, factor by factor
NN/g measures maturity on four factors. Process moved first; culture followed once PMs saw that problem-first PRDs and planned capacity made their own work easier.
What moved, factor by factor.
Process first, then culture followed.
Factors: Nielsen Norman Group, the four factors of UX maturity
Colleague feedback
From the US design leads who signed off my work at Sprinklr, shared on LinkedIn.
He brings a strong systems-thinking mindset to design and is always looking for ways to improve not just an individual experience, but the overall product and design process. Ankur is the kind of designer who makes the team around him better.
Parker GindelePrincipal Design Manager, SprinklrAnkur combines strong product thinking with a collaborative leadership style. He builds alignment, facilitates productive discussion, and helps teams move from ambiguity to action.
Michelle BrannanPrincipal Product Designer
Looking back
- 01
Earn trust before asking for a seat
Predictable delivery in phase 1 is what got design into planning in phase 2.
- 02
Write for the reader who is asleep
An update someone can act on without a call is worth more than a meeting.
- 03
Maturity is a habit
Moving up a stage took shared habits, a board, a template and a review format, not a bigger title.