Why do shrink and counts still trip up my team?

You can run the stockroom. You know the shelves, the orders, the flow. But the shrink number still surprises you, and the counts still come out wrong — and it happens with others, not alone, so the blame spreads thin and nothing gets fixed. This is not a mystery of inventory. It is a habit of attention. Your team checks when it is convenient, not when it matters. You accept 'close enough' because exact feels like extra work. That comfort is the leak. You did not choose to lose stock. But you do choose, every shift, whether to count the same way, write it down the same way, and hold each other to the same standard. Choose that, and the trips stop surprising you.

◆ How this problem reads on the two dials

GuidanceKnowledge

More coaching

Some to learn

1:1 with AureliusWith others (a Pod)

Some one-to-one

Practise with peers

The core failure is behavioral — loose habits and scattered accountability — so building a shared practice with the team matters more than teaching new facts about counting.

How the two dials adapt to you →

What’s really going on

Shrink and counts do not trip you by accident — they trip you where your system is loose and where people guess instead of check. Stop blaming bad luck or dishonest hands. Choose one count method, apply it the same way every time, and hold every person on your team to the same number.

🔒 What you’ll build togetherUnlock by starting

A movePick one count method and write it down — same steps, every time, every person.

A moveAssign a single owner for each count cycle, not a rotating vague 'someone.'

A moveCompare counts together in person, not after the fact in a report.

A moveName the variance out loud at the next team meeting — no number goes unspoken.

A moveReview the top three shrink causes together each week, and choose one to fix.

PractiseCount Audit Huddle · a Pod of 4 · 30 min

What changes unlock by starting

Your counts match more often because everyone follows the same steps.
Your team catches small discrepancies before they grow into a big shrink number.
You stop guessing who is responsible — the record shows it.
Trust builds between you and your team because the process is shared, not hidden.

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.