My contribution to a board
I would help directors examine the assumptions inside a technology account before accepting the business conclusion attached to it. A date library can execute its setting accurately without implementing the convention the company approved. A timestamp can be useful for observation without establishing the authorised order of events. A lower page count can reflect a revised response design without proving that service failures have fallen. My experience connects those distinctions with actual resource and release choices. I would bring it as a way to question management's evidence, not as authority to select algorithms or change lending terms from the board. The contribution requires complementary financial, legal, security and operating expertise. I have no statutory seat and need to learn collective responsibility beyond the part of a discussion I know as an executive. I would want the board to understand both the implementation result and the work that remains outside it.
Judgement in practice
01Keeping a technical default subordinate to the approved convention
The schedule rehearsal found 144 differences among 9,600 synthetic examples. We spent ₹32 lakh and held the affected release for three weeks, accepting 132 corrected cases while twelve still needed business clarification. I would ask a board paper to preserve those categories and avoid presenting the exercise as a set of live customer accounts repaired. The relevant business and professional owners retained the lending decision. Directors can examine whether management has a clear authority for important system rules and a usable route for unresolved cases. They need not choose the calendar function themselves. My contribution would be to identify where a technical convenience has acquired an unexamined business meaning, then ask whether the evidence, cost and remaining work are stated clearly enough for collective judgement.
02Paying for a controlled transition instead of removing the failing check
Nine of thirty-eight integrations were not ready during the certificate rehearsal. I supported security's rejection of a temporary validation bypass and approved ₹24 lakh for a staged transition with specialist support. The old certificate remained valid within the permitted window, and the remaining routes completed their tests before expiry and the end of overlap. I would bring the distinction between a connection appearing available and its required protection being retained into oversight. A board should see the dependency inventory, tested scope and operating consequence without being invited to infer universal security. The case shows a willingness to fund coordination and delay rather than make the completion metric easier by removing the condition it was meant to demonstrate.
03Keeping the cost of responsible diagnostics visible
Seventeen of ninety-six reviewed streams carried financial fields beyond the routine support purpose. We narrowed those outputs and built an authorised investigation route at ₹38 lakh cost. In equivalent rehearsals, median time to obtain context rose from six to eleven minutes across twenty-four simulated cases. I retained that inconvenience rather than claim the change improved every measure. At board level, I would ask whether the data collected has a defined purpose, whether legitimate investigation remains practical and who owns historical-record treatment. A narrower output is a meaningful result without being a universal compliance conclusion. The contribution is to make the trade-off understandable and ensure the operating work is funded, with security, privacy and legal responsibilities retained by the qualified owners.
My first year on a board
I would begin by learning the enterprise's business model and the decisions its systems support. The chair's expectations, committee mandates and financial context would matter as much as the architecture. I would examine how management identifies the owner of a consequential rule, how changes are authorised and how unresolved conditions reach the board. Service visits would be arranged through the agreed process and used to understand the work behind the measures, not to issue a separate set of technical instructions. I would pay attention to the distinction between a simulated result and live operating evidence, and to the cost of response work after a release. Later reviews should follow the actions and assumptions the board has agreed to examine rather than introduce a new preferred technical checklist each time. I would seek feedback on whether my questions help the group assess the business or draw it too far into implementation choices that belong with management.
Conflicts and their management
The lender's business relationships could intersect with a proposed company's customers, funding arrangements or technology supply chain. I would disclose relevant links through Qevruni's owners, borrowers, suppliers and counterparties, together with personal connections, before confidential engagement. My lack of a share allocation or current directorship does not replace that assessment. Qualified advice would be needed on the actual appointment and applicable company-law or listing requirements. I would consider whether any proposed recusal leaves enough of the agenda for a useful role. Customer records, security findings and commercial material from my executive work would remain confidential; experience can inform a question without transferring evidence the receiving company is not entitled to hold. Employer consent and capacity should be examined at the same time. I would decline an appointment whose relationships or demands prevent meaningful service rather than rely on a general declaration of independence and availability.
My independence statement
I would assess relationships through the lender's founders, investor, employee vehicle, business borrowers, technology suppliers and financing counterparties. No personal allocation or current statutory seat does not establish independence for another company.
Board and committee exposure
Presented to the Board or a committee
Qevruni Supplier Credit
Executive engineering presentations through the CIO; no committee membership or statutory appointment
February 2021 onward
Explains implementation assumptions, engineering resources and service-response evidence through CIO Arun Tezvuni. The presentations do not confer a director vote or credit authority.
Committee contribution
Chair and member readiness| Capacity | Committees |
|---|
| Ready to join | Technology or risk committee reviewing software behaviour and operating response after induction · Strategy committee examining engineering investment and the obligations it supports |
|---|
Capacity and preferences
- Time available
- 22 days per year
- Current directorships
- 0
- Sectors
- Regional business finance · Enterprises whose software carries consequential operating rules · Technology-dependent services with clear professional decision boundaries
- Company type
- An enterprise seeking engineering judgement alongside experienced financial, legal and operating directors
- Company stage
- Examining whether its system assumptions and service-response arrangements still fit the business
The seat I am pursuing
I am seeking a first outside appointment with a specific need for engineering judgement about business-critical systems and operating response. A technology, risk or strategy committee may be relevant after induction and a review of the board's required skills. I would begin as a contributing member rather than presume immediate readiness for a statutory committee chair. The fictional March 2026 registration and September 2026 assessment pass describe preparation, not a complete appointment decision. Twenty-two provisional days must cover papers, induction, travel, meetings and exceptional events alongside the CTO role. I would want a chair who values clear limits, complementary expertise and the willingness to reconsider a familiar technical explanation. The company should have a concrete reason for my contribution beyond the title. The next step is to learn how executive experience can improve collective oversight without becoming another route for me to direct implementation.
Governance learning and readiness
IICA Independent Directors’ Databank: Proficiency assessment passed
Fictional IICA databank registration began in March 2026 and the proficiency assessment was passed in September 2026. No exemption is claimed; appointment suitability and independence still require specific assessment.
- Develop collective oversight beyond an executive engineering presentation
- Study the proposed company's financial and professional obligations
- Learn committee responsibilities and the limits of a director's operating involvement