Week One Survival: Slack, Docs, and the Hidden Rules

Priya Nair

I- I- I once spent, it-it was literally three hours on my first day at a tech firm, just... uh, sitting there trying to figure out if I was allowed to write "looks good to me" on a Google Doc, or if that was, like, exclusively a VP thing. I'm not even kidding. Three hours.

Jordan Avery

Three hours on "looks good to me"? Priya, that is... oh man. But honestly, it's so real. It's the- the- the unwritten stuff, right? Like, nobody puts "how we comment on documents" in the official slide deck. They give you a forty-page PDF on dental benefits, but they don't tell you that if you send a DM instead of posting in the team Slack channel, people think you're, like, hiding something.

Priya Nair

Exactly! It's the decision culture. Is this a "we argue in the Slack thread" company, or is it a "we write a five-page memo and then sit in silence for ten minutes of a meeting to read it" company? Because if you- if you do the wrong one, you just... you feel like you've walked into the wrong classroom on the first day of school. It's chaotic.

Jordan Avery

Yeah, and the- the temptation is always to, you know, make a splash immediately. You want to prove they made the right call hiring you. But I- I always tell people, especially in that first week, you have to look at it as a very specific arc. Day one is really just... it's just survival, right? It's setup, it's- it's getting your laptop to talk to the printer, which is always a nightmare, and just getting basic context. Then days two and three are where the actual work begins, but not by *doing*—by shadowing. You're just... you're watching how people talk to each other, you're asking those really basic questions.

Priya Nair

Wait, so you're saying days two and three are purely passive? Because I feel like a lot of people feel this, like, intense pressure to have a "deliverable" by day three.

Jordan Avery

No, no, not passive, but... let's call it active observation. Because on days four and five, that's when you do the first small contribution. A tiny win. And you use that to check in on what "good" actually looks like. It's not about writing a whole new strategy; it's about doing one small task and saying, "Hey, I did it this way—is this how we do things here?"

Priya Nair

Right, so it's a tension between... um, being proactive and being, well, patient. I- I- I think a lot of new hires jump in and start changing things. Like, "Oh, at my old job, we used Trello for this." And everyone else on the team is just... they're rolling their eyes because they've spent three years building a custom Jira workflow that they actually like.

Jordan Avery

Yes! Oh my gosh, the "at my old job" guy. Nobody wants to be that guy. The faster path is actually to- to slow down. You need to map the terrain first. Who actually owns the decision you're trying to influence? Does a quick question belong in a public Slack channel, or does it genuinely need a fifteen-minute Zoom call? If you don't learn that in week one, you spend week two, you know, stepping on everyone's toes.

Priya Nair

It's so true. I joined a team once where I thought "everyone knows" how to write a project brief. I spent my whole first week writing this massive, beautiful, fifteen-page Word document. I was so proud of it. And then my manager saw it and was like, "Oh, we don't do these. We just... we write three bullet points in a Slack message and tag the engineering lead." I felt so stupid. The real onboarding manual was literally just watching how people reacted when I asked for help.

Jordan Avery

It's always the reactions, isn't it? That's the real culture. Not the- the- the poster on the wall with the company values.

Priya Nair

So, if we're talking about actually surviving day one, we have to talk about the tools. Because if you set them up wrong, you're setting yourself up for a very loud, very stressful month. Let's start with chat. Slack, Teams, whatever it is. What's the move there on day one?

Jordan Avery

Okay, first thing, and- and I mean this, do this in the first hour: set your notification defaults. Turn off the- the random channel pings. Pin the three or four channels that actually matter to your immediate team, and then... this is the golden rule... learn the difference between a "quick question in public" and a direct message. Don't be the person who pings six different people in private for the exact same answer. It-it-it makes you look panicked, and it ruins everyone's focus.

Priya Nair

Oh, the scattershot DM. "Hey, do you know where the log-in is?" "Hey, do you?" "Hey, do you?" And then three people are answering you at the same time and they realize you've spammed them all. It's the worst.

Jordan Avery

It really is. And- and then the second tool is docs. Google Docs, Notion, whatever. Use the company's naming convention from day one. If you name a file "final_final_v3_jordan_edit," you are... you are basically sending that document to a digital graveyard. Nobody will ever find it. The win here is making your notes easy for someone else to build on. Use the date, use the project code, use the team name. It sounds boring, but it's- it's a superpower.

Priya Nair

It's actually a massive trust builder. If I search the drive and I find a doc that is clearly labeled, and it has the right folder logic, I instantly think, "Okay, this person is organized, they respect our time." It's a tiny thing that makes you look incredibly professional. And then, what about the project tracker? Jira, Asana, Monday... those can be so overwhelming when you're new.

Jordan Avery

They really are. The key with the project tracker is knowing what a task card actually needs before it's considered "real." Does it need a due date? A story point? A specific tag? And- and more importantly, when does an update belong in the tracker versus a status meeting? If you can figure that out, you become visible without being noisy. You don't need to post an update every time you open a file, but you do need to move the card when the work is actually done.

Priya Nair

I love that. "Visible without being noisy." That is the absolute goal for week one. So, okay, let's make this super concrete for anyone starting a new gig next week. Three things they need to do in their first five days.

Jordan Avery

Okay, number one: join the main team channels and- and don't just lurk, but read the last two weeks of threads. See how people resolve disagreements. Number two: create and organize your very first working doc using the exact naming format the team uses. And number three: set up your project tracker profile, find one small task that was assigned to you, and move it all the way from "assigned" to "done" by Friday. That's it. Keep it simple.

Priya Nair

Simple is definitely better. Alright, that's a wrap on this one. Good luck to anyone starting day one next week. Go configure those notifications.

Jordan Avery

Seriously. Turn off the beeps. Talk to you later, Priya.