How My Brain Actually Works: A Thinking Framework for Getting Things Done

Most people are not lazy. They are just mentally cluttered. Here is how I learned to cut through that.

---

I am going to be honest with you. I am not the smartest person in the room. I do not have a photographic memory. I did not study productivity systems or read fifty books on deep work. What I figured out, mostly by accident, is one thing: how to think in a straight line. And that one thing changed everything.

This is not a motivational piece. This is a framework. A method I use every single day to take something overwhelming and make it so small, so stripped down, that I have no choice but to understand it and move forward.

What Is This Framework?

At its core, this is about being microscopic. Insanely microscopic. Before you do anything, before you research, before you write, before you build, you zoom in so close on your task that you can see every single fibre of it. You strip it down to its bones. You ask the dumbest, most obvious questions first. And then, only then, do you start moving.

I call it directional thinking. You build direction before you build speed. You understand before you execute. You go small before you go big.

The Core Principles

Principle One: Reverse Engineering the End Goal

Every task has a finish line. Before I touch anything, I ask myself one question. What does done actually look like? I define it in one sentence. Not a paragraph. One sentence. Then I ask who it is for. Then I ask what they need to walk away with.

When I was building a blog explaining how Alexa works using AWS services for a general audience, I sat down and wrote this: my goal is to explain each major Alexa function and the AWS technology behind it in a way that a person with zero technical background can understand. That one sentence became my compass for every decision I made after that.

Principle Two: Baby Brain First

Before I try to be smart, I try to be stupid. I ask the most obvious question a child would ask. What is this? What does it do? Why does it exist? This sounds embarrassingly simple but it is where most people skip and then wonder why they feel lost twenty minutes in.

When I started researching Alexa, I asked: what does Alexa actually do? Not how. Not why AWS. Just what. I got a list. Then I took function one from that list and asked: what is this in one sentence? That single sentence became my entry point into something that felt massive before.

Principle Three: Microscopic Task Cutting

Once I have my end goal defined and my baby brain entry point, I break the task into a numbered list. Every item is one action, one outcome. Then I take item one and break that into its own numbered list. I keep going until each item is so small it takes less than ten minutes to complete.

This is the part most people rush. They make a list that says "research Alexa" as one item. That is not a task. That is a universe. A real task is: find the five core functions of Alexa. Another real task is: define function one in one sentence. Another is: list the three actions Alexa performs within function one. That is how small I go.

Principle Four: Expand Then Strip

After I define something small, I expand it. I ask for more context, more background, more examples. I let my understanding grow. Then I strip it again. I ask: what are the core actions here? What is the skeleton of this idea? This back and forth between expanding and stripping is how real understanding is built. You are teaching your brain the shape of a concept from multiple angles.

Principle Five: Friction Logging

Every time I feel stuck, I write down exactly what I am stuck on in one sentence. I do not skip past it. I do not distract myself. I name the wall. Over time I started seeing patterns in where my brain jams. That awareness alone made me significantly faster because I stopped being surprised by my own bottlenecks.

Principle Six: The Journalist Method with AI

This one changed how I use AI entirely. When I am stuck on a topic mid-blog or mid-research, I give that exact topic to an AI and I ask it to play the role of a journalist. I tell it to question me about that specific point, starting from the most basic level, one question at a time, waiting for my answer before asking the next one. The AI becomes a ladder. Each question is one rung. I climb it by answering, and by the time I reach the top, the fog is gone.

This works because most mental blocks are clarity blocks. You think you are stuck because the task is hard. You are actually stuck because you do not yet know what you actually think about it. The journalist method forces you to find out.

Principle Seven: Teach It to Close the Loop

After understanding a sub-task, I explain it out loud or in writing as if I am teaching a ten year old. Wherever I stumble is exactly where my understanding is still hollow. I fill that gap before I move forward. This is how I know I actually understand something versus how I know I just read about it.

Five Illustrations Across Real Domains

Illustration One: Understanding a New Codebase at Work

You join a team. You are handed a repository with fifty thousand lines of code. Most people open it and immediately feel paralysed. Baby brain approach: what does this application do? One sentence. Then: what are its five main modules? Pick module one. What does this module do? What are the three core functions inside it? What does function one do? Read only that function. Understand only that function. Close it. Open function two. This is how you eat a codebase without choking.

Illustration Two: Writing a Research Paper on Quantum Computing

You know almost nothing. The reverse engineering question is: who is reading this and what do they need to understand by the end? Answer: undergraduate students who understand basic physics. Now the paper has a shape. Baby brain: what is a qubit? One sentence. Expand: how is it different from a classical bit? Strip: what are the two properties that make a qubit useful? Build upward from there. Each section of your paper is now a micro-task with a defined entry and exit point.

Illustration Three: Debugging a Production Issue at 2am

Something is breaking in your live system. Users are affected. This is high pressure and your brain is scattered. Friction logging first: write in one sentence what the system is doing that it should not be doing. Then reverse engineer: what is the expected behaviour? Baby brain: what changed in the last deployment? List those changes. Take change one. What did it touch? What could that break? This strips panic out of the process and replaces it with direction.

Illustration Four: Learning a New Financial Concept Like Options Trading

You keep hearing about it. You open three YouTube videos and feel more confused than before. Baby brain: what is an option? One sentence. Expand: what are the two types? Define type one in one sentence. What is the one scenario where a person would use type one? Now you have context. Now you ask the journalist question to an AI: I understand a call option as the right to buy a stock at a fixed price. Question me about this starting from the most basic point. Let it probe. Answer every question. By the end you own that concept.

Illustration Five: Building a Content Strategy for a Brand from Scratch

A client gives you their business. They sell B2B software to logistics companies. You have to build their entire content strategy. This feels enormous. Reverse engineer: what does a logistics decision maker need to believe before they buy this software? That is your compass. Baby brain: what problems do logistics companies face right now? List five. Take problem one. What does it cost them? Who feels that pain inside the company? What does a solution look like to them? Now you have the first content pillar. Repeat for each problem. The strategy writes itself.

The Real Insight

Decluttering your mind is the actual work. Everything else, the writing, the research, the building, becomes straightforward once the mental roadmap is clear. Direction before speed. Microscopic before panoramic. Questions before answers.

You do not need to be the smartest person. You need to be the most deliberate one.

---