My Boss Thinks I’m Productive

He dragged a blue block labeled “Deep Work” across the morning. Then he added “Cross-Functional Alignment” at eleven, “Stakeholder Review” at one, and “Strategic Touchpoint” at three-thirty. None of these meetings existed. Evan had invented them from phrases he had overheard near the coffee machine.

Dave rolled his chair over, his coffee trembling in its paper cup.

“Are you scheduling meetings?” Dave asked.

“I’m protecting my time.”

“You’ve scheduled four meetings to protect your time.”

“That’s how protection works.”

Dave examined the screen. “What’s a strategic touchpoint?”

“A meeting where people touch strategy.”

“Do they wash their hands first?”

Evan clicked save. “Don’t undermine the process.”

Across the aisle, Linda lifted her head from behind a monitor. Linda somehow knew everything before HR did, including which printer was about to jam and who had cried in the stairwell during the quarterly review.

“Marla’s walking around,” she said.

Evan’s fingers froze.

“Walking around where?” Dave asked.

“Near the shared calendar screen.”

That was not a location. That was a weather warning.

Evan glanced toward the screen. Marla was standing near it with a tablet tucked against her chest, studying the colored blocks. She wore the expression of someone inspecting a suspiciously clean kitchen. Her heels clicked across the floor, each step making Evan’s invented productivity feel more legally binding.

He turned back to his monitor and began typing.

“What are you typing?” Dave whispered.

“An update.”

“To whom?”

“Everyone.”

The document contained one sentence: “Progress remains aligned with current priorities.”

Evan highlighted it, copied it, and pasted it three times beneath itself. The result looked almost aggressive.

Marla stopped beside the shared calendar screen.

“Evan,” she called.

He waited half a second, the length of time he imagined a genuinely busy person would require before acknowledging the outside world.

“Yes?”

“Could you come over here?”

He stood, carrying his coffee as a prop. The coffee had gone cold, but cold coffee was still evidence of a morning spent working.

Marla pointed at the screen. “Walk me through your day.”

Evan smiled. “Absolutely.”

The screen showed his name in a column of blue, green, and orange rectangles. It looked magnificent. It looked exhausting. It looked like he had been entrusted with the company’s most delicate problems.

“I’ve got deep work first,” he said. “Then cross-functional alignment, followed by a stakeholder review, and later a strategic touchpoint.”

Marla nodded slowly. “That’s a lot of collaboration.”

“It’s important to keep momentum.”

“Who’s in the stakeholder review?”

Evan looked at the block. He had forgotten to add attendees.

“Stakeholders.”

Marla waited.

“Various stakeholders,” he added.

Her gaze sharpened. “Which ones?”

Evan reached for the tablet mounted beneath the screen. The plastic casing was warm from constant use. He tapped the invitation, intending to add a few names from memory. Instead, his thumb hit a small icon marked with two rotating arrows.

The calendar refreshed.

The blue “Deep Work” block vanished.

At the same moment, the orange “Strategic Touchpoint” expanded across the afternoon and landed directly on top of Marla’s weekly leadership meeting.

The screen made a soft electronic chime.

A red warning appeared.

DOUBLE-BOOKING DETECTED.

For one perfect second, nobody moved.

Then the shared calendar announced, in a voice designed for elevators, “Conflict detected.”

Dave’s coffee stopped trembling. Linda slowly lowered her monitor.

Marla looked at the screen, then at Evan.

“Conflict?”

Evan’s mouth opened. His brain offered several explanations, all of them terrible.

“It’s a sync issue,” he said.

Marla tapped the screen. “You’re double-booked with my leadership meeting.”

“Yes.”

“And you created the other meeting.”

“Yes.”

“So the system synced your schedule with itself?”

“Not exactly.”

The shared calendar chimed again.

“Conflict detected.”

“Thank you,” Evan muttered.

Marla folded her arms. “What is the strategic touchpoint?”

“It’s a high-priority discussion.”

“With whom?”

Evan glanced at the attendee field. The calendar had selected every person whose name began with the letter E, including Evan, an employee in another department, and an equipment mailbox used by Facilities.

