I Was Running by Day One. Usually That Takes Weeks.
Situation
I started a new job about a month ago. Walking in, I braced myself for a familiar kind of pain. At my last company, I'd built a whole stack of Google Apps Scripts, PowerAutomate flows, and manual processes to handle the stuff that eats an organized person's day: pulling Zoom transcripts into meeting notes, chasing action items out of Slack and email, keeping a task list that didn't quietly rot. None of that comes with you when you change jobs. I figured I had a few weeks of rebuilding ahead of me before I felt normal again.
The AI Move
Day one, I opened Claude Cowork and started connecting things. Zoom. Google Drive. Smartsheet. Then Calendar, Gmail, Slack. I wasn't trying to be ambitious about it. I was just checking what was actually available to me at this company, since my last one hadn't enabled Claude Cowork yet.
By the end of the first week I had scheduled tasks running throughout the day. Every morning it goes through my calendar, builds a document for each meeting, and goes looking for anything I need to walk in knowing, such as an open Slack thread or an email that never got a reply. After each meeting, it checks back at 30, 60, and 90 minutes for the Zoom summary and transcript and drops them into that same doc. At night it sweeps for anything that turned into a task, checks it against what's already on my Smartsheet to-do list so nothing gets duplicated, and updates my stakeholder notes with whatever came up that day.
That last part is the one that got me. Somewhere in week two, someone on a call said, "you should really talk to so-and-so about that." I didn't know so-and-so. I'd never met them. But I looked them up anyway, and there was already a profile: their name, how they're involved in one of the programs, tied to a reason, pulled out of a Slack thread and two meetings where their name had come up but they hadn't been in the room.
The Shift
Starting a new job is a little like the first day of school. You don't know the norms yet. You're reading the room for who matters and trying to sound like you belong before you're sure you do. Usually that means a lot of listening mode: nodding along to names you're quietly filing away, hoping you don't have to ask who someone is twice.
I didn't do much of that this time. When people said names, I mostly already had somewhere to put them. Not because I'd met everyone, I hadn't. But because I had context waiting for me before I needed it. That changed how I showed up. I was asking questions instead of just absorbing information. I felt like I was participating in my first week the way I'd normally expect to by month two.
The Pattern
I don't think the value here is really about the automation. It's that the context arrived before I did. Usually you earn context by being in the room enough times, hearing the same name enough times, sitting through enough meetings to notice the pattern yourself. This time the pattern was sitting there waiting on day three.
That's a different kind of confidence. It doesn't come from knowing more than everyone else in the room. It comes from not needing to catch up while everyone else assumes you already have.
The Implication
If you're starting something new, a job, a program, a team, and you have access to connectors like this, don't assume you need to rebuild what you used to have from scratch. Check what's actually available to you first. I was so used to building everything myself that I'm still amazed at the speed in which I was able to get up and running in a new role in a new company. It was all sitting there waiting for me to click "Connect."
What I'm Testing Next
Two weeks in, I already went back and refined the setup. Added more depth in a couple of places, tightened up a few things that were producing more noise than signal. I'm planning another pass around the four-week mark. Nothing about it has stayed static, and I don't expect that to change anytime soon.
Comments