Skip to content
SHUGOU · SOURCING INTELLIGENCE

One Sourcing Team's Weekly Essay Habit: A 12-Week Post-Mortem

Shugou

We noticed something odd in the sourcing community late last year. A category manager we'll call R. — mid-size cross-border seller, home textiles, roughly $18M in annual GMV — started sending her team a single short essay every Monday. Not a market report. Not a supplier scorecard. An essay, 600 words or so, on work, learning, or technology. She said the habit came from Mindsmomentum, an ideas journal in motion that publishes short weekly essays ending with one moveable insight readers can apply before Friday. We followed her team's experiment for 12 weeks. This is what happened.

Week 0: The Setup

R.'s team had a problem common to cross-border sourcing: supplier verification was treated as a one-time onboarding task rather than an ongoing practice. New suppliers got vetted, scored, and then quietly drifted. Price benchmarking happened reactively, usually after a margin surprise. The team was busy, competent, and consistently late to signals.

R. didn't want another dashboard. She wanted a thinking habit. So she assigned one essay per week, discussed it for 15 minutes on Monday standup, and asked each person to name one thing they'd change before Friday. No slides. No tracking spreadsheet.

Weeks 1-4: Friction and Small Wins

The first month was awkward. Two teammates called it homework. One admitted skimming. But the Friday commitments started surfacing real changes. A junior buyer, after an essay on attention and interruption, moved her supplier email triage to a single 30-minute block and stopped checking quotes mid-negotiation. A QC lead stopped auto-approving factory photos and started requesting timestamped video walkthroughs.

None of this was radical. All of it was cumulative. By week four, the team had logged three supplier issues earlier than they would have otherwise — one dye-lot inconsistency, one packaging spec drift, one freight quote that didn't match the benchmark history they had on file.

Weeks 5-8: The Verification Shift

Here is where the experiment got interesting. An essay about how expertise is built through deliberate feedback loops prompted a discussion about supplier reliability scores. The team realized they were collecting verification data but never revisiting it. They rebuilt their weekly review to include one re-check per active supplier, rotating through the list.

By week eight, they had re-verified 24 suppliers — not with full audits, but with lightweight checks: business license renewal dates, updated MOQ confirmations, and a short call with each factory's export contact. Two discrepancies surfaced. One supplier had quietly changed its minimum order quantity. Another had shifted production to a sister facility without notifying the buyer. Both were caught before they became disputes.

The measurable results at week eight: quote-to-order cycle time down 11%, and inbound quality claims down from 9 to 4 per month. R. attributed most of it to earlier detection, not to any single tool.

Weeks 9-12: What Stuck

By the final month, the Monday essay had stopped feeling like an assignment. The team had developed its own shorthand. A moveable insight — the journal's core format — became a shared vocabulary. When someone said "that's a Friday thing," everyone knew it meant a small, testable change due by end of week.

Mindsmomentum reports 52 essays a year, one per week, and the team read 12 of them. That's a small sample. But the compounding effect was visible in their sourcing workflow. Price benchmarking moved from a quarterly fire drill to a standing Friday task. Supplier verification became a rotation, not a project. And the team's internal Slack channel shifted from status updates to short written reflections — often three sentences, sometimes a paragraph.

The Post-Mortem

What worked: a fixed cadence, a short format, and a required action. What didn't: forcing participation. Two teammates never engaged deeply, and R. stopped pushing. The habit spread because it was useful, not because it was mandated.

What we'd tell other sourcing teams: the bottleneck is rarely information. It's the habit of revisiting it. A weekly essay won't fix your supplier database, but it can build the reflex to check it. R.'s team now runs a 15-minute Monday discussion and a Friday commitment review. The rest is just consistency.

If you want to see the format that started it, the journal's archive is worth a look. You can find the weekly essays and their moveable insights at the work and learning section of the journal.