Why Dissertations Are Actually So Hard (And Why Deadlines Matter More Than You Think)

Everyone says dissertations are “hard”, which is technically true, but also feels like a massive understatement.

At the start, it all feels quite exciting. You’ve got this big idea, loads of interesting directions, and a proposal that sounds genuinely impressive. You feel organised. Capable. Maybe even ahead of schedule.

But then you actually start, and the penny drops...

And very quickly, that big, ambitious idea starts to… unravel slightly.

Not because it was bad, but because reality shows up. Technical constraints appear out of nowhere, things take twice as long as expected, and suddenly you’re making decisions not based on what would be ideal, but on what you can actually build without your laptop, your brain, or your will to live giving up entirely.

That shift, from “this is going to be amazing” to “this is going to work, and work well”, is where things get real.

But what makes it genuinely difficult, and something people don’t really warn you about, is that the dissertation doesn’t politely become your only responsibility.

You’re still doing life at the same time.

In my case, that means a full-time job, keeping the house from slowly descending into chaos, and looking after a small army of cats who have absolutely no interest in deadlines but a very strong interest in being fed immediately and sitting on anything important - usually my keyboard.

The dissertation becomes this thing you’re constantly trying to squeeze in around everything else. Evenings. Weekends. That one hour where you feel vaguely productive before realising you’re actually just tired.

And just to keep things nicely stressful, the full dissertation, including a working prototype, user participation, analysis and documentation, is due on 22/06… which is now close enough that it feels less like a date and more like a threat.

To be fair, the start went well.

Planning, literature review, and initial design were all mostly on track. I even got ethical approval done early, which at the time felt like I had my life completely together.

Reader: I did not.

Because delays will happen.

Mine arrived during development. Things that looked straightforward, especially getting parts of the system working in the browser, turned out to be significantly more complicated than expected. And when your actual working time is limited to “after a full day of work when your brain is running on vibes”, those delays hit hard.

This is where deadlines stop being a suggestion and start being the only thing holding everything together.

Without them, it’s very easy to disappear into a spiral of “just fixing one more thing” or trying to make everything perfect. Deadlines force decisions. They force you to prioritise. They force you to accept that some things are “good enough” and that is absolutely fine.

One of the biggest turning points for me was realising I had to let go of the original plan.

I started out aiming for something quite ambitious, a fully multimodal system. On paper, great. In practice, alongside a job, life, and tight dissertation deadlines, it was… optimistic.

So I've had to scale it back.

This has meant focusing on a more lightweight, browser-based approach and building it in stages. Core functionality first. Aim for the best user experience. Anything beyond that becomes a bonus, not a requirement. It’s less “this will change everything” and more “this will actually be finished”, which, at this point, feels like the bigger achievement.

And honestly, that’s not failure.

That’s survival.

The same thing applies to research questions and methodology. You don’t just set them once and stick to them no matter what. As development progresses (and occasionally fights back), things need to evolve. In my case, it has meant narrowing the focus and prioritising technical performance first, then leaving user testing for when the system is stable enough not to embarrass me.

At this stage, with development well underway and evaluation looming, the focus has shifted again. It’s less about adding more features and more about making sure the current ones actually work, consistently, which turns out to be a full-time job in itself.

A dissertation isn’t just about producing something at the end. It’s about managing constant uncertainty while everything else in your life continues to demand your attention. You’re balancing ambition with time, ideas with reality, and quality with the very real need to sleep occasionally. Not that far different to any large tech project.

And the deadlines?

They’re not there to stress you out.

They’re the only reason this doesn’t turn into an endless project where you keep improving things forever while slowly forgetting what sunlight looks like.

Looking back, the most important thing hasn’t been sticking perfectly to the original plan. It’s been staying structured while adapting constantly. Knowing when to push forward, when to simplify, and when to accept that “done” is better than “perfect”.

That’s what actually gets you through it.