I find the users your research missed, name the design decisions that pushed them out, and give your team the tools to stop doing it.
I'm Manu Kaligotla. I've spent a decade studying the users who exit silently — the ones who never complain because they never expected to be considered. I turn that into frameworks your team can actually use.
When someone has to work around your product just to use it — translate the language, explain the error, find another way in — that's exclusion. It's costing you retention, trust, and revenue you never tracked.
I call it the Adjustment Tax: the invisible work excluded users do just to get through an experience designed for someone else. Most teams never measure it. Some never even see it.
It shows up as drop-off you can't explain, support tickets that say "I don't understand," and customers who leave without a word.
With AI in every product touchpoint now, the teams who get this right will build things that actually work for more people. The ones who don't will keep wondering why their metrics look fine but growth is stalling.
The Design for Belonging course gives you eight modules of frameworks, toolkits, and decisions you can apply in your next sprint. Not awareness-raising. Actual methods you can run on Monday.
Explore the Course →I embed as a fractional research leader and show your team specifically what's being missed — in your product, your research process, or both — and build the systems to fix it.
Start a Conversation →I've spoken at SXSW and AI conferences, and run workshops where teams leave with four frameworks they can apply to live product problems the same week.
See Talks →Developed across a decade of practice at Meta, OpenAI, Amazon, and U.S. Bank. Each tool is built to answer a specific question your team is already asking — and produce an output you can act on.
Run this before a major release to find where your product is quietly asking non-default users to do extra work just to participate. It surfaces the friction your satisfaction scores will never catch.
A systematic method for identifying the exact moments in your product where specific user populations drop off, give up, or get it wrong. You get a prioritized fix list your team can start on immediately.
A protocol your team runs before copy goes live — on error messages, onboarding flows, defaults, and labels — to catch the language and logic that signals "this wasn't built for you."
A pre-launch check that tells you whether your product communicates consideration to users outside your primary persona. Combines behavioral research, accessibility review, and ethnographic insight into one clear answer.
This isn't a course about awareness. It's a course about methods. Each module gives you a tool you can run on your actual product, with your actual team, in the next two weeks. Built for researchers, designers, and PMs who are done waiting for inclusion to become someone else's initiative.
Join the WaitlistI teach Inclusive UX Research at the graduate level. I spoke at SXSW 2025 on exactly how exclusion shows up in product metrics — and what it costs. I write Adjustment Tax, a Substack newsletter read by researchers and product leaders who want inclusion to be rigorous, not performative.
I built this course because every team I've consulted with already knows inclusion matters. What they don't have is a repeatable method. This course gives you one — module by module, tool by tool.
The talk I gave at SXSW 2025. Covers the Adjustment Tax framework, how exclusion compounds into measurable product failure, and four tools teams can apply immediately after leaving the room.
Inclusion gaps in AI aren't values failures — they're evaluation failures. This talk makes the case for treating inclusion as a technical quality standard, and shows teams what better AI evaluation practice looks like.
Half-day and full-day sessions where your team brings a real product problem and leaves with a completed Adjustment Tax Diagnostic, Exclusion Map, or Belonging Audit — plus a prioritized list of next actions.
Whether you want the course, an advisory engagement, or a workshop for your team — reach out and we'll scope the right fit. I typically respond within 48 hours.