A reusable crate needs a business for the journey back

## Keep the three return outcomes separate

A well-made crate can make a returnable-packaging proposal feel convincing before anyone has explained the return. It looks durable, protects the furniture and can clearly be used more than once. Those are useful physical characteristics. They do not organise collection from a customer, find a place to hold the empty crate or decide who repairs it when it comes back damaged. A product proposition that begins and ends with the object's durability can leave the continuing business arrangement outside the story most people hear.

Our fictional pilot dispatched ninety-five crates. At review, sixty-one had returned in usable condition, eighteen had returned needing repair and sixteen remained outstanding. The programme expense was ₹47 lakh. These categories described different outcomes and different work still to be done. Combining all returned crates into one favourable count would make the repair requirement less visible. Counting the outstanding group as though their eventual return were assured would add another assumption. I wanted the account to preserve what had actually happened before discussing the scale at which we might repeat it.

The distinction was not an argument against the idea. Fifty-three of the sixty-one usable returns were dispatched again by the next review, with eight held in reserve. That was concrete evidence of repeated use within the programme. It was also narrower than a claim that the full system was financially attractive or environmentally preferable at every destination. The remaining categories still mattered. A useful pilot report should let a reader appreciate the achieved second dispatches while also seeing the crates that required repair or had not returned at all.

I supported the pilot and wanted the proposition to succeed. That made it particularly important to keep the less convenient categories in the main account. When a product team is enthusiastic, it can treat unresolved activity as a temporary administrative detail and present the intended steady state as though it already exists. The customer and the logistics team then inherit the work needed to close the gap. My responsibility was to make that work part of the recommendation, rather than leave it for an operational appendix that only a few colleagues would read.

## Design the route beside the object

The logistics team could organise collection around two hubs with known delivery routes. Those conditions gave the pilot a practical shape. Customers outside the routes could have different collection timing, storage constraints and return costs. Extending the same phrase across the whole range would therefore extend the obligation beyond the circumstances we had examined. I wanted the proposed geographic scope discussed as carefully as the crate's construction. A product promise travels to the customer; the operating capability behind it must be able to travel there as well.

The customer has a role in the arrangement too. An empty crate may occupy valuable room after the furniture is installed. Someone needs to know when it will be collected, what condition is expected and whom to contact if the arrangement changes. Those questions should be answered through the authorised commercial and logistics process, rather than improvised by a salesperson after delivery. I do not assume that a customer will absorb indefinite storage or administrative work simply because the packaging has a desirable reuse intention. The offer needs to make that continuing relationship understandable.

Inspection and repair introduce another set of responsibilities. A returned object is not automatically ready for the next dispatch. Quality and logistics colleagues determine its condition and permitted use, and the programme needs a way to account for the work they perform. Product management should not bypass those decisions in order to improve a reuse count. Nor should it describe the repair population as a failure without examining whether repair is an expected and economical part of the system. The point is to show the activity honestly enough that the business can judge it.

The alternative proposed by sponsors was to launch more broadly and solve route questions during operation. That could have accelerated learning and given more customers access to the offer. It also risked making a wider promise before the organisation understood the collection burden. I recommended staying with the two hubs for the next cycle. This was a choice about the scale of commitment under current knowledge, not a conclusion that wider returnable packaging could never work. The product roadmap retained the possibility of expansion while giving the next operating cycle a defined scope.

## Describe the repeated use before claiming its benefit

Repeated use is an observation. A financial return is a calculation with a defined basis. An environmental benefit requires a properly bounded assessment of its own. Those statements can be related, but they are not interchangeable. Our sixty-one usable returns and fifty-three subsequent dispatches did not by themselves establish avoided emissions or a whole-programme saving. Transport, manufacturing, repair, loss and the alternative packaging arrangement could matter to such an assessment. I did not want a favourable intention to become a quantified conclusion merely because the crate was visibly more durable than a disposable package.

The ₹47 lakh expense remained in the pilot account. We did not hide it behind a claim that the crates would eventually pay for themselves, nor treat it as proof that the idea was uneconomic before enough cycles had been observed. The next review needed to understand utilisation, route costs, repair activity and outstanding returns on a consistent basis. Finance retained responsibility for the economic treatment. Product and logistics colleagues needed to show how the arrangement actually worked. That division of responsibility kept the discussion from becoming a competition between enthusiasm and one incomplete cost total.

Limiting the offer had a commercial cost. Some customers could not receive the programme yet, and sales colleagues had to explain why availability depended on the route. A national-looking proposition would have been simpler to communicate. I accepted the smaller promise because the larger one depended on capability still to be demonstrated. The explanation should be direct: this arrangement is operating within defined routes while the business examines further use. It should not imply that customers outside those routes are less important or that a limited pilot is already the company's universal delivery standard.

I would bring the return-route discussion into the earliest product brief next time. The crate and the collection arrangement should be developed together, with the customer obligation, inspection path and unresolved return cases visible from the beginning. A design review can then compare alternatives that include their continuing work, rather than approving an attractive physical object and asking logistics to invent a viable system around it afterwards. That sequence also gives colleagues a fairer opportunity to object while the proposition is still open to change.

For a board, I would ask which part of a circular or reusable proposition has been demonstrated and which part remains an intended future state. The question should invite a precise answer, not punish management for running a pilot. In our account the demonstrated part included ninety-five dispatches, three distinct return categories and fifty-three second dispatches from the usable population. The wider economics and environmental conclusions remained separate questions. Keeping those distinctions visible lets the company pursue a useful idea with ambition and discipline, without asking a durable object to stand in for the whole business required to bring it back.