Most software gets designed at a desk. Big screen, keyboard, good Wi-Fi, a cup of coffee within reach.
That's fine if the people using it are also at a desk. A lot of them aren't.
Barnlight is one of my products, and it's built for people who are very much not at a desk. It keeps breeding records for small breeding operations.
You don't need to own a single animal to get something out of this, though. The barn is just a very clear example of a problem a lot of businesses have.
A lot to remember, in the wrong place to remember it
A small breeding operation has a lot to keep track of. Animal histories. Expected dates. Health records. Contract obligations.
None of that is unusual. Plenty of businesses have a list like that. What makes it tricky is where those details come up.
They come up at the barn. Something happens, and that's the moment it needs to be written down. Not later, at the kitchen table, from memory.
So the information has to be useful at the barn, not just at a desk.
And barns aren't known for great reception. You might have one bar. You might have none. If the software needs a solid connection before it will save anything, you're left with two options. Stand there waving your phone around, or tell yourself you'll enter it later.
"Later" is where details go missing.
What Barnlight does about it
The working environment shapes the software. So I built Barnlight around the barn, not the office.
It's an installable web app. It runs in the phone's browser, and you can install it so it's there when you need it.
It includes offline barn logging. When you record something at the barn, the entry is saved on the phone. When the connection comes back, it's synchronized. You don't have to wait for a signal to get the thing written down.
The controls are phone-friendly. It's built for the moment something happens, on the device that's actually in your pocket.
Dated reminders handle the "what's next." They make it easier to review what needs attention next, instead of keeping it all in your head.
Put together, the routine is simple:
- Review what's due.
- Record what happened.
- Keep the animal's history together.
Breeding records, reminders and contract obligations all sit in one farm workspace, so the record you make at the barn ends up next to everything else you know about that animal.
None of those pieces are flashy. They're just decisions you only make if you've asked where the person will be standing when they use it.
Build for where the work actually happens
Here's the lesson I'd take from the barn to any business.
Before you decide what software should do, ask where the work happens. Not where the computer is. Where the work is.
For some businesses, that really is a desk. For plenty of others it's a job site, a truck, a kitchen, a front counter or a storeroom. And those places come with their own conditions. Hands that are full or dirty. A phone instead of a laptop. Thirty seconds instead of thirty minutes. A connection you can't count on.
If the software ignores those conditions, people work around it. They scribble on a notepad and type it up later. They text themselves. They keep it in their heads and hope. And then the "real" system is only as good as whatever survived the trip back to the desk.
A few questions worth asking about your own business:
- Where are you, or your staff, when something needs to be recorded?
- What device is in your hand at that moment?
- How long do you actually have to enter it?
- Can you count on a connection there?
- What gets lost between "it happened" and "it's in the system"?
Not every business needs a barn mode
To be fair, plenty of businesses don't need software that works offline. If your work happens at a desk with good internet, that's what you should build for, and it keeps things simpler.
The point isn't "everything should work offline." The point is to design for the real conditions, whatever they are. Sometimes that means offline logging. Sometimes it means bigger buttons, fewer fields, or a screen that does one thing well instead of ten things badly.
This is how I think about it. It's not the One True Way. But "where will you be when you use this?" is a question I want answered before I build anything.
Where does your work happen?
If there's a part of your business where things get written down late, or not at all, I'd like to hear about it. Tell me where the work happens and what gets in the way. You don't need a technical brief. We'll start there.