For years, I thought my biggest weakness was organization.

I was wrong.

The real problem was much simpler: I could always see the destination, but I had no idea how to build the path that would get me there.

Seeing the Summit… Without Seeing the Trail

I’ve always worked the same way. I can picture the final goal almost immediately.

• A novel.
• A website.
• A portfolio.
• A game universe.

The overall vision is usually crystal clear in my mind. But turning that vision into a series of concrete, manageable steps? That’s where everything became blurry.

• Where do I begin?
• What’s the very first step?
• What comes next?

For a long time, I assumed this meant I wasn’t organized enough. Looking back, that wasn’t true. I simply hadn’t learned how to break a big objective into smaller, achievable milestones.

My Brain Was Trying to Remember Everything

For years, I believed this was just part of who I was. I thought I simply needed to work harder, become more disciplined, or improve my memory. Today, I see things differently. My problem wasn’t a lack of motivation. What I was missing was a method—a way to turn a broad vision into practical steps.

That realization may end up being more valuable than any software I’ll learn this year. The downside of my approach was something I hadn’t noticed until recently. Because I had almost no real structure, my brain tried to remember everything.

• Every idea.
• Every document.
• Every connection between projects.
• Every next step.
• Every file location.
• Every little thing I couldn’t afford to forget.

Without realizing it, my brain had become my memory, my planner, my folder structure… and even my hard drive. No wonder it felt exhausted.

The Turning Point

A few days ago, I wanted to start the fun part of my portfolio.

• The CSS.
• The colors.
• The typography.
• The visual identity.
• The creative work.

I opened my project folder. There were only a handful of pages inside. And yet… I stopped.

A simple thought crossed my mind:

« If I keep working like this, I’ll be completely lost in a month. In six months, I’ll probably give up on this project altogether. »

The problem wasn’t the number of files. The problem was that I already had no idea where they belonged.

A Project Architecture Isn’t About Organization

That’s when something clicked. I used to think a folder structure existed to organize a finished project. Now I believe it exists for the exact opposite reason.

It helps a project grow. It doesn’t answer the question:

« Where should I save this file? »

Instead, it answers a much more important one:

« When I come back six months from now, will I still know where to find it? »

That small shift completely changed the way I think about project organization.

The Least Exciting Part… and Possibly the Most Important

I wanted to create. Instead, I spent hours thinking about folders, categories and page hierarchies.

Honestly? It wasn’t the most exciting part of the day. But I now believe it was one of the most valuable. Because before building a page, I was building the place where that page would live.

Turning a Mountain Into a Path

The more I reflected on it, the more I realized that folder structures weren’t really the point. They were simply revealing a much bigger issue. For years, I could see the mountain. Now I’m learning how to build the trail. Creating a portfolio is no longer one overwhelming task.

It has become a sequence of smaller ones:

• define the overall structure;
• create the main sections;
• organize the folders;
• prepare the pages;
• and only then start writing the CSS.

The destination hasn’t changed. Only the path has become visible.

Building a System Instead of Relying on Memory

I used to think I needed a better memory. Now I believe I need a better system.

• Notion.
• My project architecture.
• My folders.
• My checklists.
• GitHub.

They all serve the same purpose. They free up mental space so I can spend my energy on what truly matters:

Creating.

What I Learned

The funny part is that I’ve always described myself as someone who thinks in branching structures. Yet none of my projects actually reflected that way of thinking. My mind naturally created branches. My workflow remained stubbornly linear.

The day I finally designed a real project architecture, I felt as if my working environment had finally started speaking the same language as my brain.

I thought I was spending an entire day drawing a folder structure. What I was really doing was learning something much more important about the way I work. I naturally see the destination.

Now I’m learning how to build the path that leads there. And maybe that’s what a project architecture truly is:

A promise to your future self.

« Don’t worry. When you come back six months from now, you’ll still know exactly where everything belongs. »

---