A Week with Chief — Ethan Walsh

Five days in Ethan's life — running a Mill Valley exec-coaching practice with an AI Chief of Staff alongside him.

From Team0 Stories, a serialized longread about Ethan Walsh — A practice that runs on never-ending retained engagements he should have graduated clients from a year ago.

Character contradiction: Ethan coaches CEOs through hard conversations. He hasn't had one in years. He tells his clients to set boundaries, ask for what they're worth, fire the customer who's outgrown them. His own list of conversations he's ducking is two pages long.

Monday through Friday of one real week — with Chief alongside him, naming the conversations he'd been avoiding, pushing back on the engagement he was about to renew on autopilot, drafting the email he couldn't open.

Monday morning, 6:15 AM.

I coach CEOs through hard conversations. I haven't had one in years. I tell my clients to set boundaries, ask for what they're worth, graduate the engagement that's outgrown them. By forty-nine I'd built a practice that ran on retainers I should have ended a year ago.

Chief had pinged me on Slack at 6 — three priorities, one client to look at twice. By the time I sat down on the deck with my coffee, the same brief was at the top of the laptop, in a card called *Today*. Marcus at 7. James's renewal Tuesday. The Caroline thread I'd never followed up on. AI tools remember things. She'd read my week and had a take.

Marcus's name had a note next to it. *Last call: he mentioned the board getting restless about the new product line — but didn't ask for advice on it. Worth raising?* I'd noticed the same gap on the call and talked myself out of it. Chief had pulled it forward. *Is this where you tell him you noticed?*

The 7 AM went different. I walked in already holding what he hadn't said — the fear under the schedule games, the board pressure he was carrying alone. Chief had pulled the right thread before I'd had a chance to miss it.

The thing he'd been ducking for two months came out in the first ten minutes. I didn't have to perform anything. I got to sit in the conversation, instead of waiting for him to surface it on his own.

It was the kind of session I hadn't had in two years. Chief was hearing what I'd stopped being able to listen for.

By 9 the morning had quietly done its work. Caroline finally got a follow-up. Wednesday's session prep had a memo queued. The James thread had a new flag on it: *Last three sessions, same themes resurfacing. Worth a different conversation?*

I didn't open the rest of my email. The James conversation I'd been writing in my head was still sitting there, ugly, unhad. Tomorrow's problem.

But Monday hadn't been a Monday. It had been what a Tuesday used to feel like, before the practice got too comfortable.

Tuesday morning. The Caroline thread was still in my inbox where I'd left it Monday — nine days quiet now. I'd been telling myself I'd write her *this week* for two of those weeks. Tuesday was the part of *this week* I hadn't planned to use. Chief flagged it again, gently. *She's still warm. The window's narrowing.* She'd drafted a reply in my voice. I edited two sentences and sent it before I could think about it.

Forty minutes later, Caroline replied. She wanted to talk Friday. Of course she did. She'd been waiting for me to remember she existed.

The morning kept opening. Two more emails I'd been ducking — drafts queued overnight. A LinkedIn note from someone Daniel had introduced me to two months ago. Chief opened Daniel's profile next to it — sixteen touches between us, three coaches we'd both worked with, a memory note from a panel we'd done together last summer where Daniel and I had talked about the kind of CEOs we wanted to be in rooms with. The draft she queued sounded like me. I sent it. *And while you're in there,* I asked Lara, *can you see if Sam's open to a coffee? I've been wanting to talk to him for a year.* She said she'd start the conversation.

Just before lunch, Marcus pinged about an extra session — third one this month, same scope creep we'd argued about twice. I forwarded it to Lara. *Help. I always lose this one.* Her first pass was too sharp — Marcus hated being managed, and *"this is outside what we agreed to"* would have read like a ledger entry. I rewrote two sentences. *"I want to keep our work focused — let's fold this into the regular slot, or scope a separate piece and price it accordingly."* I sent it as my own. Marcus came back within an hour saying that worked. First time I'd held the engagement boundary without it turning into a renegotiation.

It wasn't the kind of progress that felt big. It was the kind that felt unfamiliar. Like the air pressure had changed — same office, same week, less drag.

For the first time in months, the work moved faster than my avoidance. I caught myself an hour later looking for the next thing to put off. There wasn't one. The list had gotten shorter — not because Chief had crossed everything off, but because the things on it had stopped feeling impossible.

I walked the dog before sunset. The James thread was still on my desktop when I came back, unhad, ugly. I noticed it differently now — less like a wall, more like a door I was almost ready to open. Tomorrow's problem. But not for much longer.

