<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Himanshu Kalra</title>
    <link>https://himanshukalra.com/</link>
    <atom:link href="https://himanshukalra.com/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Writing by Himanshu Kalra — UX researcher and ex-architect in Bangalore.</description>
    <language>en</language>
    <lastBuildDate>Wed, 16 Sep 2026 13:52:48 +0000</lastBuildDate>
    <item>
      <title>Deeply personalised learning</title>
      <link>https://himanshukalra.com/writing/deeply-personalised-learning/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/deeply-personalised-learning/</guid>
      <pubDate>Sat, 04 Jul 2026 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;One thing AI has unlocked for me is deeply personalised learning. Multiple books/papers synthesized into one linear learning sequence - broken down into atomic notes, Q&amp;amp;A flashcards, quizzes - uploaded to netlify in a format readable across devices auto-saving my progress.&lt;br&gt;
If I am reading business advice, it is tailored to my unique goals and situation.  If I am learning with someone else, there is a scoreboard. Spaced repetition and active recall built into the format.&lt;br&gt;
-&lt;br&gt;
Used Fable as the manager+architect with GPT 5.5 (via Codex CLI) writing and Opus 4.8 reviewing - all coordinated through Claude CLI&lt;/p&gt;</description>
    </item>
    <item>
      <title>Learn and teach</title>
      <link>https://himanshukalra.com/writing/learn-and-teach/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/learn-and-teach/</guid>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;The core of a User Researcher&amp;#x27;s job boils down to two things: Learn and Teach.&lt;br&gt;
Learn about users. Teach what you&amp;#x27;ve learned to the builders and decision-makers.&lt;br&gt;
What makes a researcher effective at this? Here&amp;#x27;s a take:&lt;br&gt;
1/ Teach only some of what you learn - and do it strategically. No infodumping. Give people only what they need for the next decision. Plant seeds early for decisions that are still downstream.&lt;br&gt;
2/ Your students outrank you, and they didn&amp;#x27;t sign up for class. This is unlike any other teaching relationship. You&amp;#x27;re correcting and informing people with more power and organizational visibility than you. The authority you carry is only what they&amp;#x27;ve chosen to extend - which means you&amp;#x27;re always earning it, never holding it.&lt;br&gt;
3/ Expect disengagement - and learn to make anything interesting. The question is always: what does this particular person care about? How does what you found connect to the problem they&amp;#x27;re facing? If there&amp;#x27;s no connection, they probably don&amp;#x27;t need to know.&lt;br&gt;
4/ Repetition is how ideas move through organizations. Not by saying the same thing twice - but by returning to the same core insights from different angles, in different rooms, with different audiences over time.&lt;br&gt;
All of this requires genuine caring - for the people using the product, and for the people building it.&lt;br&gt;
Which makes the current moment genuinely hard. If you&amp;#x27;re worried your role will be automated away or treated as optional, if you don&amp;#x27;t feel safe pushing back - it&amp;#x27;s difficult to show up as a passionate teacher. It&amp;#x27;s hard to care well for others when your own footing is uncertain.&lt;/p&gt;</description>
    </item>
    <item>
      <title>It&#x27;s just an AI wrapper</title>
      <link>https://himanshukalra.com/writing/its-just-an-ai-wrapper/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/its-just-an-ai-wrapper/</guid>
      <pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;&amp;quot;It&amp;#x27;s just an AI wrapper.&amp;quot; Said like an insult&lt;br&gt;
Nobody looks at a drill and says &amp;quot;it&amp;#x27;s just a motor.&amp;quot; Nobody calls a fan &amp;quot;just a motor with blades.&amp;quot; But that&amp;#x27;s exactly what those things are.&lt;br&gt;
It&amp;#x27;s just that someone put the effort to figure out the grip angle. The speed settings. The cord length for a real kitchen. The noise level for a real bedroom. The switch placement for someone doing it one-handed.&lt;br&gt;
That work - the unglamorous, obvious-in-hindsight work of fitting a capability to a real human need - is what turns a technology into a tool.&lt;br&gt;
AI is the motor. Powerful, general, indifferent.&lt;br&gt;
The wrapper is what makes it useful to the person who just needs to get something done and doesn&amp;#x27;t care how the thing works.&lt;br&gt;
So yes. Wrap the model. But put the effort to understand your people.&lt;br&gt;
The moat lives in that intimacy.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AI changes the question</title>
      <link>https://himanshukalra.com/writing/ai-changes-the-question/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/ai-changes-the-question/</guid>
      <pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;Most security product research answers one question: can analysts find and triage an alert, run a query, or investigate an endpoint? Most mature products have solved this.&lt;br&gt;
