# Should I Ask to Go Remote? My Manager Said "We'll See" Three Months Ago.

I asked to go remote three months ago. My manager — a good manager, genuinely — said "we'll see," in the way that means "I don't want to say no to your face." Then nothing. No follow-up. No conversation. Three months of me checking my email like a man waiting for a verdict that was never coming.

Here's the thing I can't fully explain: I don't even know if I want to go remote. I thought I did. The commute is brutal, the open office is loud, and I do my best work in the morning before anyone else arrives, which feels like a waste of the person I am at 8am. But when I actually sat down to write the request, something in me stalled. Not about the logistics — about something I couldn't name.

So the request went in lukewarm, and the "we'll see" came back, and the whole thing just... sat there. Occupying more mental space than it deserved, the way unresolved things always do.

The three reasons I wasn't pushing

I told myself I was being patient. Here's what patience was really covering:

What the reading said

I did a reading. The question: should I ask to go remote?

The reading didn't weigh productivity metrics. It asked: what are you afraid of losing when they can't see you anymore?

And that was the thing I'd been circling for three months.

I wasn't afraid of losing the work. I was afraid of losing the visibility — the being-seen. The casual hallway conversations where my manager learns my name is attached to good work. The "oh, she's in, let me grab her" moments. The small, invisible-to-me economy of presence that I'd been using as proof that I mattered. Going remote meant gambling that my actual work was worth more than my proximity — and some part of me wasn't sure it was.

The request wasn't really about the commute. It was about whether I'd built my career on being present or on being good. I'd been avoiding the answer for three months, and the "we'll see" was just the excuse I needed to keep not finding out.

What happened

I pushed. Not pushy — clear. I booked a meeting, laid out the case: the hours I'd save, the work I'd done remotely before, the trial period I was willing to do. And I said the sentence I'd been avoiding: "I'm asking because I think I can do this well, and I'd like to prove it over a trial month."

He said yes. Trial month, then we'd review. And here's what surprised me: the visibility I was terrified of losing — it was mostly in my head. The work got done. The calls happened. Nobody forgot I existed. My manager said, at the end of the month, "I didn't realize you did that much of the thinking on this project" — which was exactly the sentence I'd been scared of, and it turned out to be a compliment.

The reading didn't get me the remote job. It showed me that I'd been confusing visibility with value — that I'd built a career on being seen because I wasn't sure my work could stand alone. It can. It always could. I just hadn't been willing to test it.

Anyway. I'm remote now, mostly. And I still miss some hallway conversations. But I don't need them to know I exist anymore, and that's the part that changed.

If there's a request you keep making softly — or a "we'll see" you've been waiting on for months — try a reading. Three numbers. No account. It won't book the meeting for you. But it might show you what you're actually afraid of asking for, and whether the no you're bracing for is coming from your manager or from you.

FAQ

Q: How do I bring up remote work without sounding demanding? A: Lead with the work, not the commute. "Here's what I did remotely before, here's how I'd structure the week, here's a trial period I'm willing to do." A clear proposal with a test attached is hard to say no to. The "we'll see" you've been waiting on isn't going to resolve itself — you have to close it. See also: The Office Party Is Thursday. I've Dreaded It Longer Than It'll Last. — the visibility economy runs both ways: what you gain by being seen, and what it costs to need it.

Q: What if the answer is no? A: Then you have information, and information is never wasted. A no tells you where you stand: whether remote is a hard rule or a trust issue, and what you'd need to do differently to earn it. What costs more than a no is the months you spend waiting on a "we'll see" that was never going to resolve itself.

Q: How do I know if remote is actually right for me? A: Look at your track record, not your fantasy. When I worked from home during the extended stretch, did my output go up or down? Did I get lonely or productive? The answer was in my own history — I just hadn't wanted to look at it, because looking meant I'd have to act.

Q: How does a reading help with a work request like this? A: It separates the request from the fear underneath it. I thought I was deciding whether to ask for remote work. I was actually deciding whether I could stop relying on being seen to feel valuable. The reading named the real question, and once it was named, the request itself got easy.