Knowledge Base revamp.

Freshdesk is a cloud customer-support platform: email, chat, phone, social and knowledge base in one system, self-service first. A knowledge base article that answers a question is a ticket an agent never sees. "Best service is no service."

As Freshdesk was being rebuilt natively in Mint, a rare window opened, and I got it: rethink the knowledge base from the ground up, and introduce advanced, monetisable capabilities on a scalable foundation instead of porting the old module's limits forward. One designer, one PM, a team of sixteen, and three months.

This was my first large-scale knowledge base: learning how content is created, governed and consumed across teams while balancing speed, quality and adoption. The named challenges: designing a scalable content system rather than pages, balancing governance against content velocity, introducing roles and approvals without adding friction, and ambiguity throughout.

Screens age; structure compounds. I spent the scarce early weeks on three artifacts that every later decision would lean on: task flows for every job to be done, a rebuilt information architecture, and a task matrix mapping every action (create, publish, schedule, approve, reorder, move, delete) against the four roles.

The matrix became the contract for the approval workflow and the permissions model. When scope debates flared, we argued against the matrix, not against each other.

Only then did wireframes run ahead of the visual system: insights dashboard, folder trees, list views, bulk actions, filters. Each validated with users before high fidelity, then dressed in Mint with multi-portal support built in.

Phasing was the strategy, not a compromise. Parity buys trust, versioning makes content trustworthy, approvals make it an operation, analytics closes the loop.

After the advanced features went GA, 73% of customers were actively exploring the self-service module and article creation and management activity rose sharply. The clearest commercial signal came from the segment that stress-tests knowledge base capability hardest in evaluations: within Freshdesk's installed base of 100,000+ businesses, the mid-market segment doubled in the period after the revamp shipped, with advanced KB features like approvals, versioning and analytics repeatedly cited in those deals. Customer replies called out managing all articles on a single screen as a favourite improvement.

The strongest validation came years after I shipped it. The structure has held: the same IA, the same workspace, the same workflows, now absorbing AI-assisted article generation and editing without a redesign. That was the bet behind building the backbone first: a system designed around roles and workflows, not features, gets to say yes to the future.