“With a cross-functional group.”

“The equipment mailbox is attending?”

Evan looked at the screen. The equipment mailbox had accepted.

“It has a broad operational perspective.”

Dave made a noise that could have been a cough if coughs occasionally contained the word “equipment.”

Marla’s eyes moved from the invitation to Evan’s face. “Why is your meeting scheduled during mine?”

“It wasn’t.”

“It is now.”

“That’s the sync error.”

“You just said it wasn’t.”

“I mean, it wasn’t originally, but the error made it become now.”

The shared calendar chimed a third time.

“Conflict detected.”

Marla reached for the tablet. Evan moved first.

“I can fix it.”

He tapped the orange block and dragged it toward four o’clock. The screen lagged. His finger slipped. The meeting landed at 4:00 a.m.

A new warning appeared.

OUTSIDE WORKING HOURS.

Evan dragged it again. This time the block jumped to the following Friday and duplicated itself. Two orange rectangles appeared, one labeled “Strategic Touchpoint” and the other “Strategic Touchpoint (2).”

The equipment mailbox accepted both.

Linda whispered, “Facilities is going to love this.”

Evan selected the duplicate and pressed delete. The calendar froze. The screen went gray, then returned with every meeting shifted fifteen minutes earlier.

His deep work now began at 7:45.

The stakeholder review overlapped the cross-functional alignment.

The strategic touchpoint overlapped both.

Marla’s leadership meeting had moved to 8:30, which was technically in the past.

The screen displayed a notice: “Some events may have been modified by another user.”

Evan looked at Marla. “That’s encouraging.”

“Who is another user?”

“I’m not sure.”

“You’re the owner of these invitations.”

“Ownership is complicated.”

Marla stepped closer to the screen. Her perfume smelled faintly of peppermint and administrative authority.

“Evan, cancel the touchpoint.”

“I can’t.”

“Why not?”

“It’s already in progress.”

“It begins at three-thirty.”

“Calendar time is fluid.”

Marla stared at him.

Evan could feel the office listening. Keyboards continued clicking, but more slowly now. Someone at the far end of the room opened a bag of chips with the careful silence of a person attending a live performance.

Marla pointed at the red warning. “I need an explanation.”

Evan had prepared for many workplace emergencies. He had a folder called “Urgent,” though it contained only screenshots of unread emails and a sandwich receipt. He had not prepared for a calendar to publicly accuse him of inventing a meeting with a mailbox.

He tried the truth, trimmed until it was unrecognizable.

“I was reorganizing my availability to ensure uninterrupted focus while maintaining alignment with key stakeholders.”

Marla blinked. “You made a fake meeting.”

“I would call it a placeholder.”

“You invited Facilities equipment.”

“That was accidental.”

“You’re double-booked with me.”

“That was the sync.”

“You’re also scheduled for deep work at 7:45.”

“That was an ambitious start.”

Marla picked up the tablet. “You’re coming to my leadership meeting.”

Evan’s stomach dropped, not from fear but from the sudden disappearance of his lunch hour.

“I have a stakeholder review.”

“Cancel it.”

“It may be difficult.”

“Why?”

“It has stakeholders.”

“Evan.”

He looked at the calendar. The screen had stopped flashing, but the red warning remained, glowing above his name like a small digital confession.

“Fine,” he said. “I’ll attend.”

“Good. And after that, we’ll review your calendar.”

His calendar.

The phrase landed with the weight of an audit.

Marla walked away toward the conference room. Evan stood beneath the shared screen while his invented schedule continued betraying him in public. At 9:02, the equipment mailbox sent a response.

“Unable to attend due to maintenance.”

Dave rolled closer.

“You’re going to the leadership meeting,” he said.

“I know.”

“With leaders.”

“I know.”

“Actual stakeholders?”

“Apparently.”

Linda leaned over the divider. “Marla asked me whether your schedule was accurate.”

“What did you say?”

“I said it was accurate in the same way a weather app is accurate when it predicts rain inside a building.”

Evan looked at her.

