Producing Content as a One-Person Team: The Loop I Built

While building Vakti Geçmeden I realized something: writing the app was only half the job. Explaining it to an audience that had never heard of it took no less effort than writing code. And the only person doing both at once was me.

For the first three weeks I made the classic mistake: I posted whenever I felt like it, whenever something came to mind. The result was four posts across three consecutive days, then ten days of silence. Nothing accumulates at that rhythm. What follows is the system I set up afterward — especially for people coming from the developer side who say “I need to produce content, but how?”

The problem is not inspiration, it is decision fatigue

Asking “what should I post?” from scratch every day is a single daily decision, and a very expensive one. At eight in the evening, tired, you cannot answer it well; you either post something bad or nothing at all.

The fix is to separate the decision from the production. I split it into three distinct jobs and never do them at the same time:

• Collecting — stockpiling ideas. Continuous, in the background, a five-second task.
• Producing — turning stockpiled ideas into real content. Once a week, in a long block.
• Publishing — shipping what is ready according to the calendar. Daily, without thinking.

The idea pool has to be frictionless

There is a note on my phone’s home screen that opens with a single tap. Inside it is one single list. When something comes to mind I write one sentence there — I do not edit it, categorize it or format it. Every time I have tried to keep the idea pool tidy, the pool has died, because taking notes turns into work.

Most of the ideas come out of the daily work anyway. Being a developer has an unexpected advantage here: the problems you run into every day, the bugs you fix, the decisions you make are all natural content. Typical lines in my list look like this:

• “Turkish character bug — why usernames were getting mangled”
• “Why businesses abandon the form halfway through”
• “Got an app store rejection, what was the reason”
• “A user asked this: ...”

The batch production day

One day a week, roughly three hours. During that block I do not write code and I do not check email. I pick five or six ideas from the pool for that week and produce all of them in one go.

The reason this is far more efficient than producing one idea at a time is setup cost. If you are going to record the screen, opening the simulator, preparing the data and setting up the lighting are fixed costs. Shoot five pieces of content in the same setup and that cost gets divided by five. The same holds for writing: when your head is already in “explaining” mode, writing several pieces back to back is faster than getting into and out of that mode every day.

Format templates

To avoid designing every piece from scratch, I settled on five formats, and when I pull an idea out of the pool I drop it straight into one of them:

The real benefit of a template is never facing a blank page. The moment I say “behind the scenes,” what I will record, how I will cut it and in what order I will explain it are all settled. Creativity stays inside the template instead of being spent finding one.

The calendar: one of them, and a realistic one

For a long time I tried to keep the content calendar in complicated tools; I could not stick with any of them. It now lives in a single table with four columns: date, format, topic, status. That is all.

What I learned about frequency is this: pick the lowest frequency you can actually hit, then increase it. Two posts a week shipped consistently beats five a week followed by silence two weeks later. Both for the algorithm and for the audience, consistency is worth more than volume. I settled on three a week; I can keep that up for months.

Measurement: what I actually look at

I stopped looking at like counts. If you are running a product account, the real question is: did this content take someone to the app? So I put a UTM tag on the profile link, which lets me tell where the traffic arriving at the store page came from.

Beyond that, the only thing I look at is which formats get saved and shared more. A save is a stronger signal than a like: it means the person plans to come back to that piece. For me it usually turns out to be the “one problem – one solution” format, and I shift my production plan accordingly.

The sustainability question

The most important property of this loop is that it does not collapse when I have a bad week. Because ideas have piled up in the pool, even if I miss the production day I can produce twice as much the following week. And because the calendar is realistic, catching up never looks impossible.

For anyone who is a developer and also has to produce content, this is my main advice: build the system around your worst week, not your best one. In your best week you will do more than the plan anyway.

• Social Media
• Content
• Marketing
• Productivity