Here's a question that sounds too simple to bother asking. What is an order for?
If you sell anything, you probably think of an order as a record. Someone wants something, you write it down, and now you know. A name, some items, some quantities, a date. Done.
That's how I thought about it too, until I started building KneadIt.
KneadIt is business software for cottage food bakers: people who bake at home and sell what they make. It handles their storefront, their orders and their recipe costing.
You don't need to bake to get something out of this post. The baking is just where I happened to learn it.
Same orders, two different questions
Picture a home baker with a handful of orders due on the same day. One customer wants two loaves and a dozen cookies. Another wants one loaf. Another wants cookies and a cake. Each order came in on its own, at its own time.
An order list is great at answering one question: "Who ordered what?"
That's exactly what you need when you're packing boxes and handing them over. You look up the customer, check what they asked for, and make sure it's all there.
But the night before, the baker is asking a completely different question: "What do I need to make?"
And an order list is a pretty bad way to answer that. You'd have to go down the list with a notepad, adding up loaves from one order and cookies from another, and hope you didn't skip one. Every time. By hand.
Nothing is wrong with the information. It's all there. It's just shaped for the wrong job.
What the baking sheet does
So KneadIt has a baking sheet. It's a simple idea, and the details are what make it useful.
- The baker picks a delivery date. The day they need to prepare for.
- KneadIt gathers the right orders. It brings in the orders for that date marked Confirmed or Baking, then totals the quantities by product.
- The baker prints one sheet. It shows how much of each product to make, along with the customer names that go with them, ready to use while preparing the orders.
The individual orders are still there for packing and handoff. Nothing gets replaced. The same order information just shows up in a second shape, for a second job.
The date and the order status decide what belongs on the sheet. And grouping by product is the whole point. If the sheet were just another list of orders, the baker would still be doing the math.
Start with the work, not the data
Here's the part that applies to any business.
When people think about software, it's tempting to start with the information. What do we need to store? What fields go on the form? Where does it all live?
Those are fair questions. They're just not the first ones.
The first question is: what does someone need to do? Then you shape the information around that job.
The baker didn't need a better order list. They needed a different answer from the orders they already had. Once you see the work clearly, the screen almost designs itself. One view for "Who ordered what?" Another for "What do I need to make?"
This is how I approach building software, for my own products and for anyone I work with. It's not the only way. It's just the way that keeps me from building a beautiful screen that nobody uses.
You probably have a "baking sheet" problem too
You don't have to run a bakery for this to sound familiar. Most businesses have at least one place where the same information has to do two jobs, and one of those jobs is being done by hand.
A few questions worth asking yourself:
- Is there a list you go through every week, adding things up on paper or in your head?
- Do you copy information from one place into another just so you can look at it differently?
- Is there a question you answer the same way, from the same records, over and over?
If you said yes to any of those, the information probably isn't the problem. You likely already have it. It's just shaped for a different job than the one you're doing.
That's usually good news. Reshaping information you already have can be a smaller, more practical project than it sounds. It doesn't have to start with a big new system. It can start with one sheet of paper you're tired of filling out by hand.
A good place to start
If you're thinking about software for your business, don't start with a list of features. Start with the moment in your week where the work gets fiddly. What are you trying to figure out right then? What do you wish was already added up for you?
That's the kind of thing I like to hear about. You don't need a technical brief or a finished idea. Just tell me where it gets complicated.