I want to talk about something that's been bugging me, and it starts with a confession: I checked my delivery tracking four times yesterday for a Le Creuset dutch oven.
A dutch oven. Duck egg blue, if you're wondering, because, unfortunately for my savings, my disposition is very much impacted by the beauty of my surroundings. That said, it’s not medicine. Not a part I needed to fix something broken. A very heavy, very beautiful pot that could have arrived literally whenever and my day to day would have proceeded exactly the same. And yet there I was, refreshing a little truck icon like it owed me an explanation.
That's not a personal failing (entirely). It's conditioning. We have spent the better part of two decades being trained, gently and then not-so-gently, to expect that wanting equals having, almost immediately. Same-day delivery. Overnight everything. A world that has quietly agreed the correct amount of time to wait for something is none.
And I get why. Speed feels like a kind of respect, someone took you seriously enough to prioritise. It also feels like competency, like the business you're buying from has their ducks in a row, proper systems, nothing held together with string. We've built entire industries on that feeling. But somewhere in all that hurrying, we started applying the same expectation to things that were never meant to move that fast. Craft. Trust. Quality. The stuff that's actually supposed to last.
The Rome problem
You know the phrase. 'Rome wasn't built in a day'. It's one of those sayings that's been repeated so often it's basically wallpaper now, nobody actually looks at it anymore. But sit with it for a second, because it's doing more work than we give it credit for.
Rome wasn't built in a day and it's still standing two thousand years later. Those two facts are not a coincidence. They're the same fact.
Here's the bit that gets glossed over: nobody in ancient Rome was stressed about the timeline. There was no investor deck promising the Colosseum by Q3. The thing that made it durable was precisely the thing that made it slow, layer after layer of people who actually knew what they were doing, building on foundations that had been properly laid, with materials chosen because they'd hold, not because they were available by Thursday.
We've somehow inherited the wisdom of that phrase while completely rejecting the practice of it. Everyone nods along to "good things take time" and then get snarky when a CAD drawing takes longer than a lunch order.
What we're actually conditioned to want
I don't think most people actually want speed. I think they want certainty, and speed has become the proxy for it. If it arrives fast, it feels controlled, predictable, safe. Waiting feels like risk, like something might go wrong in that gap, or worse, like nobody's actually working on it.
That's the bit worth pulling apart, because it means the anxiety was never really about the clock. It's about trust. And trust is the one thing you genuinely cannot overnight, no matter how good your logistics network is.
Where this hits home at VICELLO
I'll be honest about something we don't say out loud enough: that pressure doesn't stop at the client's door. It walks straight into our studio too. A brief lands, someone's move-in date has already been pre-determined, and suddenly the ask isn't "make this properly," it's "make this by X." We feel that pull constantly, the temptation to bend the process to match someone else's clock instead of the work's actual needs.
And here's the aha moment we keep coming back to: when something is made properly, it takes the time it takes. Not because we're precious about it, not because slow is some kind of virtue signal, but because the thinking, the testing, the sitting-with-it-until-it's-actually-right can't be compressed without the work quietly losing the thing that made it worth doing. You can rush a deliverable. You cannot rush the understanding underneath it.
This is the conversation we try to have early at VICELLO, before the pressure sets in rather than during it. Not "trust us, it'll be worth the wait," though it will be, but "let's agree now on what actually needs time, so neither of us is negotiating that under deadline stress later." Clients who get this upfront become the best collaborators we have, because they stop mistaking our pace for slowness and start recognising it for what it actually is: the work being done right.
We always tell clients, and I have to remind myself of this too, because I am not immune to wanting things right now, that anything built to survive contact with real use, real scrutiny, real time, needs actual time inside it. Not delay for delay's sake. Nobody's romanticising slowness here; slow-for-slow's-sake is just as lazy as fast-for-fast's-sake. I mean the kind of time where someone sits with a problem long enough to understand its actual shape, instead of shipping the first shape that turns up.
(Quick tangent, because I can't help myself: this is basically the difference between a flat-pack bookshelf and one your grandfather made. Both hold books. One of them will hold books after your grandkids fight over who gets it.)
Building the thing that's worth keeping
So what does this actually mean for the work we do.
It means resisting the urge to mistake output for progress. It means understanding that a wobbly-but-fast version of something isn't actually further along than a considered one that's still in draft, it's just louder about being finished. And it means being honest with the people we're building for about which parts of the process can genuinely be sped up and which parts still need a designer to sit still and be creative and revise, and a craftsman to go as fast as his hands will allow, because that part hasn't changed since Rome was laying its first road.
Efficiency is not the enemy here; bureaucracy dressed up as "craft" is just as guilty of wasting everyone's time as reckless hurry is. The enemy is mistaking velocity for value.
Here's the catch, though, and it's the one worth remembering next time speed feels like proof of a well-run business. That read, fast equals competent, only holds up when the thing you're buying already exists. Rows of stock, sitting on a shelf, mass produced ahead of time. Of course it can ship tomorrow. The investment was already made, weeks or months ago, by someone else, in a factory you'll never see. Speed there genuinely does signal good systems. But none of that logic transfers to something that hasn't been made yet. When the plans that land on your craftsman's bench still have "TBC" scattered through them, when nobody's worked out how the timber will actually behave, or how the build on site has already changed the circumstances the piece needs to be altered to suit, fast isn't a sign of competency. It's usually a sign that someone skipped the step in between: sitting down with you to explain how the piece is going to change, or simply asking where you want the handle placed on the shaker door.
And here's the annoying part: knowing that distinction doesn't actually fix anything. Our brains don't sort neatly into "already made" and "not yet made" before they start expecting. Understanding the logic doesn't switch off the impatience. It just means we get to notice it happening, which, most days, is the best any of us can do.
The stuff worth keeping was never going to arrive overnight. It was going to arrive when it was ready, built by people who cared more about it lasting than about it landing fast.
Anyway. My dutch oven arrived. It's gorgeous. It's also, at the end of the day, a pot, cast iron and enamel, made slowly, built to outlast me and probably whoever inherits it after me. Which, now that I think about it, might be the whole point I've been dancing around this entire post.
