Follow the proof into the customer's decision

Mandate

Make personal creation, approval and receipt understandable across the complete keepsake proposition

Outcomes

• Introduced explicit appointed-editor and shared-edit modes for family albums
• Revised wall-print previews to expose crop decisions before approval
• Made the physical gift complete without requiring recipient enrolment
• Established bounded assisted capture at eight studios

Decisions in context

The CPO appointment joined the product choices across creation, approval and receipt. Thirty-eight colleagues work through four heads within ₹8.6 crore FY2026–27 development expense. The employer's310 employees and ₹128 crore revenue describe a wider enterprise than my delegation. Sameer holds executive business decisions, while engineering, production, studio operations, legal and finance keep their own responsibilities. I have revised decisions I initially favoured, including unrestricted shared editing and a borderless preview that made a crop too easy to overlook. I have also supported a gift that remains complete without a recipient account and an assisted service that leaves originals with their owners. Those choices require a workable alternative, not only a criticism of the first design. A future board contribution would need to apply that judgement through oversight while giving another company's managers the room to design and operate their own product.

Reason for the move

Current role; preparing to assess one first external board opportunity

Mandate

Connect creation features with the decisions and responsibilities they introduce

Outcomes

• Brought purchaser, contributor and recipient perspectives into product review
• Examined where additional options helped or burdened personal creation
• Prepared a broader product remit across studio and online experiences

Decisions in context

I became vice-president in September 2016, leading twenty-seven colleagues through three heads. The ₹4.7 crore annual function account sat within a230-person business with eleven studios and ₹79 crore revenue for FY ending March 2017. The range of creation features was expanding, but I learned that a longer feature list did not necessarily make a personal task easier. A new option could offer useful control or leave the customer responsible for a distinction the business had not explained. I began asking whose decision each feature represented and which colleagues would have to make the promise true after the screen was complete. The role required more collaboration with studio and production owners while leaving their authority intact. Promotion to CPO followed from that broader product perspective, rather than a transfer of every operating responsibility into the product function or an appointment to the statutory board.

Reason for the move

Promoted to chief product officer

Mandate

Shape creation journeys around the people contributing to and receiving a personalised object

Outcomes

• Connected proofing experience with customer-facing creation tools
• Examined the roles around a family photo-book project
• Learned to carry physical-format choices into the approval experience

Decisions in context

Moving to Qerzuni in May 2010 placed my proofing experience inside a retail product. Fourteen colleagues and two leads worked within ₹1.4 crore annual expense. The employer had six studios,140 employees and ₹38 crore revenue for the following March year-end. A photo-book project combined selecting images, arranging pages and choosing a physical format, but it also involved people whose names did not appear on the order. I learned to ask what a contributor thought an upload meant and what a recipient would encounter when the object arrived. Those questions were different from preparing a correct print file, although the file remained necessary. The role helped me connect the interface with the physical undertaking and with the relationships around it. I moved into the vice-president appointment to apply that perspective across a broader set of products and studio experiences.

Reason for the move

Promoted to vice-president of product

Mandate

Help customers understand the choices they are being asked to approve

Outcomes

• Made approval discussions more explicit about the decision under review
• Connected customer change requests with production responsibilities
• Completed a part-time management diploma in November 2008

Decisions in context

The proofing-service appointment began in June 2004 with nine colleagues and two supervisors. I held ₹56 lakh annual function expense within a160-person company reporting ₹29 crore revenue for FY ending March 2005. The work taught me that a completed approval could conceal an unresolved understanding. A customer might agree to a proof without recognising the aspect that would affect the final object, while a requested change might reach production without enough explanation. I wanted the service to make those decisions clearer rather than treat every approval as equivalent evidence. Part-time management study completed in November 2008 helped me connect the experience with cost, capacity and commercial choices. I moved to Qerzuni because I wanted to influence the product before a customer reached the proofing conversation, while retaining respect for the technical responsibilities that a good interface cannot remove.

Reason for the move

Joined a personalised retailer to influence the creation product earlier

Mandate

Prepare visual material and explain unresolved choices for supervisor and customer review

Outcomes

• Learned the distinction between a technically prepared file and an understandable choice
• Observed how customer approvals entered production work
• Developed an interest in proofing as part of the service

Decisions in context

I completed graphic communication in May 1998 and began work at Telqari that July. The six-person studio group reported to a design supervisor, and I held no independent expense delegation or management role. The company employed ninety people and recorded ₹14 crore revenue in the year ending March 1999. I prepared visual material for review and learned how a file could be technically ready while the customer's intention remained unclear. Senior colleagues approved the work and held the production decisions; those early assignments were a foundation for my judgement rather than programmes I directed. I became interested in the conversation around a proof, especially when someone agreed quickly and then described a different expectation later. Moving into the proofing-service role let me work on that relationship more directly and eventually led me towards the product decisions that create it.

Reason for the move

Promoted to lead the proofing service