Skip to content

Micro Lesson Blog: Mapping the Journey from Supply to Customer

Business Basics Blog
As HarvestBox gained more customers, founder Naledi Mokoena noticed small problems appearing across the business.

Some meal boxes were packed late because the ingredients had not arrived. At other times, the team discovered missing items only after packing had begun. Delivery routes changed at the last minute, and a few customers complained that their product was no longer as fresh as expected.

Everyone had a different explanation. The farmers blamed late order confirmations. The packing team blamed unpredictable deliveries. The drivers blamed last-minute changes.

Naledi wondered whether HarvestBox simply needed more staff. Before spending money, however, she decided to map the entire journey from supplier to customer.

Seeing the Whole Journey

A value stream includes all the activities needed to create and deliver something the customer values.

Naledi brought her team together and mapped HarvestBox’s main milestones:

Forecast demand → Confirm the menu → Order ingredients → Receive supplies → Pack meal boxes → Plan delivery routes → Deliver to customers → Collect feedback

Seeing the complete journey on one page immediately changed the conversation. The team realized that ingredients were not the only things moving through the business. Information also had to travel between customers, HarvestBox, suppliers, and delivery partners.

When that information was late or unclear, everything that followed was affected.

Finding the Real Barrier

Naledi had assumed that packing was the main bottleneck. Boxes often left the packing station late, so hiring another packer seemed like an obvious solution.

The value stream map revealed a different story.

The biggest problem happened earlier when customer demand was converted into supplier orders. HarvestBox used a mixture of spreadsheets, handwritten notes, and messages. Quantities changed repeatedly, and farmers where not always sure which order was final.

Late confirmations resulted in late ingredient deliveries. The packing team then had to wait or adjust the boxes at the last minute. Delivery routes could not be finalised, and drivers had less time to reach customers while the product was still fresh.

Hiring another packer might have made one activity faster, but it would not have solved the problem affecting the whole stream.

Building a Better Flow

The team created a second map showing how the process should work.

They introduced a weekly cut-off time for customer orders, followed by one approved demand forecast. Suppliers would receive confirmed quantities through a standard order form. Deliveries would be scheduled so that ingredients could be inspected and refrigerated immediately.

Recipe cards and packaging would also be prepared in advance, while delivery partners would receive estimated order volumes earlier. This allowed routes to be planned before the boxes were ready for dispatch.

Naledi selected two simple measures to track the improvement:

  • The percentage of supplier deliveries arriving on time
  • The percentage of customer orders delivered correctly and on time

These measures connected activity at the beginning of the stream with the experience at the end.

Start with What the Customer Values

A value stream map is more than a picture of your business process. It shows how suppliers, people, information, and activities work together to deliver value to the customer.

As you review your own value stream, focus on two questions:

  • Where do delays, errors, or unclear handovers interrupt the flow?
  • Which improvement would have the greatest effect on the final customer experience?

HarvestBox customers did not care how quickly one person could pack a box. They cared about receiving the correct ingredients, in good condition, at the promised time.

By mapping the journey from the local farmer to the customer’s front door, Naledi could see where that promise was being protected—and where it was at risk.

Once the full journey became visible, HarvestBox stopped reacting to individual problems and started building a more reliable way to deliver value.

Until next time, Instant Startup community!

Back To Top