How do I manage to have my own projects —what many people call side projects— without letting them bleed into my main work? The answer isn’t extraordinary: there’s an order, a system and a lot of small decisions that keep that order in place.
I’m going to explain how I do it. Not as a recipe, but as what works for me. Maybe it’ll give someone an idea.
How the day is structured
Mornings are when I’m most available and productive, and I keep them blocked for my main work at Kaleida. Six hours of focus, no exceptions. No side projects in that window. No “I’ll just get ahead on this.” Even inside Kaleida we have clear priorities: sometimes things become urgent, and those urgencies take precedence over any other project we’re working on.
The six hours aren’t a magic number. They’re the result of trial and error. Working in long blocks without interruptions lets me move faster and focus on more complex tasks. After lunch, with more interruptions, it’s easier to handle video calls, answer emails and do smaller tasks that start and finish in under an hour. And jumping from one thing to another is exactly the multitasking that works against productivity.
Where my own projects fit
My own projects live at the edges. Not at the center. Specifically:
- Two or three hours at the end of the day, after the gym.
- Saturday mornings.
- Some dead time while I’m waiting for feedback or approval.
That’s it. There’s no more. And it doesn’t happen every day: there are weeks when I don’t touch a side project. The system has to be sustainable; otherwise it doesn’t work.
The key is that those edges don’t belong to Kaleida, unless one of those urgencies I mentioned comes up. When things catch fire, you have to put them out. Time with my kids doesn’t count either: it isn’t dead time or available time.
Organization is the foundation
Side projects don’t work because you have more hours; they work because you have a system. Mine has been refined over the years and evolves with me:
- One calendar, with blocks for Kaleida and blocks for my own projects.
- A weekly priority list, not a daily one. If the day falls apart, the week keeps going.
- One place for tasks and pending items. If it’s in my head, it gets lost.
- Short reviews: what do I have to deliver, what’s waiting for feedback, what can I move.
- Clear rules for switching context: I don’t mix Kaleida and my own projects in the same time block, so I can keep my head clear.
And something just as important: I learned to say no. Not to everything, but to what doesn’t fit the system. If there’s no time available in the afternoons or on Saturdays, it doesn’t go in.
Automating to free up attention
Another thing that helped me a lot: automating processes. Not to work more, but to make the time I have go further. Report generation, publishing content, tracking repetitive tasks: if something repeats and follows rules, I automate it.
One of my own projects was born from exactly that: automating reports that used to eat up days. What used to take a week now takes minutes. But the important part isn’t just the time it frees up. It’s the attention. Attention is the scarce resource. A side project doesn’t grow because you add hours; it grows because you remove friction. Automation lets me get to the end of the day with energy for the work that requires judgment, instead of spending it on tasks a machine could do.
The time I said no
A while back, a direct client contacted me with an interesting project. It was a very busy month at Kaleida: a big part of the team was working on a launch that was going to demand more hours than usual, including a weekend. I said no.
It wasn’t an easy decision, but it wasn’t a drama either. I liked the project, but I couldn’t give it the time it deserved without neglecting the main work. And doing it halfway wouldn’t have served anyone.
That’s one of the things that took me the longest to learn. When I was starting out, partly out of necessity and partly out of inexperience, I took everything. And since not delivering wasn’t an option, I ended up burned out. So I had to learn that saying no in time is part of the job. It isn’t a loss: it’s a way to protect what I already have.
What I’ve learned
Over the years I’ve learned to take care of three things: time, attention and my word. If I say I’ll deliver something, I deliver it. If I can’t, I say so early. And if a side project starts asking for more than I have available, I put it on hold.
I also learned that you don’t need to be available all the time to show commitment. What sustains a working relationship is delivering, solving problems and not neglecting what matters. My relationship with Kaleida goes back almost twenty years and is built on results and mutual trust. When there’s an important project, my own projects wait. They don’t compete: they organize around it.
My own projects exist because the main work is organized. That’s the rule. The rest is organization.
