Safiya Zevqenri · Chief Technology Officer · India

Make the technical assumption usable in collective judgement

My contribution to a board

I would help directors understand what a technical assurance assumes about meaning, state and use. A number can reach a component without its unit, an undo action can leave a configuration invalid and an old application can return to data it no longer understands. My experience offers practical questions about those conditions, including a release approval I gave too early. I would use them alongside financial, commercial, people and sector perspectives rather than treat engineering confidence as the whole enterprise answer. The board should be able to see the relevant test boundary, the unresolved work and the cost of obtaining stronger evidence. I would also want to distinguish a useful observation from a universal conclusion, especially where a successful demonstration or improved task result could be promoted beyond what was actually assessed. The contribution is a clearer technical conversation for collective judgement, with implementation and specialist feasibility remaining with their authorised owners.

Judgement in practice

Asking whether a transmitted value retains its product meaning

I approved a centimetre interface while its receiver still assumed metres. The synthetic 2.35-metre example travelled as 235 and became 235 metres downstream; eighteen of 120 test quotations exposed the mismatch. We held release and funded ₹41 lakh of correction. I would ask whether a material assurance includes the receiving behaviour and the assumptions shared between teams. The case contains no live wrong order or physical-measurement certification. Directors do not need conversion code to understand why a successful transmission is insufficient. They can expect management to explain the meaning preserved at the boundary and retain responsibility for an approval that preceded adequate evidence.

Keeping a usability improvement within the review it actually passed

Nine of twenty-four adults could not complete width setup through a dragging-only control. After a ₹52 lakh programme of labelled inputs and keyboard controls, three of the same group could not complete it. I would ask what the observation supports and what it leaves unresolved. Practice and order effects prevent a controlled causal claim, and one task does not certify the entire product. The improvement and the remaining failures both matter. A board can scrutinise the scope of a customer-access assurance without diagnosing participants or prescribing interface details. Qualified assessment and further enquiry remain necessary before broader claims are made.

Examining the saved state inside a rollback promise

Seventeen of forty-eight synthetic saved designs could not be read by the old application after the new structure had been written. We deferred release for a twelve-week ₹1.2 crore compatibility and recovery programme. I would ask whether reversibility includes the state left behind, rather than only an executable that can be redeployed. No actual customer data loss is asserted, and funding does not establish completed recovery capability. Directors can examine how the transition was rehearsed and which conditions remain open while leaving engineering owners to design and operate the response. The assurance should describe the customer product that returns, not simply the package restored.

My first year on a board

I would begin by learning the receiving enterprise's value creation, customer commitments and the relationship between technology and its other responsibilities. Induction should make the actual board and committee duties clear, with qualified guidance on eligibility and the relevant preparation. Through agreed channels I would follow selected technical assurances from the management claim to the scope of the evidence and the unresolved assumptions. I would ask the chair for feedback on whether my questions help the decision or become an attempt to design the system from outside. I would not create an informal architecture authority over the engineering team or request sensitive customer designs without a proper purpose. A useful first year would build understanding beyond my own retail context, strengthen my ability to discuss technical uncertainty with other directors and demonstrate that I can revise an interpretation when a commercial, physical or people perspective changes the question we need to answer.

Conflicts and their management

Before confidential access I would disclose executive employment, the 1.2% holding and relevant relationships with founders, the growth investor, suppliers, advisers and technology partners. Qualified review should examine the specific institution and proposed committee rather than infer independence from a modest holding or the absence of an existing seat. I would not bring proprietary software, customer designs or protected commercial terms into another board's discussion. Disclosure should lead to a practical assessment of which matters I can consider and whether exclusions would undermine the proposed contribution. Employer agreement and capacity also require attention, including the exceptional demands that can arise from an engineering incident or material release. If current duties repeatedly prevent useful participation, accepting a title would not resolve the conflict. The appointment should be workable in practice before relationships and access create obligations that exceed the time or independence I can responsibly provide.

My independence statement

My employment, 1.2% employee holding and relationships with founders, the growth investor, suppliers and technology partners require qualified review. I hold no statutory seat, but that does not determine independence for another institution.

Committee contribution

Chair and member readiness
Capacity	Committees
Ready to join	Technology or risk committee where the actual remit and eligibility fit · Customer-product or investment committee examining software-dependent commitments

Capacity and preferences

Time available: 24 days per year
Current directorships: 0
Sectors: Consumer businesses with configurable products · Retailers combining physical design with customer software · Enterprises reviewing product-engineering assurance and release decisions
Company type: An enterprise willing to examine the assumptions beneath a convincing technical demonstration
Company stage: Expanding customer-product capabilities or reassessing release and recovery confidence

The seat I am pursuing

I would explore one first non-executive role in a consumer or related enterprise whose product commitments depend materially on software. A technology, risk, customer-product or investment committee may be relevant only after its actual remit and my eligibility are assessed. I do not claim committee-chair readiness from the CTO title. Fictional registration and proficiency assessment are complete, while company-specific learning and qualified appointment review remain necessary. Twenty-four provisional days must include induction, reading, travel and unusual demands alongside executive work. I would value a chair who expects me to contribute beyond technical detail and listen carefully when another director sees an enterprise consequence I have missed. The role should allow sufficient preparation and appropriate access to evaluate the assurance without making me an unofficial second technology executive or the owner of implementation decisions that belong to management.

Governance learning and readiness

IICA Independent Directors’ Databank: Proficiency assessment passed

Fictional IICA registration completed in June 2026 and proficiency assessment passed in September 2026. No exemption is claimed; actual appointment and committee requirements still need qualified assessment.

Develop sector and enterprise understanding beyond customer-product engineering
Learn how board scrutiny differs from directing architecture and release execution
Examine the actual committee remit, relationships and preparation required for an appointment

Board and committee exposure

Presented to the Board or a committee

Vedqezmi Window Furnishings

Customer-product engineering, release and development proposals presented through the CEO

January 2022 onward

Explains technical assumptions, programme costs and release evidence without claiming a statutory seat or committee appointment.