Rukhsana Vezlqami · Chief Information Officer · India
I could help directors examine whether a digital-change claim describes the outcome the business actually needs. A completed import can alter the calendar meaning of a field; a converted document can detach values from their labels; a withdrawal action can leave a separate retrieval route unchanged. My experience includes approving the first of those mistakes, so I would bring a practical question about acceptance rather than a claim that technical leadership always prevents it. I would ask management which business owner defines the meaning, what evidence shows it survived and what remains unresolved. The board should understand the consequence without selecting a data type or directing an implementation. I would first need to learn the receiving company’s responsibilities and assurance process, particularly where information supports professional decisions that the technology team does not own.
| Capacity | Committees |
|---|---|
| Ready to join | Digital-change and information-risk oversight · Business acceptance and document-lifecycle discussions |
I would consider one first non-executive contribution under an experienced chair who wants a clearer account of what digital programmes preserve or change for the business. Preparation and company-specific assessment must come first; reporting to directors as CIO is not statutory board service. I could contribute initially to information-risk, digital-change or business-acceptance discussions alongside established governance expertise, without offering to chair a statutory committee. The receiving organisation should identify the particular judgement it needs and the assurance already available. Technology delivery, document ownership and professional interpretation must remain with management and the responsible advisers. The useful contribution would be to help colleagues distinguish a completed technical activity from a supported business outcome, and to recognise the unresolved part before approving a wider commitment or declaring the programme successful.
Presented to the Board or a committee
Board corporate-systems and change-risk discussions
April 2022–present
Explains enterprise change evidence through the CEO, including limitations on conversion and withdrawal claims; no statutory seat.
Reported to a committee
Corporate change review through the COO
April 2017–March 2022
Reported the date-migration correction and revised reminder acceptance; executive reporting rather than director service.
Twenty-four of eighty reviewed contract records displayed a day earlier after the migration I had approved. I would ask directors whether acceptance tested the business meaning or only confirmed that the transfer completed. The underlying agreement did not change because the display did, but staff could still act on an incorrect reminder. Contract owners had to establish the intended interpretation while technology corrected its representation. The useful oversight question is how management detects a semantic error before it becomes a broader operating assumption, and how the affected use is controlled while the evidence is examined. I would not ask directors to choose timestamp handling; I would ask whether the responsible owners can demonstrate that the business calendar survived the change.
Thirteen of seventy-two retired guidance items remained available through the reviewed search service after their source withdrawal. I would ask whether a completion claim follows the route employees actually use, rather than stopping at the system where the change began. The eventual search check supported the defined service correction, not erasure of every archive or downloaded copy. Document and legal owners retained retention decisions, and technical teams executed the approved status change. The board needs to understand the scope of that evidence and the consequence of the remaining copies without directing deletion methods. A useful question is whether the owner’s decision remains true after content has passed into another service that users may treat as equally authoritative.
I would begin by examining one recent enterprise change with the business owner who relied on its outcome. Through induction agreed with the chair, I would follow the acceptance evidence from technical completion to the user’s task and identify any limitation carried into the decision. I would also ask how current document status is maintained across the services that retrieve or transform content. The proposed twenty-four days must be tested against preparation, meetings, learning and exceptional demands, alongside employer agreement. I would seek feedback on whether my questions clarify a consequential assumption or pull directors into application management. An effective first-year contribution might improve the board’s understanding of one major transformation claim, including the evidence it lacks, rather than establish a parallel technical review that weakens the responsibility of management and its business owners. I would also ask how the board learns when an accepted limitation later affects a real user, so that assurance remains connected to experience after the programme closes.
My role provides access to client-administration arrangements, technology contracts, corporate documents and plans for future systems. Connections with the industrial investor, suppliers and business clients could matter to a prospective appointment even though I hold no personal interest. I would disclose relevant relationships before receiving protected board material and ask the receiving organisation to assess eligibility and independence in its own circumstances. Employer consent and realistic capacity need agreement. I would not transfer private system designs or commercial terms into another company’s negotiations, or present access to a supplier as the value of a seat. Recusal can address a specific issue, but repeated exclusion from the central transformation agenda may make the contribution ineffective. I would decline a role that expects informal technology certification, privileged data access or implementation work in place of collective oversight supported by the company’s own accountable teams.
Employment, technology suppliers, industrial investors and client relationships require review for each proposed appointment. No personal equity is held; independence is not inferred from that fact.
IICA Independent Directors’ Databank: Not yet registered
A first statutory appointment would require unfinished governance learning, any applicable registration and company-specific eligibility assessment. No proficiency result or exemption is claimed.