this is getting bad. how many of your followers have ever replied to you? mine is a small slice of that chart. X's algo is a total mystery.

A product's onboarding shouldn't teach me everything it can do. It should help me get one useful result quickly enough that I want to keep going. Give me a win first. The rest can come later.

You don't always need a new productivity system. Sometimes you need to stop accepting meetings that could've been a message, stop checking notifications every ten minutes, and finish one thing before opening five more tabs.

With ZenStack, the aim is to make remote hiring less of a guessing game for growing teams. Find suitable candidates for roles like SDR, appointment setter, or social media manager, then choose the person who fits your actual needs. The hire should make your workload lighter, not create a new job managing the hiring process.

A quiet milestone that deserves more credit: when a process works without you having to think about every step. A repeatable sales routine. A reliable onboarding flow. A task someone else can own. That's progress, even if there's nothing flashy to announce.

A remote hire who asks a thoughtful question before starting can save you hours of rework later. I'd rather work with someone who clarifies the goal than someone who silently makes the wrong assumption.

A website doesn't need to impress me in the first five seconds. It needs to help me understand what it does, who it's for, and whether it's relevant to me. Pretty is nice. Clear is useful.

What's one thing you refuse to compromise on when choosing a tool? For me, it gets harder to justify a tool when it makes a simple task feel complicated.

There's a difference between being responsive to customers and letting every customer steer the roadmap. Listen carefully. Look for patterns. Then make a decision. You can respect feedback without automatically implementing it.

Hiring is expensive in ways that don't always show up on the invoice. Time spent reviewing CVs, scheduling interviews, chasing responses, and restarting when the fit is wrong adds up quickly. The process matters almost as much as the final hire.

What's one thing you bought because it looked impressive, then barely used? No judgment. Some of my favourite lessons have come with receipts.

Hiring someone remotely is easy to describe and harder to get right. The real test is what happens after the first week: do they understand the priorities, communicate blockers, and move work forward without constant chasing? That's the kind of ownership worth hiring for.

An idea isn't validated because your friends say they'd use it. They're being supportive, and that's fine. Ask someone to change their current behaviour, spend money, or make time for it. That's when you start learning something useful.

I've started paying attention to how many times a product makes me stop and think. Where do I click? What does this mean? Did that save? Every little moment of confusion adds friction. Good design quietly removes those moments.

A founder can spend an entire week improving the product and still make no progress on getting customers. Building feels productive because you can see what you've made. Distribution often feels uncomfortable because you can't control the response. Both deserve time on the calendar.

What's a task you genuinely enjoy doing that most people around you seem to hate? I'm curious how different the answers will be.

A tiny thing that makes me trust a product more: When something goes wrong, it tells me what happened and what I can do next. Don't just show me an error code and leave me to figure it out.

A useful question before starting a new project: “What would make me stop working on this?” If you don't define that early, it's easy to keep investing time just because you've already invested time.

When hiring for a growing team, I care about more than whether someone can talk confidently in an interview. Can they do the work? Can they explain their thinking? Can they take feedback without getting defensive? That's what I'd want to understand.

One of the easiest ways to waste a month building a product is to treat every positive comment as validation. Compliments are nice. Repeated use, honest feedback, and willingness to pay tell you much more.