Choose the people.
I reviewed hundreds of résumés and handpicked the designers who joined my team.
← SELECTED WORK / 03KEARNEY / DESIGN LEADERSHIP & DATA VISUALIZATIONFrom requirements
From requirements
to a product
people can see.
Leading Benchmarking from discovery workshops to enterprise interfaces—within three years of building and developing the design team at Kearney.
Explore the Benchmarking story
From data scattered across teams to information consultants can work with.
A team I built.
A practice
we developed.
I built the design team and stayed involved from the beginning of both projects.
Across three years, I handpicked designers from hundreds of résumés, trained them, and led their work on enterprise products.
My contribution connected people and product: building the team’s capability while working through complex business requirements from discovery onward.
Grow their capability.
I trained designers throughout my tenure, developing the team through its work on enterprise products.
Connect the work.
I led the team across SAP, Power BI, Salesforce, and custom dashboard design assignments.
02 / FLAGSHIP STORY · BENCHMARKINGMake the problem visible.
Make the problem visible.
Then design the product.
Benchmarking brings my hands-on workshop practice, design management, and enterprise product work together. Supplier Prism extends that wider practice.
01 / COMPARE DATABenchmarking
Spend, price, and savings comparisons for consultants.
02 / CONNECT INFORMATIONSupplier PrismSupplier discovery, evaluation, and collaborative updates.
01 / PROCUREMENT INTELLIGENCE
Benchmarking
Bring spend, price, and savings comparisons into one place.
The product challenge
Consultants depended on spreadsheets and exchanges with colleagues to assemble procurement comparisons. The product consolidated those comparisons into a shared application.
Why I brought people together
Requirements arrived through presentations, PDFs, and conversations with different stakeholders. Those inputs described parts of the problem, but a collection of documents was not yet a product structure.
My role was to bring that material into a product design process. I introduced workshops and visual thinking as a way to explore the experience with the people contributing to it, alongside my responsibility for leading the design team.
My intervention
I conducted a three-day client workshop in Bangalore with Kearney colleagues and client participants who travelled from Mumbai. The first two days focused on discovery and project requirements. On day three, frontend and backend development leads joined us to discuss technical feasibility.
The design challenge
The product served consultants, data contributors, administrators, and subject-matter experts. The design needed to account for how information moved between these roles, alongside the comparisons consultants would use.
The screens below make that scope tangible: consultants explore benchmarks; power users contribute data; administrators coordinate normalization and review; and subject-matter experts inspect the information. The story is about designing that connected experience, as well as the individual dashboard.
BENCHMARKING / CLIENT WORKSHOP · BANGALOREThree days.
Three days.
One shared
understanding.
I conducted the workshop in Bangalore, with Kearney colleagues and client participants who travelled from Mumbai. Rather than treating requirements and implementation as separate conversations, the three-day agenda made room for both.
- DAYS 01–02Discover the requirements.
The first two days focused on discovery and project requirements. I facilitated the conversation with Kearney colleagues and client participants, using the workshop to work through the material together.
- DAY 03Discuss what is feasible.
On the third day, frontend and backend development leads joined us. We discussed technical feasibility alongside the requirements, bringing the implementation perspective into the early design conversation.
A product experience
across four roles.
The resulting screens show how comparison, data contribution, administration, and expert review fit into the same application.
Start with people and requirements.
The workshop brought client participants and Kearney colleagues into discovery, with frontend and backend leads joining for the feasibility discussion.
Make responsibilities visible.
The interfaces distinguish the consultant’s comparison tools from data uploads, administrator coordination, and SME review.
Stay close to the work.
I combined hands-on facilitation with recruiting, training, and leading the design team. Benchmarking is one example of that practice.
My contribution connected discovery, technical discussion, and product design—while developing the team doing the work.
BENCHMARKING / PRODUCT SCREENS
One product. Different responsibilities.
Explore the interfaces for comparison, contribution, administration, and expert review.
Consultant
Compare spend and explore benchmarks.
Portfolio copies · Headers, identifying details, and sensitive data obscured.
02 / SUPPLIER INFORMATION & COLLABORATION
Supplier Prism
Give supplier information a shared home.
The product challenge
Supplier information was spread across offline files, making it difficult to keep records current and coordinate updates. Supplier Prism brought supplier discovery, evaluation, and information management into a collaborative platform.
My contribution
I combined design management with hands-on work from the beginning. I conducted workshops involving client-side participants and frontend colleagues, bringing their input into the project alongside my leadership of the design team.
The leadership lens
The work brought together two related needs: helping consultants find useful supplier information, and supporting the administration and approval of changes to that information.
03 / THE SYSTEM CONNECTING THE WORKKearney Activate.
Kearney Activate.
Built to keep evolving.
A shared design system I designed and developed with the team as new projects introduced new needs.
Each new project added to the system. Each addition became something the next project could build on.
Repeated component creation across Kearney products prompted a reusable system. We continually added components, design tokens, colour, and guidance as the work evolved.
During remote working, we moved from Sketch and InVision to Figma. I partnered with a frontend colleague to connect the design library with tokens, CSS classes, and code snippets.
One visual language.
Colour, typography, and tokens established a shared starting point.
Reuse, then extend.
New project requirements became new components and additions to the library.
Design meets code.
Implementation guidance helped designers and developers work from the same system.
The value was in maintaining a shared foundation while giving each product room to grow.
04 / POWER BI PRACTICE & COMMUNITYMade for my practice.
Made for my practice.
Shared with everyone.
Beyond the client projects: a reusable resource I created for designers working with Power BI.
POWER BI CHARTS / BY SARAVANAKUMAR KLess rebuilding.
Less rebuilding.
More designing.
I created and published a Power BI chart kit on Figma Community to support dashboard prototyping and the visual consistency of analytics experiences.
It brings chart patterns together in a reusable design resource, helping designers explore data experiences without starting each chart from scratch.
8.2kFigma Community users
153Community likes
Counts displayed by Figma Community · 20 October 2026
Explore my Power BI chart kit
VIEW CHART LIBRARY ↗THE PRACTICE BEHIND THE KITDesign for decisions.
Design for decisions.
Work with the platform.
My Power BI work spanned fintech, insurance, and large-data applications. Its constraints called for an approach tailored to the platform.
- Different people, different depth.
- Summary views for senior leaders, deeper exploration for executives, and actionable information for consultants.
- Prioritize what needs attention.
- Surface the information that supports immediate decisions, with room to explore further.
- Keep feedback in the process.
- Use Miro to organize requirements, gather stakeholder comments, and review with developers.
- Consider the whole experience.
- Balance chart clarity, navigation, filtering, and responsive interactions with the demands of large datasets.
Across platforms.
Across
industries.
The team supported designs for SAP, Power BI, Salesforce, and custom dashboards.
Our client work included organizations across banking, technology, aviation, retirement services, and life sciences.
Bank of IrelandNTTAustralianSuperLufthansaMerck
Clients listed reflect work during my tenure; they are not assigned to individual projects in this collection.
Design leadership
is also about the people
doing the designing.
Building the team, developing designers, and connecting their work across enterprise products are central to my contribution at Kearney.
Let’s talk about design leadership ← BACK TO SELECTED WORK