AI changes the question. When an analyst dismisses an alert because the AI flagged it low-priority, did they evaluate it independently or accept the recommendation? Defer too readily and you miss what the model wasn&amp;#x27;t trained on. Ignore the recommendations and you&amp;#x27;ve bought automation you don&amp;#x27;t use.&lt;br&gt;
Both look the same from the outside - an analyst made a call and moved on. Neither shows up until something is missed.&lt;br&gt;
Research on human-AI collaboration has established methods for studying this - trust calibration, appropriate reliance, confidence elicitation - and applied them in clinical contexts. They haven&amp;#x27;t been applied to SOC workflows. AI triage platforms are scaling now. Radiology went through this - AI-assisted image reading raised the same question: when does the radiologist trust the flag, when do they override it? That&amp;#x27;s now an active research area with published methods.&lt;br&gt;
If security vendors are doing this work, they&amp;#x27;re not publishing it. Which means it&amp;#x27;s a competitive edge - or a gap. Probably both.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A reckoning with complexity</title>
      <link>https://himanshukalra.com/writing/a-reckoning-with-complexity/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/a-reckoning-with-complexity/</guid>
      <pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;One hopeful consequence of AI: it may force a reckoning with complexity. When you can generate a convincing argument for almost any position - and against it - the question &amp;quot;what is the right thing to do?&amp;quot; loses its clean answer.&lt;br&gt;
Do you take the flight to close the deal, knowing your company has a net-zero pledge? The carbon is real. So is the relationship that won&amp;#x27;t form over a Zoom call.&lt;br&gt;
Do you recommend the automation that cuts costs - and three jobs? Efficiency serves the many. Displacement lands on the few.&lt;br&gt;
Do you tell a colleague their leadership style is holding the team back? Honesty serves them. It might also just serve you.&lt;br&gt;
That discomfort - not knowing which side is right - might be the opening we need.&lt;br&gt;
A model of Human Development - Spiral Dynamics - calls this Stage Yellow: the ability to hold multiple valid frameworks at once and still make a call. Not that all answers are equal, but that all frameworks/models are contextual and should be held loosely, functionally.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Facilitating insights, not delivering them</title>
      <link>https://himanshukalra.com/writing/facilitating-insights-not-delivering-them/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/facilitating-insights-not-delivering-them/</guid>
      <pubDate>Thu, 20 Nov 2025 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;When generating insights becomes faster, the next frontier might be *facilitating* them&lt;br&gt;
