What Moving Labs Taught Me About Component Organisation

I moved labs in February. Not by choice — the building where I'd been renting desk space decided to repurpose the floor, and I had about three weeks to pack everything and find somewhere new. I'd been in that space for four years. Four years of components accumulating in drawers, bins, trays, ziplock bags, and, embarrassingly, just loose on a shelf in a pile I kept meaning to sort.

The move forced something I'd been avoiding for the entire time I'd been there: I had to physically touch every component I owned.

What I found was a mess I'd completely normalised. I had four USB multimeters — I knew about two of them. I had 340 1k resistors in seven different bags across four different locations. I had components still in their original Mouser packaging that I'd ordered specifically for a project, used two of, and then just left in the bag with the packing slip still inside. I had a bag labelled "sensors (misc)" that contained, among other things, two pressure sensors I'd forgotten I'd purchased, a ToF sensor still in its ESD bag, and a BME680 I'd been genuinely convinced I didn't own when I ordered a replacement in November.

The replacement BME680 was also in the bag. Ordered after the one I didn't know I had.

Four years of accumulation had split my component collection into two parallel inventories: the official one I thought I maintained, and the real one that had quietly grown underneath it. Both were real. Neither was complete. The overlap between them was large and unmeasured.

The move as audit

Here's the thing about a forced lab move: it strips away the fiction that you know what you have. When everything is in drawers and labelled bins and you can walk up to the shelf and pull out the "ESP32" drawer, you feel organised. You have a system. The system is running.

But the system is only as good as what you actually put into it. And most of us don't put everything in. We have the official system and then we have the overflow — the components that didn't make it back to the right drawer after a late-night session, the ones that arrived while we were mid-build and got left "temporarily" on the bench, the ones that came as extras in an order and didn't fit the existing categories so they just became a new pile somewhere.

Over four years, that overflow layer had grown large enough that it was basically a shadow inventory. The official one lived in the drawers. The real one was scattered.

When I was packing to move, I couldn't just pack drawer by drawer. I had to go through all of it — the official layer and the shadow layer simultaneously — and make decisions. What goes in which box. What's actually the same thing in five different containers. What I could let go.

It took two full days. I lost those two days to packing when I should have been building. I'm still a little annoyed about it.

What I changed after

The new space is smaller, which forced a different kind of discipline. I couldn't bring everything. I had to make actual decisions about what to keep and what to pass on.

That constraint turned out to be useful. I had to know what I owned before I could decide what to bring. And knowing what I owned required having it all in one place, accounted for, with quantities.

I started using an inventory app seriously during the packing process — not as an afterthought after moving, but as the primary tool for deciding what to move. Everything went into the system before it went into a box. By the time I arrived at the new space, I had a complete picture of what I was unpacking.

I'd been reluctant to do a full inventory before because it felt like a large upfront investment with unclear payoff. The move showed me the payoff very clearly: without it, you're guessing every time you reach for something. With it, when I'm mid-project and I wonder if I have a certain level shifter, I can check. And the answer is trustworthy.

The other change: I got serious about the overflow layer. Everything that doesn't have a home in the official inventory when it arrives gets logged immediately or it doesn't get kept. I've been moderately successful at this. Better than I was.

The components you didn't know you had

The most expensive lesson from the move was the duplicates. Not because individual components cost much, but because of what they represent. Every duplicate is a moment when I reached for something, didn't find it, assumed I didn't have it, and ordered it. That's money. It's also the time to place the order, the delivery wait, the mental overhead of tracking it, and then the moment of opening the package and realising I already owned one.

Some duplicates are unavoidable — you can't always wait for delivery when you're mid-build. But most of the ones I found weren't urgent replacements. They were the result of not trusting my own inventory enough to believe it when it said I had something, or not having an inventory that covered everything I actually owned.

The BME680 situation still stings. That module costs somewhere between ₹600 and ₹800 depending on where you source it. I had two and didn't know. When I ordered the replacement, I paid for express delivery because I was under pressure. Extra cost on top of a component I already owned.

That's not a sourcing problem. That's an information problem.

If you're planning a lab move, or even just considering reorganising — treat it as an inventory audit, not a logistics exercise. The work of actually knowing what you own is the real work. The physical reorganisation follows from that.