A spare-time number is only useful when the whole programme is counted

Sixteen minutes of main script left fourteen minutes in the half-hour window, according to the preview I had approved. It was a reassuring calculation, and the arithmetic was correct. The programme plan also contained eleven minutes of recorded clips, three of separate links and two of opening and closing material. Once Riniki walked through those components with me, the useful number was different: thirty-two minutes planned against thirty available. The product had made the producer's task look easier by counting less of it.

A correct sum can answer the wrong question

I had reviewed the spoken-duration feature as though the main script were the programme. The team had explained how the estimate was produced, and I had asked reasonable questions about that estimate. I had not asked the more important question about its scope. When the result appeared as spare time in the programme view, a calculation about one component became a claim about the whole undertaking. The error was in the product proposition I accepted, not simply in a formula that an engineer needed to correct.

This distinction matters because accurate components can lend false confidence to an incomplete account. A leader may inspect the calculation carefully and still overlook what has been left outside it. In our case, the missing material was not an unusual exception. Recorded clips, links and opening or closing material were ordinary parts of the planned sequence. The feature's apparent precision made it less likely that a busy producer would recognise how much interpretation remained. We had not merely omitted a detail; we had chosen a label that implied a broader answer than the calculation supplied.

The delivery sponsor proposed keeping the preview and adding a qualification that other material could affect duration. I understood the implementation advantage. Experienced producers often make such adjustments themselves, and the feature still offered information about the main script. But that defence changed the product's promise after the fact. If the view was intended to estimate only one component, it should say so. If it was intended to help a producer plan the whole programme, the ordinary components belonged in the account rather than in a warning that the user had to compensate for.

We chose the latter and allocated ₹34 lakh to the redesign. The revised view represented sixteen minutes of main script, eleven of clips, three of links and two of opening and closing material. It made the two-minute excess visible against the thirty-minute planning window. Those figures describe the defined plan. They are not a prediction that a real presenter will deliver every spoken element in precisely the estimated time. Keeping that distinction in the interface was part of the repair, because replacing an incomplete certainty with an overconfident complete certainty would not have served the producer well.

The producer should choose the response

Once the excess was visible, the product could have offered to remove two minutes automatically. I did not want the timing correction to become an unexamined editorial decision. There were different ways to revise the plan, and their value depended on the programme's purpose. A producer might shorten a link, choose another clip, revise the main script or reconsider the structure. The workspace could support those choices without deciding which content mattered least. Our authority over the tool did not confer authority over the programme.

That boundary is easy to blur when a product team is rewarded for completing the user's journey. The screen has identified a problem; a one-click fix appears to finish the task. Yet the final step may be the judgement the professional came to the tool to make, rather than an obstacle the product should remove. I want product leaders to distinguish avoidable effort around a decision from the decision itself. Making the components and their timing understandable reduced effort. Silently choosing what to cut would have assumed responsibility for the substance of the work.

The correction also required humility about the relationship between preparation and performance. Tevqari supplies a preparation workspace. It does not operate a station or control transmission. A complete plan can help a team rehearse and revise, but it does not establish that every live programme will end on time. We did not claim a measured reduction in on-air overruns or a financial benefit from the redesign. The supported outcome was a better account of what the producer had planned and the gap that needed attention before use.

I find that limit useful in an executive review. It makes clear what the programme bought for ₹34 lakh and what further evidence would be needed to claim a different result. A necessary product correction does not become more credible by attaching a speculative performance improvement to it. Directors and colleagues can assess the decision more honestly when the scope remains intact: we repaired a misleading planning view, retained the producer's judgement and accepted the cost of a more complete representation. Those are meaningful outcomes without an invented broadcast success rate.

Test the proposition against the whole undertaking

The review that changed my mind was not a sophisticated dashboard. It was a walkthrough of the planned sequence with somebody who understood the producer's task. That does not make technical testing less important. It identifies a different kind of test: whether the feature's claim matches the work it is supposed to support. A formula test can confirm that sixteen subtracted from thirty gives fourteen. It cannot tell us whether the sixteen includes the components the user reasonably thinks the result covers. Both questions need an owner.

I now ask a proposal to name the boundary around its calculation and then test that boundary against a realistic preparation example. What is included, what remains estimated, what has been entered elsewhere and what will the label lead a user to infer? The answers may reveal that the product needs a broader model or simply a narrower claim. Either can be responsible if it is explicit. What I want to avoid is a small calculation wearing the language of a complete service because that language makes the feature easier to sell.

For a board, the case is a reminder that a product can mislead without using a false number. The relationship between the number and the promise matters. Directors should hear how management tests that relationship, who can challenge it and what happens when a senior approval proves incomplete. I had to acknowledge my part in this one. The programme fitted only while we counted the main script; hearing the whole plan changed the decision. A preparation tool earns its place when it helps the producer see that fuller undertaking and leaves them able to choose what should happen next.