The system made the total easier to trust

The resource calendar looked like an improvement over scattered planning sheets. It gave managers one view of the people and hours they wanted to allocate. In 2018 I supported a rule that multiplied forty colleagues by thirty scheduled hours and presented 1,200 hours as available for campaign work. Daniel Qavzori asked where approved leave and training appeared. The system had made the total easier to see while making a crucial subtraction disappear.

I completed computing studies at Drevqathi Computing College in May 1992 and joined Trezqoli Business Applications in June. Eight colleagues formed the support group. I investigated application records and user problems under supervision, without authority to change a client’s business rules independently. The work taught me that a field can be technically valid while carrying the wrong meaning for the person who uses it. The useful question was often what decision the user thought the system had already made.

In April 2000 I became Applications Manager, leading twelve colleagues within ₹1.6 crore annual function expense. We supported business systems for privately owned service firms. I learned to distinguish a technical change request from the business approval it needed. A client might ask for a faster process while the proposed default silently changed who could act or what a record meant. Our role was to make that consequence clear before implementing the request, not to claim that the software specification settled the commercial choice.

I joined Veqzorn Campaign Services in April 2008 as Business Systems Manager. The business-systems appointment brought eighteen colleagues and ₹3.2 crore in annual function expense into my remit. Campaign production brought together account teams, creative specialists and client decisions with different responsibilities. I worked on systems that carried those relationships through planning and delivery. The appointment made the cost of a weak default more immediate, because colleagues could commit work based on a system view whose assumptions had become invisible.

Promotion to Head of Enterprise IT followed in April 2015. Twenty-two colleagues worked within ₹4.1 crore annual operating expense. The calendar review identified 240 hours of approved leave and training within the gross 1,200 hours. That left 960 potential hours before assignments and skill fit, against 1,120 proposed allocation. We held the excess 160 planned hours and used ₹32 lakh over nine weeks to correct the account. I did not describe potential capacity as universally interchangeable hours or claim that the error had already caused overtime or cancellation. The weakness was in the planning permission the system appeared to give.

I became CIO in April 2021. In 2023 a client-workspace review examined forty folders. Twenty-eight matched the accountable owner’s intended permissions; twelve inherited broader access than intended. We held the twelve, corrected ten and left two awaiting owner clarification, using ₹47 lakh over eleven weeks. The example does not assert that anybody accessed or disclosed material improperly. It concerns a rule that needed a business owner’s permission boundary restored before further reliance.

In 2025 an archive proposal treated completed projects as ready for the next removal process. Of sixty examined projects, forty-five were eligible under the owner review and fifteen had unresolved contractual questions. We excluded the fifteen and used ₹53 lakh over twelve weeks to revise the process. Qualified contractual and information owners retained the actual decisions. I did not infer a universal retention period or treat completion status as a legal conclusion about what could be removed.

Today I report to Lalita Zeqronli and lead twenty-six technology colleagues. My executive presentations are not statutory board service, and I hold no personal equity. A first outside role would require further governance learning and an appointment-specific review. I want systems to reveal the authority still needed instead of supplying it through a default nobody remembers approving. The practical test is whether an operating colleague can see why the system permits an action, which assumption supports it and who can change the decision when the underlying commitment is different from the one the software was built to carry. I also want the two unresolved workspace cases to remain part of the story. Their continued hold shows a limit of technology’s authority that a list of completed corrections would miss. The enterprise still needed an owner’s answer, and completing the project was not a sufficient reason to invent one.

Open to Board appointments · Executive opportunities

Languages / Assamese · English · Hindi