The small wins you stop noticing

I want to be upfront about something. This is not a motivational piece. Sidewrks is meant to be honest company for people building things, not a source of encouragement or frameworks. But I think there is something honest worth saying here, which is that it is easy to document the friction and quietly ignore the progress.

So this is an attempt to do the opposite.

Over the past few weeks I have shipped three things for rcordr that had been sitting on my list for a long time. An onboarding tour for new users. A set of objective templates to help people get started. Updated copy on the website and app store listing.

None of them are technically impressive. None of them changed how the app works. But getting them done has shifted something.

The onboarding tour is the most honest example. In my head, it was going to be a multi-step walkthrough with highlighted buttons, tooltips, the full thing. That version felt complicated enough that I never quite started it. Every time it came up on the list I found something more pressing.

What I shipped in the end was a handful of screens. They explain what rcordr is, what it is for, and walk a new user through creating their first objective. Simple. Probably better than the version I had been imagining.

The interesting thing about all three of these tasks is what they have in common. None of them are things I need as the person who built the app. I know how it works. I know what it is for. The onboarding tour, the templates, the copy: they are all for someone arriving cold, with no context.

That is probably why they kept getting skipped. It is easy to build what you need. It is harder to build what someone else needs, especially when you are not entirely sure who that person is yet.

There is also a specific kind of task that tends to accumulate on side project lists. Not difficult, exactly. Just a bit dull. Updating copy is not the same kind of work as building a feature. It does not feel like progress in the same way, even when it objectively is.

Here is the thing I had not fully registered until recently: these tasks were quietly blocking me from moving forward.

Not in an obvious way. The app was working. rcordr has real users. But I had been holding off on any serious push to grow or promote it because it did not feel ready. And when I examined what "not ready" actually meant, it came back to things like the onboarding. A new user landing in the app without any guidance. Someone finding it in the app store and not quite understanding what it was for.

Getting these things done did not make the app perfect. The onboarding tour is not perfectly executed. But it is good enough, and I wrote about what that actually means a few weeks ago. It is shippable, it is better than what was there before, and it can be improved once I see how people actually move through it.

More than anything, having them in the rear view mirror has made the next step feel possible in a way it did not before.

I am not sure this is a universal lesson. Some people have no trouble shipping the boring stuff and get stuck on the technical problems. Some people skip the copy updates entirely and never notice.

But if you are building something and there is a list of tasks that keep getting deprioritised, not because they are hard but because they are not for you, it is worth taking a look at whether any of them are quietly acting as a ceiling.

The small wins are still wins. They are just easier to overlook.