Misstepping
882 Words
The artefact was flawless.
That, too, was the problem.
Alicia worked through the evening with focused intensity, refining the dependency map, annotating risk mitigations, embedding user‑centric logic that made the entire workflow resilient rather than rigid. By the time she finished, the document didn’t just solve the immediate problem.
It anticipated the next three.
She reviewed it once. Twice. Checked formatting. Sanitised language. Removed identifiers.
Then, distracted by a message from Natalie-You alive?-she missed the one thing she never missed.
A comment.
Buried deep in the document’s version history.
Alicia uploaded the file and sent the link to the project team, copying Nate out of habit rather than intention.
Done.
She shut her laptop and moved through her routine mechanically, shoes aligned, kitchen reset, lights dimmed. The familiar motions usually calmed her.
That night, they didn’t.
***
Nate saw it the next morning.
Not immediately.
He reviewed the artefact the way he reviewed everything, thoroughly, methodically, with an eye for structure rather than surface. He followed the logic easily. It was elegant. Comprehensive.
Too comprehensive.
He opened the version history out of curiosity more than suspicion.
And there it was.
A single comment, time‑stamped just before finalisation.
“This mirrors the SAP Energy rollout in 2014-same user resistance pattern, same mitigation strategy. Don’t escalate; redesign the feedback loop instead.”
Nate stared at the line.
SAP Energy. 2014.
That wasn’t a casual reference.
That was a fingerprint.
He scrolled back through previous deliverables. Training content. Risk frameworks. Data reconciliation logic. Threads he’d half‑noticed before, now resolved themselves into something unmistakable.
This wasn’t just experience.
This was authorship.
He closed the document slowly.
***
Alicia knew something was wrong the moment she saw him.
He didn’t approach her desk. Didn’t send a message. Didn’t hover at the edge of her awareness the way he usually did when something didn’t add up.
He waited.
At 10:45, she found him standing in one of the smaller conference rooms, glass walls clear, door open. Neutral ground.
“Alicia,” he said as she passed.
She stopped.
“Yes?”
“Do you have a moment?”
Her instincts flared, not panic, but precision. This was the moment where the system either held or failed.
She stepped inside. “Make it quick.”
He closed the door, not fully, just enough to dampen the noise outside.
“I was reviewing the artefact you sent last night,” he said.
“Yes.”
“There’s a reference in the version history.”
Her chest tightened, sharp and immediate.
“I should have cleaned that up,” she said evenly.
“That’s not what I’m asking.”
She met his gaze, posture perfectly neutral. “Then ask something else.”
He didn’t raise his voice. Didn’t lean in. Didn’t push.
“How were you involved in the SAP Energy rollout in 2014?”
The room seemed to contract around them.
Alicia did not answer immediately.
She should have deflected. Redirected. Reasserted distance.
Instead, she said, “I was adjacent to it.”
Nate’s expression didn’t change. “Adjacent how?”
There it was.
The line.
She crossed it without meaning to.
“I helped design the mitigation strategy when escalation failed,” she said. “Unofficially.”
Silence.
Then, carefully, “Unofficially in what capacity?”
Alicia felt the walls closing in, not from him, but from herself. From the sudden awareness that she had stepped out from behind the façade without checking her footing.
“That’s not relevant to this project,” she said.
“Isn’t it?” he asked quietly.
She straightened. “No.”
Nate held her gaze, searching, not for dominance, not for leverage, but for coherence.
“You’re not just implementing,” he said. “You’re referencing decisions that predate most of the frameworks we use now. You speak with authority you don’t claim. You solve problems before they’re acknowledged.”
She said nothing.
“You told me you’d been doing ERP work for over a decade,” he continued. “That was true. You didn’t tell me how.”
Her voice was cold now. Controlled. “I told you what was necessary.”
“And what you omitted?” he asked.
She stepped back, creating physical distance. “This conversation is over.”
Nate didn’t move to block her.
“Did I do something wrong?” he asked.
The question landed harder than accusation would have.
“No,” she said.
“Then why does it feel like I crossed a line?”
Because you’re too close, she thought.
Because I miscalculated.
Because I let myself forget why the walls exist.
“Because curiosity isn’t consent,” she said aloud. “And access isn’t entitlement.”
His jaw tightened, not with anger, but hurt.
“I haven’t assumed entitlement,” he said. “I asked for clarity.”
“You don’t get clarity,” she replied. “You get deliverables.”
The words were sharper than she intended.
They hung between them, brittle.
Nate exhaled slowly. “Alright.”
He stepped aside, opening the door fully.
“For what it’s worth,” he added, “I wasn’t trying to expose you. I am trying to understand you.”
She brushed past him without responding.
- Writer
- chap_listContents
- likeADD