How I make the boundary of my recommendation visible

The technology account I take to directors begins with the service proposition rather than the application name. I want the board to understand what the enterprise intends to promise, which operating decisions support that promise and what the proposed technology can establish. The distinction is particularly important in retail because an internal ambiguity can become a customer conversation very quickly. A record may move successfully between systems while the colleague receiving it still lacks the authority or context needed to give a dependable answer.

I have presented to Varneli's directors as CIO since January 2020, without serving as a director myself. My executive remit is 162 employees and ₹96 crore authority for FY2026–27, within a 6,800-person business. I keep those scopes separate. The CIO can fund and organise technical work, but merchandising, operations and service-policy owners retain decisions that the applications implement. A board paper should show that relationship clearly, rather than imply that technology has resolved every dependency because an interface has been delivered.

The collection-service rehearsal illustrates the point. Ninety-six of 600 proposals carried apparent availability that did not support the intended allocation. Returned items awaiting inspection and stock reserved elsewhere required different operating explanations. We accepted a four-week controlled stage at ₹3.6 crore to agree and implement the status handover. I reported correct status for the examined scenarios, not actual customer fulfilment. Directors could then consider the readiness proposition and the operating observation still required, without being asked to approve a wider claim than the exercise supported.

Measurement requires similar care. The lookup deployment produced an eleven-to-four-second change at the 95th percentile, while customer queue medians moved from 4.8 to 4.4 minutes in separate cohorts. I retained those definitions when presenting the ₹2.8 crore investment result. The report did not establish sole causality or a workforce reduction. A useful technical improvement deserved recognition, but it should not acquire a larger meaning merely because the board would prefer one simple benefit figure. Operations and technology needed to examine the remaining work together before proposing the next intervention.

For customer records, I wanted uncertainty to remain visible. We confirmed 4,000 additional links through review and left 8,000 candidates separate. The final count described linkage decisions within the examined set, not a population of unique people or a newly authorised audience. The relevant owners needed to assess intended use separately. My responsibility was to make the technical account and continuing correction process dependable. I did not present it as a legal-compliance determination. That boundary helps directors ask whether the enterprise has the right expertise and ownership for each part of the proposition.

Investment discipline also means examining whether a product is being asked to solve an unassigned decision. Of 720 support cases, 480 concerned permissions. A narrower ₹85 lakh ownership and routing intervention resolved 410 of those over six weeks, while seventy remained pending. The deferred ₹4.2 crore tool request was unapproved expenditure, so it did not become a cash saving in my report. The proposal could be reconsidered against a clearer requirement. I wanted directors to see both the immediate result and the evidence that would make a different next choice sensible.

An external board role would change my responsibility in these conversations. I would join fellow directors in assessing the whole company and would need to develop my financial and governance knowledge accordingly. I would examine relationships and appointment requirements before accepting, with employer consent and a realistic account of the twenty-two annual days I propose. I have no current directorships and do not claim universal independence. The contribution I could bring is a habit of following a digital promise to the people expected to fulfil it, then asking whether the enterprise has given them a clear and supportable decision.