The thing is: Researchers aren&amp;#x27;t the decision makers. We learn from users and carry that information to the people who make decisions. But traditional delivery often fails. Research repos collect dust. New frameworks promise to make insights &amp;quot;stick&amp;quot; but rarely do&lt;br&gt;
The reason is simple: transfer of information isn&amp;#x27;t transfer of conviction. What&amp;#x27;s learned without being felt is forgotten. People are most convinced by reasons they discover themselves. (Pascal)&lt;br&gt;
So maybe the standard practice will move from *finding and delivering* to *finding and facilitating derivation* - like teachers helping derive a math equation - the logical chain is established and the conclusions are clear, but re-deriving together helps the learner foster a stronger sense of ownership and understanding compared to sharing beautifully-packaged final equations (or insights)&lt;br&gt;
(We&amp;#x27;ve seen this work in workshops. The question is how we make facilitation the default, not a once-in-a-while technique reserved for highly important and visible studies)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Steel-manning research findings</title>
      <link>https://himanshukalra.com/writing/steel-manning-research-findings/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/steel-manning-research-findings/</guid>
      <pubDate>Thu, 30 Oct 2025 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;Notes on steel-manning user research findings:&lt;br&gt;
1/ risk and impact. what are they risking if they don&amp;#x27;t act on it. what can they gain if they do. great to include numbers that measure the impact. estimates, quick arithmetic - and walking them through them - is far better than nothing&lt;br&gt;
2/ stories. why it matters for the user. in what situation would it be crucial. drama - emotional highs and lows - is a part of human life, and should be a part of stories you tell&lt;br&gt;
3/ prioritise it for them. PMs already have quarterly planning. Where might the findings map onto what&amp;#x27;s already planned?&lt;br&gt;
4/ behavioral AND attitudinal data - made sense of and narrated to give insight into ongoing product/business issues and what may solve them&lt;/p&gt;</description>
    </item>
    <item>
      <title>First principles of user research</title>
      <link>https://himanshukalra.com/writing/first-principles-of-user-research/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/first-principles-of-user-research/</guid>
      <pubDate>Mon, 10 Mar 2025 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;When entering unfamiliar territory, it&amp;#x27;s useful to keep returning to the first principles of User Research:&lt;br&gt;
1/ Start with the assumption that you don&amp;#x27;t know what users need or how they think. (Epistemic Humility)&lt;br&gt;
2/ What people say often differs from what they do.&lt;br&gt;
3/ Many usage behaviors rely on unspoken, embodied knowledge that users cannot articulate. Research must surface this tacit dimension.&lt;br&gt;
4/ User behaviors are shaped by their environments, tools, social contexts, and constraints - not just by preferences or rational choices.&lt;br&gt;
5/ Research findings are only meaningful to the extent that they represent users&amp;#x27; actual contexts, environments, and behaviors. The lab is never the same as the wild.&lt;br&gt;
6/ Users can reliably identify problems they experience but are less reliable at envisioning effective solutions. Their struggles are data; their suggestions are hypotheses.&lt;br&gt;
7/ The models we create of users and their behaviors are always simplifications. The map is not the territory.&lt;br&gt;
8/ Focus research on the zone just beyond what you already know, where uncertainty is highest and learning potential is greatest.&lt;br&gt;
9/ Research can never be comprehensive. Focus on reducing uncertainty in decision-critical areas rather than attempting exhaustive understanding.&lt;br&gt;
10/ Package insights differently for different audiences (designers, engineers, executives) without compromising integrity or nuance.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Learning flows both ways</title>
      <link>https://himanshukalra.com/writing/learning-flows-both-ways/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/learning-flows-both-ways/</guid>
      <pubDate>Tue, 31 Dec 2024 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;The interesting part about AI interaction is that the usage style is unique to each person and learning flows both ways.&lt;br&gt;
AI capabilities are improving quickly and users&amp;#x27; mental models are shifting with it. What works in Week 1 might be irrelevant by Week 4.&lt;br&gt;
In this evolving relationship, designers need to actively understand:&lt;br&gt;
&amp;gt; how people ascribe agency, intelligence and intentionality to AI responses, and how that affects their interaction style and emotional investment&lt;br&gt;
&amp;gt; how people develop working models of AI reliability and capabilities, similar to how we form attachment styles through repeated interactions and expectation-setting&lt;br&gt;
&amp;gt; what makes people feel comfortable sharing personal information, and how this affects depth of engagement and learning outcomes&lt;br&gt;
With AI agents being a significant focus area of big tech in 2025, perhaps we will shift our focus from designing a sequence of interactions to designing dynamically evolving relationships.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Andrea Knight Dolan on AI in research</title>
      <link>https://himanshukalra.com/writing/andrea-knight-dolan-on-ai-in-research/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/andrea-knight-dolan-on-ai-in-research/</guid>
      <pubDate>Tue, 30 Jul 2024 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;An 18-year Google veteran,&lt;br&gt;
Andrea Knight Dolan&lt;br&gt;
is a leading expert in applying AI to UX research. She offers consulting, teaching, and mentorship services to help organizations harness the power of AI for better user experiences.&lt;br&gt;
Here&amp;#x27;s what I learnt from her discussion with&lt;br&gt;
Christine Perfetti&lt;br&gt;
last week:&lt;br&gt;
1/ AI enables scale - and raises expectations&lt;br&gt;
&amp;quot;With AI moderators, it&amp;#x27;s not 10 interviews anymore. It&amp;#x27;s 30. It&amp;#x27;s not 30 interviews total. It&amp;#x27;s 30 per country. As the magnitude of data increases, it is where the opportunity and the necessity to rely on AI to process the data comes in.&amp;quot;&lt;br&gt;
2/ There are a range of products available (general and specialised), each with it&amp;#x27;s use case for Research. In a recent project, she used:&lt;br&gt;
ChatGPT-4o for:&lt;br&gt;
- Domain research and literature reviews&lt;br&gt;
- Brainstorming and drafting interview scripts&lt;br&gt;
- Translating responses (e.g., Spanish to English)&lt;br&gt;
- Summarizing respondent answers&lt;br&gt;
- Cross-checking responses across interviews&lt;br&gt;
Voicepanel&lt;br&gt;
for AI-moderated interviews in Spanish (a language she doesn&amp;#x27;t speak💡)&lt;br&gt;
AddMaple&lt;br&gt;
(Quant analysis tool) for Open-ended coding and thematic tagging. &amp;quot;AddMaple did in 3 minutes what would usually take me 45-50 mins of manual work. And those 3 minutes were reviewing it&amp;#x27;s work&amp;quot;&lt;br&gt;
CoLoop&lt;br&gt;
for segment analysis&lt;br&gt;
Reveal&lt;br&gt;
for hypothesis testing with PII stripping&lt;br&gt;
3/ Synthetic (AI-generated) user data may be convincing, but they do NOT represent real user behaviour. Use it carefully.&lt;br&gt;
AI has never truly lived - it hasn&amp;#x27;t slept, exercised, or eaten, and it can only regurgitate existing discussions, and not truly respond to new stimuli. Using an AI-generated user is like modeling an expert user who knows exactly what to do and don&amp;#x27;t make any mistakes.&lt;br&gt;
4/ If you are a skeptic, a safe and effective way to start is to use AI for Desk Research&lt;br&gt;
Use ChatGPT as your resource librarian, ask it to quickly find relevant resources and summarize key points. If you find any good reports, share it with GPT to chat with them&lt;br&gt;
5/ Micromanage the tools until you trust them&lt;br&gt;
Treat AI tools as research assistants and give them specific, targeted tasks instead of broad assignments. Maintain control and oversight, ensuring the quality and relevance of insights while leveraging AI&amp;#x27;s efficiency for tasks like data processing and analysis.&lt;br&gt;
&amp;quot;You don&amp;#x27;t ask it to boil the ocean. You ask, &amp;#x27;This is what the stakeholder needs to know. Do we have evidence of this here?&amp;#x27;&amp;quot;&lt;br&gt;
6/ The most important skill for UX Researchers? Interviewing.&lt;br&gt;
AI tools help scale up the extent and speed up the process, yet if you don&amp;#x27;t ask the right questions, you don&amp;#x27;t collect the right information. Even with an AI moderator, you have to program the interview, and you have to know if it&amp;#x27;s doing a good job. The classic principle still holds: Garbage in, garbage out.&lt;/p&gt;</description>
    </item>
    <item>
      <title>When everyone can create</title>
      <link>https://himanshukalra.com/writing/when-everyone-can-create/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/when-everyone-can-create/</guid>
      <pubDate>Sun, 05 May 2024 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;GenAI tools raise everyone&amp;#x27;s ability to create. Now, more and more people can create with less and less skills and effort.&lt;br&gt;
You no longer *need* to know:&lt;br&gt;
- color theory to create illustrations, or&lt;br&gt;
- data structures and algorithms to write a program, or&lt;br&gt;
- the difference between inductive and deductive reasoning to write a research plan&lt;br&gt;
(Hurray for reducing the grunt between idea and output)&lt;br&gt;
But when it&amp;#x27;s easier to create, it seems that the value of human discernment will go up.&lt;br&gt;
Discernment for:&lt;br&gt;
- Quality: Mediocrity is easy and aplenty, high quality work stands out. Domain expertise helps.&lt;br&gt;
- Relevance: Is it relevant and useful for the people it is created? Context and cultural sensitivity helps. (Shameless plug for the importance of UX Research)&lt;br&gt;
- Facts v/s Biases(Human) and Hallucinations (GenAI): Both Humans and AI are fallible. Critical thinking and evaluation helps.&lt;br&gt;
#genai&lt;br&gt;
#creativity&lt;/p&gt;</description>
    </item>
    <item>
      <title>Books aren&#x27;t sacred</title>
      <link>https://himanshukalra.com/writing/books-arent-sacred/</link>
      <guid isPermaLink="true">https://himanshukalra.com/writing/books-arent-sacred/</guid>
      <pubDate>Fri, 22 Sep 2023 00:00:00 +0000</pubDate>
      <description>&lt;p&gt;Books aren&amp;#x27;t sacred.&lt;br&gt;
They are objects like any other.&lt;br&gt;
Ink on paper. Dead weight. Collecting dust.&lt;br&gt;
A book is only valuable to the degree you engage with it.&lt;br&gt;
Argue with the author.&lt;br&gt;
Wrestle with the ideas.&lt;br&gt;
Test them for yourself.&lt;br&gt;
Keep what works, discard the rest.&lt;br&gt;
Books aren&amp;#x27;t sacred.&lt;br&gt;
Scribble on them with pens and markers.&lt;br&gt;
Rip your favorite parts and paste them on your desk.&lt;br&gt;
By themselves, books are nothing but dead wood.&lt;br&gt;
Engaging, embodying and expressing their ideas is what keeps them alive.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
