16. Blair
SIXTEEN
BLAIR
Monday morning. Atlanta. The studio.
The north drafting table had the Hartwell elevation drawings spread across it, the Midtown lighting spec open on the laptop beside them, and Emma's annotated punch list for the Buckhead project clipped to the board on the left.
Three active projects in various stages of completion, each with its own timeline, its own contractor chain, its own specific set of decisions that only I could make.
I made them.
The Hartwell grout variance: I'd already called this on Friday. The affected section was being reset. Timeline shifted by three days, which the client had accepted without the conversation I'd been bracing for. Emma had managed the communication precisely. No drama, no escalation.
The Midtown lighting: the clients had approved the fixture placement after two rounds of revised renders.
The approval had come through Saturday morning.
I'd read it at the hotel desk in Jacksonville, typed a two-sentence confirmation, and gone back to reviewing the project file I'd been reviewing when it arrived.
The Buckhead punch list had eleven items, nine of which were Marcus-level decisions. I delegated eight and kept one — the threshold material at the primary entry, which was a judgment call that required seeing the actual stone rather than the spec sheet.
By ten o'clock I'd cleared the backlog that had accumulated over six days of Jacksonville site presence.
I read through the Hartwell approval email a second time.
It said what it had said the first time. The clients had approved. The approval was clear and unambiguous and did not require a second reading. I read it a second time anyway, which was the first indication of the morning that something was running at a slightly different level than usual.
I filed it under: monitor, and closed the email.
—
Emma appeared at the drafting table at ten-forty with the Riverside project file and the expression she wore when she had something that required a decision rather than just a handoff.
The Riverside project was a residential gut renovation in Virginia-Highland — a client referred by the Hartwell couple, which was either a good sign about the Hartwell relationship or going to make any future difficulty with the Hartwells more complicated.
The scope was significant: full kitchen and primary bath renovation, new lighting throughout, flooring replacement on the main level.
The decision Emma needed: the client wanted to add a secondary bathroom to the scope.
"They called Friday afternoon," Emma said. "After you'd left for Jacksonville. They want a quote for the guest bath addition — tile, fixtures, vanity. Full scope."
"Timeline impact?"
"Three weeks minimum, given where we are in the sequence. Possibly four if the tile lead time runs long."
"Budget conversation first, then scope decision. Don't commit to the addition until I've talked to them directly. When are they available?"
"Wednesday morning or Thursday afternoon."
"Thursday afternoon." I made a note. "I have a site visit Tuesday."
Emma wrote it down. She had the particular quality of someone who processed information quickly and didn't require elaboration, which was why she'd been the right hire.
"Jacksonville follow-up?" she said.
The question was neutral. Emma's questions were always neutral — she asked what she needed to know and nothing additional.
"Natalie has a new property she wants me to look at. It's adjacent to the Shaw project in terms of neighborhood and client type."
"Do you want me to request the architectural plans in advance?"
"Yes. Same process as before."
Emma made a second note and moved on to the Buckhead threshold question, which we resolved in four minutes.
I looked at my calendar after she left.
There were two open slots next week where the project didn't require her.
He didn't like the look of them.
Tuesday: Jacksonville. Listed as a site visit for the Natalie referral property.
That was accurate. That was also not the complete picture, and I was aware of the gap between the two.
—
The kitchen appeared at eleven-fifteen.
Not the Atlanta studio kitchen, which was a functional galley off the back hallway that Emma used for coffee and the occasional working lunch.
The Jacksonville kitchen. The island in the right position.
The undercabinet strip. The pendant fixtures at the verified height.
The sightline from the entry to the deck running clear.
I was reviewing tile specifications for the Riverside project and the kitchen arrived without invitation, a specific quality of spatial memory that I'd been noticing more often since Friday.
I closed it the same way I closed irrelevant browser tabs — deliberately, without dwelling — and went back to the tile spec.
It didn't close as cleanly.
She opened a different file.
The Riverside bathroom tile was a Calacatta variant, similar to the Midtown project but with a different vein pattern that would read differently under the client's specific lighting conditions. I had renders. I had the physical sample. I had everything I needed to make the recommendation.
I pulled up the render.
Looked at it.
Pulled up the Jacksonville kitchen pendant spec instead.
Set it down.
The Riverside render was correct. The tile was correct. I wrote the recommendation in the project file and moved on.
The kitchen did not reappear for the rest of the morning.
That was a data point. I moved on.
What I was not examining: why the Jacksonville kitchen had arrived during a tile review. Why the specific image had been the island in its correct position rather than any other detail of the space. Why I'd pulled up the pendant spec before catching myself and closing it.
Those were in the category of things I was aware of and had filed under: not relevant to current work.
I was adding a lot to that category this week.
—
Emma came back at one with the lunch order and a look.
The look was not intrusive — Emma didn't do intrusive. It was the particular quality of attention she deployed when she was observing something she'd decided not to comment on yet.
"You approved the Hartwell threshold tile twice," she said, setting down the order.
"I know."
"The first approval was Thursday. The second was this morning."
"I know that too."
She sat down across the drafting table with her own lunch and opened her notebook. Not asking anything further. The double approval wasn't a problem — it was redundant, which was different. Emma understood the distinction and was choosing to let it sit.
I ate and reviewed the Riverside floor plan.
The floor plan was correct. The load-bearing wall on the north side of the guest bath precluded the expansion the clients wanted without a structural consultation, which was going to complicate the scope addition conversation. I noted it for Thursday.
"The Jacksonville project,' Emma said, not looking up from her notebook. 'How did it resolve?"
"Cleanly. The feature shoot went well. Natalie's office confirmed the publication timeline."
"And the client?"
I looked at the floor plan.
"Professional," I said. "Straightforward scope. Good architecture to work with."
Emma wrote something in her notebook. She did that — wrote things that may or may not have been related to the conversation. I'd stopped trying to determine which.
"The Tuesday visit is a new referral," I said.
"I know," she said. "I'm requesting the plans this afternoon."
She went back to her notes. I went back to the floor plan.
The double-approval was a thing I was not examining. The conversation I'd just had with Emma about the Jacksonville client was a thing I was not examining. Both were in the category of information I was aware of and had filed under: not relevant to current work.
The category was expanding.
—
At three I had the realization I'd been circling since Monday morning.
I was reviewing the Hartwell installation sequence — a document I'd reviewed twice already, which was the second instance of redundant review today — when it arrived fully formed:
This was inefficient.
Not the project. Not the work. The situation. The specific configuration of variables that had developed since the first walkthrough six weeks ago and which was now occupying a layer of bandwidth that I needed for other things.
I ran the assessment the way I ran project assessments: clearly, without sentiment.
Variable one: I was returning to Jacksonville on Tuesday for a reason that was partly professional and partly not. I'd told Emma it was a referral visit. That was true. It was not complete.
Variable two: the project was closed. My professional relationship with the property and its owner had concluded at the final walkthrough. What was continuing was outside the project structure and therefore outside my normal operational framework.
Variable three: I was double-approving documents and redirecting my own attention and reviewing specifications I'd already reviewed. These were small deviations. They were deviations.
The assessment was: this situation did not fit inside my control structure.
I had built a very specific control structure over eight years of running a practice that required precision, client trust, and a professional reputation that was the actual product I was selling.
The structure worked because it was consistent.
Because clients could rely on me to be exactly what I presented myself as being — someone who came in, assessed the situation clearly, made correct decisions, and executed without interference from variables that weren't part of the project scope.
Evan Shaw was no longer part of any project scope.