Joel Daqverni · Chief Technology Officer · India
I would help directors examine whether a product promise preserves the conditions under which its engineering result was established. Specialist software can produce a compelling demonstration while leaving a source assumption or compatibility limit unstated. I would ask management to explain the tested scope, the consequence for users and the decision required when the evidence does not support the original claim. That is different from personally approving the algorithm or directing a release team from the boardroom. I would work alongside directors with commercial, financial and legal experience and use qualified assurance where needed. My own corrections provide useful examples of how a technical leader can become too attached to an attractive account. A first board role would require me to learn the whole enterprise and contribute to collective judgement beyond the engineering topics most familiar to me.
| Capacity | Committees |
|---|---|
| Ready to join | Technology and product-risk committee where constituted · Strategy and investment committee with specialist-software responsibility |
I would consider a first non-executive seat in a specialist software company where directors need stronger questions about product evidence, compatibility obligations and technical investment. Creative tools are close to my experience, but the fit would depend on the actual business and its relationships. I would seek a committee-member contribution under experienced leadership before considering chair responsibility. I have presented to directors but have not held a statutory appointment, and my formal preparation remains incomplete. Those facts should shape the induction and expectations. I would want the company to explain how my experience complements the rest of the board rather than treat the seat as a substitute for a CTO. A suitable appointment would allow me to learn, challenge and share responsibility for the whole enterprise while preserving the independence, time and confidentiality the role requires.
Presented to the Board or a committee
Board technology-investment and product-risk discussions
April 2021–present
Invited CTO presenter on engineering investment, release decisions and compatibility limits; no director or committee-member appointment.
The import defect kept the sample sequence while assigning the wrong rate, changing a sixty-second example to 55.125 seconds. The processing path completed, but the product had not preserved the recording as intended. At board level I would ask whether management's technical assurance follows the relevant context through the whole user operation, rather than only checking components in isolation. I would want to understand how the affected scope was established and how customers were informed. Directors should expect a clear correction and accountability without prescribing the conversion routine themselves. The broader lesson is that a small descriptive assumption can carry a material user consequence. A report of passing tests is useful only when the board understands what those tests were intended to establish and what remained outside their coverage.
The dialogue review found wanted consonant detail missing in seven of forty-eight clips under an aggressive setting. Further work improved three, while four retained a manual path. I would bring that distinction into a board discussion about the release and its claims. The decision is not simply whether engineering has improved an average measure. It includes which users may experience a different consequence, what they can inspect and whether the commercial description makes the limit clear. The four-week delay and ₹14 lakh correction were real costs, not evidence of a quantified loss avoided. A board can support a narrower product while still holding management accountable for demand, expenditure and the next learning step. It should not require every difficult example to disappear before accepting an honest account of progress.
I would begin by learning the company's customers, product economics and existing governance arrangements. With the chair, I would plan an induction that includes product, engineering, support and commercial perspectives through agreed access. Selected release and compatibility decisions could show how evidence reaches management and then the board. I would review earlier investment assumptions and the outcomes used to assess them, including work that was stopped or narrowed. Before suggesting a new reporting method, I would ask how current directors distinguish a technical result from a commercial forecast. Twenty-two days is a proposed annual allowance for meetings, reading and induction, subject to employer consent and the real calendar. A major product issue or transaction could require additional time. I would seek feedback on whether my contribution improves collective oversight or draws the board too far into individual design choices.
Velnuri's studio customers, software-component providers and commercial partners could create connections with a prospective board or its competitors. I would disclose relevant relationships and personal interests before receiving confidential papers, then seek an appointment-specific assessment with appropriate advice. Unpublished recordings, customer session details and my employer's technical plans would not be carried into another company's deliberations. I would also clarify whether the proposed seat assumes access to our engineers or informal product consulting. Those expectations could create obligations beyond the director role and should not remain implicit. If recurring conflicts prevented me from contributing to central product decisions, the appointment might be unsuitable even where individual matters could be managed. The assessment would need to remain current as commercial relationships and my own responsibilities changed, rather than become a one-time declaration filed at the start.
Any proposed seat would need a specific review of my employment, investments and relationships with software, studio and component partners. Technical confidence does not replace that assessment or establish eligibility.
IICA Independent Directors’ Databank: Not yet registered
I remain at an early stage of formal board preparation, before databank registration and any applicable proficiency assessment. Appointment-specific requirements would be established and completed; I am not relying on an exemption.