There is a kind of problem that never gets solved, and it isn’t the hard kind. It’s the one that gets answered with a sentence beginning just. Just remember it. Just write it down. Just check again. It only takes a minute.
Every one of those sentences is true. That is what makes them so effective at closing the subject.
Large problems come with permission
A large problem announces itself. It arrives with enough weight that stopping is obviously justified. You are allowed to interrupt the day for it, allowed to ask for help, allowed to spend money, allowed to make a plan and tell people about the plan. Nobody questions the proportion, because the proportion is visible.
A small problem comes with the opposite. Attention paid to it has to be defended. Why does that bother you so much? is a question people ask about small problems and never about large ones. It is usually asked kindly. It is just that from the outside, the cost of a small problem is invisible. From the inside, it is not.
So the small one gets postponed, tolerated, worked around, or waved off: by other people first, and then, eventually, by you. Being dismissed is not incidental to small problems. It is their defining property, and it is why they persist.
Attention doesn’t scale with importance
Here is the part that usually gets skipped. The size of a problem and the amount of attention it consumes are two different measurements, and they are not well correlated.
A task that takes thirty seconds can be postponed for a week, and during that week it is not costing thirty seconds. It is costing a small recurring ping, arriving at inconvenient moments, each time re-deciding not to deal with it now. The work was never the thirty seconds. The work was carrying it.
A tiny uncertainty behaves worse. Did I take it already? cannot be resolved by thinking harder, which means thinking about it doesn’t end it. It sits there, occupying space out of all proportion to the four seconds the original action took.
Six frictions, each a few seconds, each recurring a few times a day, is not a few seconds. It is the texture of the day.
That accumulation is the actual subject. Not any single annoyance: nobody would defend building software about any one of them. It is the way a dozen of them together shape attention, mood, and how an ordinary day feels by the evening.
Efficiency is not the interesting part
It is tempting to file all of this under productivity and then measure it in time saved. That framing is available, and mostly wrong. Time saved is the easiest thing to count and rarely the thing that mattered.
The outcomes that matter more are harder to put on a chart: not having to make a decision; not having to hold something in your head; knowing a thing has been taken care of; being able to leave something unfinished without losing it; finding what you need immediately, at the moment someone is waiting; closing a loop that was open.
The case against solving it
This is the point where a software company is supposed to conclude that every friction deserves an app. We don’t think that, and the reason is consistent with everything above.
A new app is itself a small problem. It is something to install, learn, update, keep an eye on, decide about, and eventually abandon with faint guilt. Software that asks you to maintain a system in exchange for removing an annoyance has usually traded one friction for a slightly better-dressed one.
Plenty of small problems are better solved by a hook next to the door, a habit, a piece of paper, or the decision to stop caring. Some were never problems in the first place.
So the bar isn’t is this annoying? The bar is: would a small intervention actually remove this, and can it do that without quietly becoming a new one? Most ideas die at the second half of that question. They should.
What a small intervention looks like
The apps we did build are all versions of the same move. Tap Today doesn’t manage your medication; it records that you marked a dose and puts the answer on the Lock Screen and the watch face, because reaching for a phone to answer a four-second question is itself too much friction.
LemonBook doesn’t do your accounting; it lets an entry exist from a single detail: an amount, a title, a note, or just the receipt. The reason small amounts go unrecorded is not that typing is hard, but that finishing the form requires things you don’t have yet. That decision has a real cost: the ledger ends up holding rows that can’t be totalled. We chose it anyway. A record you can complete later beats a record that was never made.
Calemon doesn’t organize your week; it takes a schedule that hasn’t changed since August and moves it onto the wallpaper, because information you need repeatedly shouldn’t require navigation to reach.
None of these is a system. None of them asks to be maintained. Each one removes a specific recurring friction and then, ideally, becomes uninteresting.
Why there is a lemon in the name
The company name started as a pun: implement plus lemon. The lemon then turned out to be a better description of the work than the pun deserved.
A lemon is almost never the main thing. A slice beside a drink. A squeeze at the end of a dish. A strip of peel dropped in at the right moment. It cuts through, brightens, finishes something that was nearly there. Remove it and nothing collapses. Something just feels faintly unfinished.
That is a specific and demanding brief for software. Make the smallest useful intervention. Have a disproportionate effect. Don’t try to become the dish. It is also a useful test: if a feature only makes sense once the product has become the center of someone’s day, it is the wrong feature for us.
Some of us notice the small things
This studio exists partly because somebody finds it difficult not to notice: the extra step, the unanswered question, the tiny inconsistency, the task that should be trivial and keeps coming back for attention.
It can be exhausting to notice everything. It can also be useful. Both are true at once, and neither is a triumph. The useful version is narrow: noticing a friction often enough to describe it precisely, and then being willing to conclude that removing it isn’t worth the cost of the thing that would remove it.
None of this is a large claim, and it isn’t meant to be one.
Small problems are still problems. Sometimes, a little is enough.
IMPLEMON · Arizona · September 2026