Not a highlight reel. Full sessions, start to finish.

That one tends to stick around — not just the answer itself, but the not-knowing-why. A few quick questions to get it on the table:

1. 1In a line or two: what was the question, and what were you hoping your answer would do?
2. 2What's sitting with you about it — what feels unresolved, off, or worth pulling apart? List whatever comes to mind, even small things.
3. 3While you were answering, what was going through your head?

That's useful — especially number three. That's the most important piece. Let me work through what you've given me.

The "weaknesses" question is one of the most structurally awkward in interviewing. There's a real tension baked into it: be honest, but not too honest. Show self-awareness, but also competence. That tension alone can make it hard to land cleanly, even when you know your material.

A few things stand out from what you've described:

The rambling itself — you said you were telling yourself to get to the point while answering, but hadn't formulated what that point was before you started. That suggests the issue wasn't what happened during the answer so much as what didn't happen before it. Did you have a prepared structure going in, or were you building the answer in real time?

The "always fall over on it" pattern — this is worth separating out. Is it that you don't know what to say about your weaknesses, or that you know roughly what you want to say but it never comes out the way you want it to? Those are two different problems, and they point in different directions.

One more thing to check: when you say you were telling yourself to get to the point — was that happening from the very start of the answer, or did it kick in once you felt it starting to go sideways?

Good — that fills the picture in nicely. A few things are now pretty clear.

On the "get to the point" moment: that's consistent with what you described. It kicked in once things were already sliding, which means it wasn't interference that caused the ramble — it was a response to it. So I'm not going to put weight there.

What's actually going on looks like two distinct things:

The first is a preparation issue with a specific shape. You had an answer, but mid-interview you started judging it against an imagined standard — is this good enough? — and that doubt pulled you off the prepared answer without replacing it with anything better. The problem wasn't that you were unprepared. It was that your preparation didn't include enough confidence in the answer itself.

The second is the harder one. You don't know what to say because you're trying to solve the wrong problem. You're trying to find a weakness answer that sounds fresh and creative — essentially trying to win a game you think everyone else is playing badly. That's a real instinct, but it's also what's keeping you stuck.

Can I ask: what's the answer you've been preparing? Or roughly what shape does it take? I want to see whether the "it's not good enough" judgement is accurate, or whether you're discarding something that would actually land.

That's a really clear account — and it tells me a lot.

First: the answer itself is actually good. It's specific, it's real, it's self-aware. That's exactly what interviewers are looking for. The instinct that it wasn't good enough was wrong.

What happened is that you started defending it mid-answer — against objections the interviewer hadn't made. You anticipated how it might land badly, tried to pre-empt that, which opened a new vulnerability, which you then tried to pre-empt, and so on. The rambling wasn't because you had nothing to say. It was because you were arguing against an imaginary hostile read of your own answer while simultaneously delivering it.

That's a specific pattern and it has a specific fix — but let me make sure I've got everything before I wrap this up. Two things worth naming:

The "sounds like everyone else" worry — does that still feel like a live concern now that you've described the actual answer? Because what you described doesn't sound generic to me.

And the cycle itself — is this something that happens across interview questions generally, or is it particular to the weaknesses question?

There's something worth naming straight away: you already have the plan. The gap isn't knowledge — you're not here because you don't know how to run three times a week. The gap is between the plan on paper and the version of you at 6am (or whenever it is) who keeps not doing it.

That gap usually has a reason, and it's rarely laziness. It's almost always something more specific: a friction point that makes starting harder than it looks, a time that doesn't actually fit your life as it is, or a version of the goal that sounds right but doesn't feel compelling once it's actually in front of you.

So before we try to fix the doing — what does "not doing it" actually look like? Is it that you're skipping sessions you'd planned, or that the sessions never quite make it onto the day in the first place?

So the intention is real — you're not avoiding the idea of running, you're just consistently finding a reason not to when the moment actually arrives. That's a different problem than not caring: the commitment is happening in the abstract (this week, tomorrow morning), but something dissolves it when it gets concrete.

That usually means one of two things: either the moment you've picked has too much friction in it — something about that morning that makes not running the easier choice — or the version of yourself who made the plan and the version facing the actual run aren't quite connected. Future-you commits. Present-you finds a reason.

One thing I'd want to know: when you don't go, what actually happens? Is it that you wake up and talk yourself out of it, or does it never even reach a decision — you just drift past it?

That's a really clear pattern — and it's useful, because it tells us exactly where the problem lives. It's not the run itself. It's the decision point. Every morning you're giving yourself a fresh negotiation, and your brain is very good at winning it.

The fix isn't more willpower or more commitment. It's removing the negotiation entirely. The people who run consistently don't out-motivate themselves every morning — they've made the decision in advance, in a way that makes opting out feel like the active choice rather than the default.

A few things tend to break this specific pattern:

• The night before matters more than the morning. Kit out, shoes by the door, nothing to decide. Make running the path of least resistance, and not running the thing that requires effort.
• "Later" is a lie your brain tells you. Not because you're weak — because "later" almost never has better conditions than "now." If it's not morning, it probably won't happen, and you likely already know this.
• The tiredness excuse is usually true and usually irrelevant. You probably are a bit tired. Most people who run regularly are also a bit tired. The run almost always feels better than the alternative once you're moving.

What I want to ask: is three times a week actually realistic for where your life is right now, or is it an aspirational number that's been quietly intimidating you into paralysis?

Good — that's a clean brief. You've got the capacity, you know the pattern — you just need a system that takes the decision out of your hands and handles the motivation problem structurally, rather than asking you to feel like it every time.

I can build you a proper plan around this. Before I do — roughly how many days a week do you have mornings free, and are there specific days that are harder than others? That way I can make the plan fit your actual week rather than an ideal one.

Perfect — that's enough to work with. Here's a system built around your actual week:

The only thing I'd add: don't measure this by how the runs feel for the first couple of weeks. Measure it by whether you went. The feeling comes later — consistency comes first.