“She didn’t like that,” Linda added.

The conference room smelled of dry-erase markers and the lemon cleaner Facilities used whenever someone important was expected. Evan took the last empty chair beside a bowl of wrapped mints. Marla sat at the head of the table, tablet in front of her, while six department heads opened laptops with the solemnity of people preparing to witness a budget.

Evan had intended to look booked solid. Instead, he was now physically trapped inside one of the blocks he had created.

Marla began the meeting.

“Before we discuss priorities, I want to address a scheduling discrepancy.”

Every head turned toward Evan.

He held his coffee under the table. It was still cold.

“There was a sync error,” he said.

Marla nodded. “Evan believes the calendar created a conflict.”

“It did.”

“After he created the event.”

“Before it became a conflict.”

One of the department heads, a man named Paul who wore suspenders without visible need, leaned forward. “Was this an automated workflow?”

Evan seized the phrase. “Exactly.”

Marla’s eyebrows rose.

“It was an automated workflow,” Evan continued, gaining speed. “The system attempted to reconcile availability across multiple calendars, encountered a duplication event, and propagated the conflict.”

Paul looked impressed. “That can happen.”

Evan nodded. “Frequently.”

“It can?” Marla asked.

“Not frequently,” Evan said. “But meaningfully.”

The room went quiet except for the hum of the air conditioner.

Marla studied him for a long moment. Then she opened the calendar on her tablet. “So you’re saying the system generated the meeting?”

“Yes.”

“And added the equipment mailbox?”

“Yes.”

“Why?”

“Operational coverage.”

Paul nodded again, as if operational coverage were something he personally had been missing.

Marla’s thumb moved across the screen. “Then why did you name it Strategic Touchpoint?”

Evan felt the trap closing.

“Because the system uses naming conventions.”

“You named it.”

“Under pressure.”

“What pressure?”

Evan glanced around the room. The mints sat in their bowl, each one wrapped in clear plastic, each one offering the same false promise of freshness.

“Time pressure,” he said.

Marla leaned back. “All right. We’ll call it a sync error.”

Evan exhaled.

“But you’re still attending this meeting,” she added. “And I’m going to review your schedule every morning for the next two weeks.”

His relief folded neatly into a new problem.

“Every morning?”

“Just until the errors stop.”

“I understand.”

Marla looked at the tablet again. “Also, your deep-work block begins at 7:45.”

“I’ve been trying to start earlier.”

“Were you here?”

“No.”

“Then move it.”

Evan reached for his laptop. “I can do that now.”

“Don’t. We’ll do it together after the meeting.”

The meeting continued. Evan took notes with impressive speed, though most of them consisted of phrases like “follow up,” “clarify ownership,” and “ask Dave.” He nodded at appropriate intervals. He even made one comment about protecting momentum, which Marla wrote down.

By the time the meeting ended, Evan had acquired three action items, one follow-up call, and a calendar review scheduled for the next morning.

He returned to his desk at 10:18. His original plan had been to spend the morning appearing unavailable. Instead, he had spent ninety-six minutes being available to everyone.

Dave looked up. “How was leadership?”

“Strategic.”

“Did you touch anything?”

“Several priorities.”

Linda swiveled in her chair. “Marla told Paul the calendar had a sync error.”

Evan sat down. The chair squeaked beneath him, a tiny protest from office furniture that had seen too much.

“It did,” he said.

“Marla also said she’s reviewing your schedule every morning.”

Evan opened his calendar. The blocks were still there, bright and confident. Underneath them, a new invitation waited.

Calendar Integrity Review.

Organizer: Marla Whitcomb.

Required attendee: Evan Brooks.

Time: 8:00 a.m.

He stared at it while the clock on the wall clicked toward payday, one minute at a time.

Then another notification appeared.

Strategic Touchpoint (2) had been rescheduled by the equipment mailbox.

New time: tomorrow, 8:00 a.m.

Evan looked across the office at the shared calendar screen.

The red warning returned.

DOUBLE-BOOKING DETECTED.

End of chapter one. 11 more chapters and about 25,882 words in the full book.