
Learning to Work, Not Just to Study
For a long time, I measured how hard I was working by how long I stayed in the library.
Staying until midnight felt like commitment. Leaving early felt like falling behind. I stayed because others stayed, and because sitting in front of books for hours felt like the right shape of effort, even when very little was actually happening.
It took me longer than I would like to admit to understand that I was confusing presence with productivity.
Nobody had taught me how to work. School teaches you what to study. It does not teach you how to structure your days, manage your energy, or build a system that holds up under real pressure. You arrive at university and you are expected to figure that out alone, usually in the middle of a curriculum that does not slow down while you do.
So I started paying attention. Not to what the students around me were doing, but to when I actually produced my best work. What time of day my thinking was sharpest. How long I could genuinely concentrate before the quality dropped. What kind of planning made me feel calm versus what kind made me feel constantly behind.
What I found was not a revelation. It was more like a slow accumulation of small honest observations.
The first thing that changed everything: planning the week before it started
Not the night before. The week before. On Sunday, before the new week began, I would look at everything coming — deadlines, classes, commitments — and build a structure around them. Not a rigid hour-by-hour schedule, but a realistic map of where things needed to go.
The crucial part was leaving buffer. Before, I planned my weeks at 100% capacity and then felt derailed every time something unexpected appeared, which it always did. The buffer was not laziness. It was honesty about how time actually works. It turned disruption from a crisis into something I had already quietly accounted for.
The second thing: a to-do list that is actually realistic
Most to-do lists are wish lists. Fifteen items that could not possibly all be completed in a single day, which means you end the day having crossed off five things and feeling behind on ten.
I started working with what I now call the TAP method, something I developed through trial and error and have refined ever since.
T is for tasks — the concrete things that need to happen today, broken into clear specific steps rather than vague intentions.
A is for actions — anything that takes less than ten or fifteen minutes to complete. These are handled quickly and separately, because letting them sit on a task list gives them a weight they do not deserve.
P is for projects — the larger outcomes you are working toward. And this is the important part: projects do not belong on a daily to-do list. They are not things you do in a day. They are the results of sustained T and A work over time. Confusing the two is one of the most common reasons people feel permanently behind.
The method is not complicated. But building it required understanding how I actually worked, not how I thought I should work.
What I want you to take from this
If your current system is not working, that is not a personality flaw. Organisation is not a trait you either have or do not have. It is a skill, and like any skill it improves through practice, adjustment, and paying honest attention to what actually works for you specifically.
There is no universal system. The students who perform consistently well are not the ones who found the perfect method in a productivity book. They are the ones who took the time to understand their own patterns and built something around them.
You may need to reimagine how you work entirely. That is not a setback. It is the beginning of something that will compound for years.





