Worked withAtlassianTrelloPayPalInklingBoldiumKaiser PermanenteParkAssistCity of Oakland
Selected work.
Trello / Atlassian
Problem
Trello had to pivot from project management to personal productivity for 50M+ users — and the organization needed to act fast to get the new product out the door. Leadership was split over the new navigation — a bold design meant to signal the pivot, versus a traditional sidebar that played it safe.
Approach
As Trello’s Lead Researcher, Niranjan ran a comparative study that settled the design dispute, an SEQ benchmarking framework across six feature areas, and a three-wave JTBD program that mapped 33 jobs — the foundation for future feature and AI development.
Decision unlocked
Leadership approved a bolder navigation, new features shipped against a 5.5 SEQ usability bar, and the JTBD map became the roadmap’s shared foundation.
Bitbucket / Atlassian
Problem
Bitbucket was shipping AI features with no dedicated researcher and no picture of what developers actually needed from AI — or what would make them switch CI/CD tools.
Approach
As Bitbucket’s first dedicated researcher, Niranjan evaluated three live AI features with developers, developed AI Jobs to Be Done across the full development lifecycle, and tested different CI/CD models against GitHub and GitLab for desirability.
Decision unlocked
AI investment got a prioritized map, and the competitive strategy shifted toward standalone Pipelines and cross-Atlassian product AI competitors can’t replicate.
PayPal
Problem
PayPal’s Checkout team was working on numerous products with no research direction: Online checkout, subscriptions, guest checkout and developer integration.
Approach
Embedded across 10 product teams, Niranjan paired field research with in-lab usability testing to expose actual mental-model mismatch, and coached designers and PMs to run research themselves so research could get ahead of product roadmap.
Decision unlocked
Niranjan showed so much value as a researcher that the Checkout team approved the allocation of another headcount for research. Research became a core part of the Checkout team’s decision making.
Two ways to work with me.
WORK TOGETHER
Consulting
Research sprints and strategic advisory for product and founding teams.
Your team disagrees and the debate won’t end.Research sprints: moderated and comparative usability studies that settle it with evidence.
You’re making roadmap bets without knowing what customers need.Jobs-to-be-done research, personas and journey maps that become the roadmap’s foundation.
You’re unsure how to package, price or position against rivals.Switching-barrier studies, Kano-style questionnaires and competitive research.
Research depends on one person, or doesn’t exist yet.Charters, operating models and templates, plus coaching so your team runs its own studies.
You want a senior research voice without a full-time hire.Advisory: an ongoing strategic research partner.
Previously consulted with Boldium, the Oakland Public Ethics Commission, Kaiser Permanente and ParkAssist.
Three times now, I’ve been the first researcher in the room. At PayPal, I built research into a five-team payments organization that had never had one. At Atlassian, I did it again at Trello, growing the function from just me to a team of three, and then again at Bitbucket, where the open question wasn’t whether to do research, but how to aim it at AI. The pattern is the point: I build the evidence habit inside teams that have never had one, and I leave them able to decide well without me. That’s the work I now do with founders.
In the room with leadership
The rooms I work in are senior ones: executive staff, VPs, and Heads of Products and Design. My approach in those rooms:
Ask leaders about their skepticism, and understand their point of view
Turn the session into a conversation, not a debate
Never tell stakeholders they are doing it wrong; show them a better way, and how research gets them there
01
Confluence, Atlassian. The Head of Design doubted Confluence was ready to adopt its new navigation. My research showed users performing common tasks in the new design with ease, and it cleared the way for the launch.
02
Jira Work Management, Atlassian. Leaders asked why people were not using it and what features were missing. The real answer was not features: it was branding and packaging, and that finding helped Jira’s leadership merge two products into one.
03
PayPal. The ask was how to convince buyers to use PayPal when making online purchases. I reframed it: what can we show as valuable differentiators so buyers decide PayPal is the best payment choice? That turned a persuasion problem into a product question.
I’m a computer engineer by training, with a master’s in information management from UC Berkeley, where my qualitative research ran in close partnership with the Haas School of Business. That makes me a solutions-oriented researcher: I find satisfaction in seeing insights come to life as real changes that solve customer problems. So I hold my work to a practical standard. Foundational research has to be easily understood and actionable. Tactical research has to produce real changes to the product. And when I teach team members to run research themselves, it has to give them enough evidence to make an informed decision.
My work has ranged across: healthcare / government / parking logistics / education / team collaboration / personal productivity / developer lifecycle / finance.
I don’t just answer the WHAT, I also answer the SO WHAT and NOW WHAT?