Ethan Hrabak

Essay / Culture

Everyone Has a System and None of Them Work

On the quiet trap of optimizing your life instead of living it.

At some point in the last few years, everyone I know got obsessed with systems. Morning routines. Productivity frameworks. The perfect note-taking app. The optimal way to structure your week so nothing slips through the cracks. And I fell into it too. I spent more time building the system than doing the thing the system was supposed to help me do. I didn't realize it at the time, but that was the whole problem.

There's something appealing about the idea that the right method makes everything click. Your days feel intentional. You become the kind of person who wakes up at 5 a.m. and journals before the sun comes up. But I don't think the fantasy is really about productivity. I think it's about control. If I can just organize my life well enough, maybe I'll stop feeling like I'm falling behind.

The Problem with the Perfect System

Systems aren't bad. Some structure genuinely helps. But most of us aren't using systems to get things done. We're using them to avoid starting. And there's a difference. Building a color-coded spreadsheet for your goals feels like progress. It feels productive. But it isn't. It's preparation pretending to be action, and it's addictive because you get all the satisfaction of doing something without any of the risk of doing it badly.

I've watched friends spend entire weekends moving their task lists from one app to another, totally convinced the app was the problem. I've done it too. But the app was never the problem. Starting is the problem. Starting is always the problem. And organizing feels so much easier than creating that it's almost impossible not to choose it instead.

What Actually Works

I don't have a universal answer. And honestly, I don't trust anyone who says they do. But the closest thing I've found is almost embarrassingly simple: just do the thing before you build the system around the thing. Write before you organize your writing folder. Work out before you design the training plan. Cook before you buy the matching meal-prep containers.

Start messy. Start without a plan. The structure comes from doing, not the other way around. And when it does come, it's better, because it's built on what you actually need instead of what someone online told you works for them.

The irony of writing an essay about overplanning is not lost on me. I outlined this three times before I just sat down and started typing. Old habits.

The Uncomfortable Truth

The people who get things done aren't the ones with the best systems. They're the ones willing to be bad at something long enough to get better. That's it. No framework. No app. Just the willingness to sit in the discomfort of imperfection and keep going anyway.

I'm still working on that. But I've stopped building spreadsheets about it.

Essay / Advice

The Advice Nobody Asked For (And the Kind That Actually Helps)

Why most people are bad at helping, even when they mean well.

Everyone has that friend. You tell them you're stressed about work and they send you a productivity article. You mention you're not sleeping well and they recommend a supplement. You say you feel lost and they tell you to start journaling. And they mean well. They always mean well. But meaning well and being helpful are not the same thing, and I think most people don't realize how wide the gap between those two things really is.

Here's what I've come to believe: most advice isn't given for the person receiving it. It's given to make the person giving it feel useful. That's not cynical, it's just honest. When someone you care about is struggling, the discomfort of not being able to fix it is genuinely hard to sit with. So you offer something. A book. A tip. A "have you tried." It's a reflex. And reflexes aren't the same as responses.

Why Solutions Don't Land

When someone tells you about a problem, they are almost never asking you to solve it. They're asking you to hear it. And that distinction matters more than most people want to admit. Jumping straight to a fix skips the part where the other person feels understood. Without that, even the best advice falls flat. People don't take advice from people who don't get it. They take advice from people who make them feel gotten.

Think about the last time someone gave you advice you didn't ask for. Even if it was good advice. Your first reaction probably wasn't gratitude. It was resistance. Not because the advice was wrong, but because it showed up before you felt heard. The order matters more than the content.

What Actually Helps

The most helpful people I know all share one thing, and it has nothing to do with being smart or having the right answers. They ask questions before they offer solutions. Not leading questions designed to steer you toward what they already think. Real questions. The kind that make you feel like they're actually trying to understand your situation instead of projecting their own onto it.

And sometimes the most useful thing someone can say is just "that sounds really hard." Not because it fixes anything. But because it creates space for the other person to keep talking. And the more someone talks through what they're dealing with, the closer they usually get to their own answer. You don't have to hand it to them. You just have to stop getting in the way.

I think there's a version of this that applies to everything. The best teachers don't lecture. The best writing doesn't tell you what to think. And the best advice doesn't come from someone with all the answers. It comes from someone willing to sit in the question with you long enough for it to become clear on its own.

The Hard Part

Being helpful without fixing is uncomfortable. It requires you to be present without being productive, which goes against basically every instinct most of us have. We want to do something. We want to contribute. Sitting with someone in their mess without reaching for a mop feels passive. But it isn't. It's generous. It's just a kind of generosity that doesn't look like anything from the outside.

Next time someone comes to you with a problem, try not solving it. Ask what it feels like. Ask what they've already tried. Ask what they think they need. You might be surprised how often the answer isn't advice at all. It's just someone willing to listen like they actually care. And honestly, that's rarer than any tip you could give.

Explainer / Communication

Why You're Bad at Giving Feedback (And What to Do Instead)

Most people confuse honesty with bluntness. There's a better way.

At some point, someone told you that good feedback is honest feedback. And that's true, as far as it goes. But the problem is that most people hear "be honest" and take it to mean "say whatever you're thinking with no filter." They call it being direct. They call it being real. What it usually is, though, is lazy. Honesty without thought isn't bravery. It's just carelessness with plausible deniability.

Good feedback is honest, yes. But it's also specific. It's intentional. And it's delivered in a way the other person can actually do something with. That last part is where most people completely fall apart.

The Problem with "Just Be Honest"

When someone asks you for feedback, the instinct is to lead with what's wrong. It feels useful. It feels like you're adding value by spotting problems. But if that's all you're doing, you're not giving feedback. You're handing down a verdict. And verdicts don't help people get better. They just make people shut down.

The other extreme is just as bad. Telling someone "it's great!" when it clearly isn't doesn't help anyone either. It's comfortable. But it's not kind. Actual kindness is caring enough to be specific about what's working and what isn't, and doing it in a way that respects the other person's intelligence. That takes effort. Most people don't want to put in the effort. So they either go too hard or don't go at all.

What Good Feedback Actually Looks Like

Start with what's working. And I don't mean as a warm-up before you get to the real stuff. I mean because it actually matters. When you tell someone what they did well, you're giving them a signal about what to keep doing. That's information they need just as much as knowing what to fix. If you skip it, they're left guessing about whether any of it landed. And guessing is exhausting.

Then when you get to what could be better, be specific. "This section is confusing" is not helpful. "I lost the thread between the second and third paragraphs because the transition felt abrupt" is. The first one tells someone something is wrong. The second tells them where it went wrong and why. One creates frustration. The other creates a path forward. And the difference between those two things is everything.

Here's a good test: if your feedback could apply to literally anyone's work, it's too vague. "Tighten this up" means nothing. "The point in paragraph three could land in one sentence instead of four" means everything.

Tone Matters More Than You Think

You could have the sharpest, most insightful critique in the world. But if you deliver it with even a hint of condescension, the other person is going to shut down before they hear any of it. That's not a character flaw. That's just how people work. We process tone before we process content. If the tone feels hostile, the content doesn't get through. It doesn't matter how right you are.

That doesn't mean sugarcoating everything. It means caring about how you say something as much as you care about what you're saying. Be direct. But be direct in a way that assumes the other person is trying. Because most of the time, they are. And they deserve to be treated like it.

The Real Point

Feedback isn't about proving you have good taste or a sharp eye. It's about helping someone get closer to the thing they're trying to make. If your feedback doesn't do that, it doesn't matter how honest it was. The goal was never to be right. The goal was to be useful. And being useful takes more care than most people are willing to give.

But it's worth it. It's always worth it.