The boundaries I keep visible when I ask for an investment decision

I want a technology investment discussion to show which operating decision the proposed system will support and who is authorised to make it. A technically complete platform can leave that question unanswered. If its records imply a commitment that nobody has approved, the organisation has acquired a more efficient way to circulate ambiguity. My executive contribution is to expose the dependence before management relies on the result, and to make clear where my own authority ends.

At Rujantra Systems I report to the CEO and present selected internal technology matters to the board. I do not hold a director seat. The distinction matters because I arrive with a management recommendation and responsibility for its implementation. Directors need room to question the purpose, alternatives, cost and evidence without becoming the operating team. I try to provide a decision they can examine rather than a technical account that requires them to accept my interpretation because the detail is difficult.

The first part of my recommendation is the boundary. A common environment serving 126 projects should not be presented as if it serves all 180 merely because that was the original aspiration. I identify the restrictions that keep the remaining work outside the scope, who can change them and the cost of continuing support. Where the programme depends on another function making a decision, I want that dependency to appear in the proposal. It should not emerge later as an explanation for a benefit that never materialised.

The second part is the account of the evidence. A pilot can show faster first drafts without showing equivalent capacity available for another engagement. I distinguish task-stage observations, end-to-end measures and the operating plan that would use any time released. I would not ask a board to approve an enterprise benefit based on a short study while leaving the connecting assumptions implicit. At the same time, I do not regard a limited result as worthless. A narrower next step may be an appropriate recommendation when its sponsor and purpose are clear.

The third part is the financial interpretation. When ₹1.8 crore of a shared technology pool cannot be reliably attributed, a formula can distribute it but cannot make it directly observed project consumption. Finance may choose a practical convention for planning. My responsibility is to supply the underlying records and explain their limits so the convention remains visible. Improving those records can change the discussion without reducing the bill. I avoid allowing a more detailed allocation to be described as a realised saving or a complete account of project profitability.

Disagreement belongs in this account. A delivery leader may value faster adoption more than a platform team does. A finance partner may prefer a stable allocation convention to a fluctuating observed measure. I try to explain what each position protects and what my recommendation gives up. That is more informative than presenting consensus as evidence that the choice is sound. It also helps directors see whether management has considered a credible alternative instead of merely comparing its preferred proposal with an obviously inadequate one.

After approval, I want the report to retain the same boundaries. If an access review continues after an acquisition's legal completion, the operational item should remain open even though the transaction has closed. If a pilot cohort improves, the result should remain attached to that cohort until broader evidence exists. Changing the language at the reporting stage can quietly remove qualifications that were essential to the original decision. I regard preserving them as part of executive accountability, not as a reluctance to recognise progress.

For a future board contribution, I would bring this attention to technology dependence while respecting collective oversight and the expertise of other directors. I would need induction in the particular enterprise and continuing development beyond my executive field. My employer's customer and supplier relationships would require careful examination, as would the time expected of the role. I have yet to complete registration in the IICA Independent Directors' Databank and do not claim appointment eligibility or independence through this profile. Those matters need the appropriate process for the seat under consideration. My immediate proposition is a practical capacity to question scope, evidence and responsibility, with an equally clear account of the experience I have yet to acquire.