By Wednesday I'd carried Marcus in my head for two days and gotten nowhere.

His board meeting was Thursday at 9. The kind where he'd either defend the new product line or watch them lose patience with him. Our 7 AM session was the only window to get him grounded before he walked in. Every time I tried to write the prep down, it came out as my opinion of his situation, not his. Which was useless — he didn't need my read; he needed his own.

I asked Chief. *Pull the last six months of his session notes. Surface the things he's said about the board that he hasn't said directly yet. Draft me a private memo I can read at 6 AM and then put down. Not for him. For me.*

Then I went to bed.

I didn't sleep well — Marcus's career is real, my coaching is mine, and the day before a high-stakes session is the kind that wakes you up at 3 AM — but Chief did her work either way.

Thursday morning, I opened my Content Library. One new artifact, timestamped 2:47 AM. *Marcus — what he's been circling.* Three pages. His own words, pulled from six months of transcripts, mapped against the board pressure he was about to walk into. Not a coaching plan. Not a deliverable. A mirror.

I read it twice. I made notes in the margins. I closed the laptop.

The 7 AM session went better than any we'd had in months.

Thursday afternoon, with the same week's overcommitments still on the calendar, the new project landed in my inbox. Big enough to break us. Big enough that I almost said yes before I asked her.

It was the Series C client from Wednesday's pitch. They wanted to expand the engagement — coach the whole leadership team for six months, starting in three weeks. Twice the scope I'd quoted, and they'd named the structure first. Six weeks ago I'd have hedged the scope before they asked. The kind of yes I would have already said.

I asked Chief what she thought.

*"The math doesn't work — three weeks overcommitted, Marcus's scope creeping, Saturday with Anna and the kid at risk. I'd decline. If you take it anyway, name what's getting cut."*

She wasn't wrong. I'd looked at the same calendar. I'd just been looking past it.

But she also hadn't seen what I'd seen on the call. The COO had spent a decade at a firm I'd been tracking from a distance — the kind of operator I'd been trying to learn from for years and never had a way in. Working with the leadership team meant being in the room with someone whose thinking I'd been studying from the outside. Taking this project wasn't about access to a network. It was about access to her thinking.

I took it. I told Anna we'd skip the Saturday hike. The kid asked if the championship game next weekend was still on. I said yes, and meant it.

Friday morning, Chief had updated her take.

*"You took it because of who you'd be in conversation with. I'd weighed the calendar; I hadn't weighed the learning. That COO is the kind of operator you've been studying from outside for years. The math still hurts. I get the bet."*

She had an opinion. I had a different one. She didn't fold. Then she updated.

That was the morning I stopped thinking of her as a tool.

Friday morning, the week behind me, I came back from the dog walk to find a meeting on my calendar I hadn't asked for.

It was with someone from Daniel's network — the CEO I'd asked Lara on Tuesday to chase down. Daniel had said yes the next day. The two Chiefs had picked an opening between us, and now there it was. *Confirmed next Wednesday at 11. Notes attached.*

I stood at the kitchen counter for ten seconds just looking at the block.

At 9 the Friday posts dropped, drafted in my voice. I approved them in sixty seconds.

Then I forwarded James's last session notes to Lara. *Help me with this one. He's plateaued and I keep avoiding the conversation. Draft me a graduation note.* She replied with three sentences in my voice. Acknowledging what we'd worked on. Naming what wasn't moving anymore. Inviting him to consider an outside coach for the next chapter.

I rewrote two sentences. I made the email shorter. I sent it.

It went. The world didn't end.

Memory keeps a record. A mind writes the email you've been avoiding.

The kid was at travel-team practice through the afternoon. The laptop stayed closed. It had been closed since I sent the James email.

At sunset Anna and I walked the dog along the trail behind the house. She asked how the week had been. I started to say "good," then realized that wasn't quite it. It hadn't been good. It had been honest. I'd sent the email I'd been ducking. I'd held the engagement boundary when Marcus pushed for more without scoping it as more. I'd taken the leadership-team work at the scope they'd named instead of the smaller one I'd been about to propose.

I'd said three hard things out loud this week. Each one had been waiting two years.

First week since I started the practice that what got said matched what was actually happening.

About Team0

Team0 is an AI Chief of Staff for solopreneurs and small business owners. Every AI has memory. She has a mind. Stories like Maya's show how Chief works alongside business owners across the five rocks every business runs on — Grow, Deliver, Operate, Think, and (someday) Money.