A record of growing design and product responsibility

Mandate

Lead visitor-guide product choices while preserving the boundaries between digital support, physical conditions and curatorial authority.

Outcomes

• Funded ₹28 lakh offline-readiness work and kept two incomplete packs visibly unready in a later twenty-eight-pack review.
• Separated five venue-confirmed routes from three awaiting verification.
• Made the evidential distinction visible across twenty-one reconstruction views.
• Preserved forty-four unanswered questions within a 120-question content trial.

Decisions in context

The CPO role connects product discovery, visitor research and the continuing obligations of a guide service. I lead the team and stated expense, while Maya retains responsibility for the enterprise and venue partners retain their physical and curatorial authority. Offline preparation, route information, reconstruction and question handling have required different product decisions. I have presented their costs and limits to directors without asking the board to design the interactions. My responsibility includes keeping an unresolved condition visible when a complete-looking experience would be easier to demonstrate. The foundation ownership gives the company a particular purpose, but does not remove the need for sound commercial choices or a clear account of what the product supplies. I want that account to remain useful to visitors as well as to the people reviewing our business.

Reason for the move

Current executive remit; exploring a first outside governance contribution.

Mandate

Develop the guide experience and the evidence used to approve new visitor interactions.

Outcomes

• Owned the automatic-playback approval that produced nine mismatches in twenty-four walkthroughs.
• Supported ₹31 lakh of work on visitor-confirmed object identification.
• Kept the fifteen intended starts and nine mismatches visible in the trial account.

Decisions in context

The proximity-playback decision was mine, and the chronology should show the role in which I made it. I wanted the guide to feel effortless and accepted an automatic start before examining how a plausible but incorrect explanation affected the visit. Arun's field work made that consequence visible. The correction added a deliberate object-confirmation step and changed the promise in the demonstration. I learned to distinguish a smooth interaction from an interaction with a sound basis for what it claimed. The director remit also required explaining the cost of changing an approved feature to commercial colleagues. I did not present the correction as evidence that the underlying positioning technology had become accurate. The work instead established a more defensible relationship between the visitor's choice and the commentary the product supplied.

Reason for the move

Promoted into enterprise product leadership as CPO.

Mandate

Move from individual design assignments to a maintained guide product with clear venue and supplier responsibilities.

Outcomes

• Led an eight-person product group within the agreed ₹1.4 crore expense.
• Connected visitor research with recurring product decisions rather than isolated delivery presentations.
• Separated curatorial approval from interface and implementation decisions.

Decisions in context

Joining Zelqavri changed the timescale of my work. A studio assignment could end with delivery, but a guide product continued to meet visitors, changing content and venue conditions. I worked under the product director and learned how the supplier's choices affected curators, front-of-house staff and visitors who had not seen the original demonstration. The eight-person team could improve an interaction without owning the interpretation or physical environment around it. I became more careful about those boundaries and about the practical work needed to maintain them. My earlier design experience helped me explain alternatives, but the role required a broader account of responsibility over time. That understanding prepared me for the director role, although my later automatic-playback mistake showed how easily an attractive feature could still outrun the evidence for its promise.

Reason for the move

Expanded into product direction with a larger team and approval responsibility.

Mandate

Lead the design team's work on understandable interactions and the choices they ask people to make.

Outcomes

• Managed six designers within the stated ₹55 lakh annual expense.
• Introduced reviews of what a control promised as well as whether it could be found.
• Connected client explanations with observations of how people used the delivered design.

Decisions in context

Leading six designers required me to explain the reason for an interaction, not only its visual treatment. I worked with the creative director on assignments where a person needed to understand the consequence of a choice before making it. The team's expense was my defined scope; I did not own a client's operating budget or strategy. I learned to distinguish an instruction that made sense to the commissioning team from one that made sense to someone encountering the product for the first time. The work also taught me to listen when production colleagues identified a limit that a design presentation had concealed. I wanted to follow those questions beyond individual projects and see how a product changed through repeated use. That interest led to the move into cultural-guide product management.

Reason for the move

Joined a continuing cultural-guide product business rather than remaining in project-based studio work.

Mandate

Prepare visual and interaction material while learning how design intentions survive production and use.

Outcomes

• Supported work within a twenty-nine-person studio after completing the design degree.
• Revised instructions where the intended audience lacked the commissioning team's context.
• Carried production questions to the responsible designer rather than silently changing the intended meaning.

Decisions in context

My first employment began two months after the design degree and involved supporting work under the studio director. I prepared material, followed revisions and learned from the difference between an approved presentation and an experience someone could actually use. There were no direct reports or delegated budgets in my role. The useful discipline was to notice when an explanation depended on knowledge that the audience did not share. I also learned that a design change could affect production or meaning beyond the part of the screen I was editing. Those observations were the beginnings of professional judgement, not evidence that I already held product authority. The later promotion gave me responsibility for other designers and a defined expense, building on the practical experience of helping ideas survive their passage into use.

Reason for the move

Promoted to interaction-design lead with people and expense responsibility.