01
The Challenge
Triveni Kala Sangam is one of the region's most historically significant cultural and arts institutions — a venue with decades of legacy, a dense programme calendar, and an audience that expects a level of credibility that matches the institution's standing.
But the digital presence had fallen behind. Publishing a programme update, announcing a new event, or updating institutional content required navigating a slow, manual, technically dependent process. The team had the content — they just couldn't get it live without delay and friction.
For a live cultural institution where programmes change, events get added, and communications need to move quickly, that gap between intention and publication was material. The project needed to close it — while preserving the institutional character that made the organisation what it is.
02
My Role & Scope
I served as the primary stakeholder interface across the full engagement — translating institutional requirements into system design, managing delivery through a development team, and ensuring every output matched the organisation's credibility and communication standards.
Cultural institutions carry identity constraints that commercial projects don't. The design, language, and structural decisions all had to work within a brand that had been built over generations. My role included managing those constraints without letting them become blockers.
The project ran from May to November 2025 — six months covering requirements, design, development, testing, and a fully governed handover to the internal team.
03
What We Built
The primary deliverable was a fully rebuilt website paired with a custom admin panel — a content management system designed around how the Triveni team actually works, not how a generic CMS assumes they should.
Programme management, event listings, institutional communications, and gallery content all had structured content types that matched the organisation's existing workflows. The team could create, edit, and publish without writing code, without raising a ticket, and without waiting for developer availability.
The website itself was rebuilt to reflect institutional credibility — clean, authoritative, and structured to communicate the depth of the organisation's history and current programme to both patrons and press.
04
Execution Approach
Institutions of this nature have multiple stakeholders with different priorities — administration, curators, communications teams, leadership. Managing those voices into a coherent product brief, and maintaining that coherence through delivery, was a significant part of the work.
I structured the engagement around clear decision points — keeping stakeholders aligned on scope and direction without letting every conversation become a scope discussion. Design and content decisions were documented and signed off before development began, reducing rework in later stages.
Handover was treated as a delivery milestone, not an afterthought. The internal team received structured training on the admin system, and the documentation was written for the actual users — not for developers.
05
Outcomes
Content publishing and update turnaround time improved by 65%. What previously required coordinating across teams and waiting on developer availability became a direct, same-day internal action.
The institution now operates its digital presence with full editorial independence. Programme updates, event announcements, and institutional communications are published when they need to be — not when the technical queue allows.
The platform was designed for longevity — structured to accommodate the organisation's evolving programme and communication needs without requiring a rebuild every time requirements grow.