Hari MahendraContact
Sept 2026 • HM.OS News

HARI MAHENDRA

content design leadership portfolio

enterprise SaaS · AI products

Open the case files
Currently • Simpplr

Principal UX Content Strategist & Senior Technical Writer_

Hari MahendraContent design, 13+ years

I Design The Words, Structure, And Systems Behind Complex Software

Content designer and UX content strategist with 13+ years across enterprise SaaS, creative tools, ad-tech, and health-tech. I make product content clear for people and ready for AI to use.

HM.OS 13
impact.log — before → after
Help search success63% → 78%
Answer found, no escalation63% → 76%
Release adoption41% → 57%
SIMA thumbs up23% → 41%

Selected measured outcomes from shipped work

KNOWLEDGE BASE

563

articles audited for AI readiness

RETIRED

93

stale articles removed

TEAMS

34

scrum teams mapped

ADOBE

+21%

Premiere Pro trial sign-ups

RULES.SYS

328 deterministic rules in code. Judgment stays with people. 83% bulk review efficiency.

Hari Mahendra

Portfolio v2.0 · Built in Delhi-NCR. Some visuals redacted to protect customer data.

Words Are Product Infrastructure

Not copy decks

Most content work starts at the string. Mine starts at the structure — who needs what, where, and what the product actually knows — then writes the string last.

Words as a system

Content design systems, IA and review engines that let 34 teams and several AI agents make the same call on the same sentence.

Decisions, not strings

Every case shows the call I made and why.

Humans in the loop

AI drafts and checks. People decide.

Measured

Deflection, search, adoption, sign-ups.

563 Articles.
177+ Features.

*One help center, 34 scrum teams, 12 functional areas, 6 intent-based hubs. (See how)

Case Files (13)

Pick a file. Each one shows the problem, the calls I made, the proof, and where human judgment beat the shortcut.

C:/PORTFOLIO/FILES
HELP_PANEL.EXE — Simpplr

Information architecture

In-app help, shipped after 12 years in the backlog

Users had to leave the product, log in again and search a separate site. I led a native help panel from PRD to production.

0→43%

Ticket deflection, first month

63→76%

Answer found, no escalation

41→57%

Release adoption

The in-app help surface did not exist before launch.

Help panel default view with search, knowledge base, tutorials and a path to a human
Help panel default view with search, knowledge base, tutorials and a path to a human

What I decided

  1. 01Wrote the PRD: launcher, search, assistant, ticketing, article rendering and phased rollout.
  2. 02Designed screen-to-content matching so help appears for the exact screen a user is on.
  3. 03Scoped the assistant narrow: answer when confident, hand off to a pre-filled ticket when not.
  4. 04Moved page-to-content mapping to the writing team, so a new mapping never needs a code change.

Role

PRD author, prototype designer, end-to-end lead

Partners

Product leadership, design, engineering, CX leadership

Backend

DevRev PLuG SDK

Status

Shipped in 4 phases

> where_human_judgment_mattered

The shortcut was a vendor widget bolted on top. I set two constraints: it must feel like Simpplr, and the assistant must know its limits. Both cost more to build — and both are why it gets used.

How the work actually runs

Rules In Code. Judgment With People.

Accordis runs 328 deterministic rules on every string — no model decides whether a check happens. The Vernacular Skill handles tone and clarity. Content designers sign off. Try a sample string.

accordis — review

$ accordis check --surface "Delete dialog · button"

input“Yes”flagP0 · A destructive confirm repeats the exact verb and object. Never a bare “Yes.”output“Delete workflow”

✓ checked · shape valid · logged ▌

Sample strings illustrating real Accordis and Magnus voice rules.

magnus — authority ladder
  1. 1. Know“8 workflows failed in the last 24 hours.”
  2. 2. Offer“I can pause the 8 workflows.”
  3. 3. Authorize“Pausing these will stop their scheduled runs. Continue?”
  4. 4. Report“8 workflows paused.”

01

Pick the tool for the task

Prototyping, UI text, research synthesis or review. Keep what makes work better, drop the rest.

02

Give models real context

Skills, glossaries, design system rules and journey context. The screen, the step, the terms.

03

Review before anything ships

Diff tests, flagged review, hands-on testing against the real product.

04

Design the feature, not the docs

Join product and design early, so content shapes how AI features behave.

hari.jpg
Portrait of Hari Mahendra

About

Hari Mahendra

I started in newsrooms and health-tech, writing for millions of readers, and moved into product content as the work shifted from articles to interfaces. At Info Edge I led 14 writers and editors for Naukri.com. At Adobe I worked on help at portfolio scale. At Simpplr I lead content design, information architecture, AI agent voice, help, and the systems behind them as a senior individual contributor.

Master's in mass communication, AJKMCRC, Jamia Millia Islamia University.

Simpplr — Principal UX Content Strategist & Senior Technical Writer

2025 — now

Adobe — Senior Content Strategist, HelpNext

2022 — 2025

Info Edge (Naukri.com) — Assistant Manager, Content Strategy

2019 — 2022

Lybrate, NewsPiQ, Saur Energy, Zee Media — Content and UX writing

2012 — 2019

Multiplying the team

  • Leads a working group of 3 writers.
  • Trains 12 product designers in biweekly sessions on copy fundamentals and Vernacular.
  • Partners with 4 UX engineers on content implementation and internal AI tools.
  • Mentors 2 UX researchers on interview feedback sessions and friction-discovery forms.
  • Designed the hiring assessment for technical writers.
  • Led a team of 14 writers and editors at Naukri.com.

Contact

Let's Make Your Product Say The Right Thing

Content design leadership · Delhi-NCR, India

© 2026 Hari MahendraSome visuals redacted or recreated to protect customer and company data.Back to top