Programme Manager by Day, Ghost by Design
1205 Words
Alicia lived her days in layers.
Each morning, she selected which version of herself the world would be allowed to see, and each evening she folded those versions away again, creased neatly, ready for reuse. It was not deception. It was architecture. Structure. Survival.
By 08:00, she was already installed at the head of the programme floor, jacket draped over the back of her chair, sleeves rolled with quiet authority. Screens glowed to life at her command, dashboards unfolding in crisp, colour‑coded certainty. Risks tracked. Dependencies mapped. Escalations anticipated before they reached the surface.
This was the visible Alicia Brent.
Programme Manager.
She stood when people entered the room, not because she needed to, but because it set the tone. Tall, composed, unhurried. When she spoke, conversations bent toward her voice as if pulled by something gravitational rather than imposed.
“Let’s align on the critical path first,” she said, already knowing where the friction lay. “Then we’ll talk contingencies.”
No one questioned her sequencing. They never did. Her leadership had crafted a seamless, smooth, frictionless working environment and therein lay the foundation of her success.
She listened more than she spoke, but when she did speak, it was precise. She untangled competing priorities without diminishing anyone’s contribution, reframed disagreements as solvable design problems, and made decisions that felt collaborative even when they were final.
Stakeholders trusted her instinctively. Teams relaxed around her. Problems confessed themselves more readily in her presence, as if sensing they would be handled rather than judged.
It was a skill she had honed carefully.
By 09:45, the meeting concluded ahead of schedule. Actions were clear. Tension diffused. Momentum restored.
“Well run,” someone murmured as they filed out.
Alicia acknowledged it with a nod, already closing the loop in her mind. Praise, like criticism, was data. Nothing more.
At 10:00, she disappeared.
Different floor. Different access badge. Different login credentials.
She became smaller in the physical sense, no longer positioned at the centre of rooms, no longer framed by glass walls and leadership seating. Her workstation this time was tucked near a column, partially shielded by a printer that hummed unpredictably and a whiteboard no one had updated in weeks.
Training Content Developer.
A role that came with assumptions baked into it. That she followed instructions rather than gave them. That she executed rather than designed. That she translated decisions made elsewhere instead of shaping them.
Alicia embraced those assumptions fully.
She adjusted her posture subtly, softened her presence. Her voice, when she spoke, was quieter. She avoided eye contact just enough to discourage questions. When someone passed her desk, they registered her as competent background noise, useful, but not central.
Invisible by design.
She opened the learning management system and began building.
User journeys unfolded under her fingers with an elegance no one ever saw. She mapped not just what users would do, but what they would fear doing. Where they would hesitate. Where they would assume they had broken something irrevocably. She placed reassurance precisely where panic would bloom, embedded logic where confusion would spike.
It was not documentation. It was psychology.
Occasionally, someone would lean over the partition.
“Can you add a quick note here?” they’d ask, gesturing vaguely at the screen.
“Of course,” Alicia would reply, already anticipating the downstream impact of that “quick note” across six modules and three business processes.
They never saw the scope. Only the outcome.
By mid‑morning, her inbox contained two very different streams of communication. One labelled Programme Steering, measured, strategic, laced with authority. The other labelled Training Review, transactional, deferential, easily dismissed.
She responded to both with equal efficiency, tone‑shifting instinctively.
It was a dangerous balance, but one she had perfected.
At 11:30, she slipped into a project stand‑up on mute, camera off. The discussion drifted toward a data dependency that threatened the testing schedule.
“We’ll need someone to sanity‑check the migration logic,” a voice said. “Just to be safe.”
Alicia typed a brief message into the chat.
I can review the scenarios and flag risks.
No fanfare. No emphasis.
“Great,” the facilitator replied distractedly. “Thanks.”
She smiled faintly at the screen.
They had no idea.
At lunch, Alicia ate alone as usual, not out of loneliness but efficiency. She preferred meals without performance. Without negotiation. Food was fuel, not an event.
From her seat by the window, she watched the city below assemble itself into patterns, traffic lights cycling obediently, pedestrians obeying invisible rules, systems interacting with predictable friction.
She understood systems.
People were more complex, but they followed patterns too. Incentives. Fear. Validation. Power.
She had once been naïve enough to believe that contribution alone dictated outcome. That good work rose naturally to the surface. That visibility followed value.
Experience had corrected that assumption.
After lunch, she spent two hours refining training content that would later be praised in a steering committee she would not attend. Someone else would present it. Someone else would accept the nods of approval.
That was acceptable.
Preferred, even.
At 15:00, she shifted again, back into visibility for a brief executive update. She straightened her jacket, lifted her chin a fraction, re‑entered the room as if she had never left.
The executives listened.
They always did.
She spoke in outcomes and mitigation strategies, never revealing how much work lived beneath her calm summaries. When questions came, she answered without defensiveness, acknowledging risks without inflating them.
“You’re confident?” one of them asked.
Alicia met his gaze evenly. “Yes.”
Not I think so. Not I believe.
Yes.
The meeting ended with satisfied murmurs and a sense of reassurance that would ripple outward across the programme.
At 16:10, she vanished again.
By the end of the day, Alicia had been four different women and none of them fully seen.
She shut down her workstation, packed her bag, and paused briefly as she stood. Around her, the office buzzed with end‑of‑day energy, people negotiating drinks, venting frustrations, transitioning into personal lives that intersected freely with their professional ones.
She felt no envy. On the contrary, she was relieved at the simplicity she had designed for herself.
Her separation was intentional.
In the elevator, she caught her reflection in the mirrored wall. For a moment, the layers blurred. Programme Manager. Content Developer. Owner. Ghost.
All of them were her.
None of them were Vicky.
The name surfaced briefly, uninvited again, then receded. She had learned not to wrestle with memories. Resistance gave them weight. Acknowledgment let them pass.
Outside, the late afternoon sun angled low between buildings, casting long shadows across the pavement. Alicia walked with the same measured pace she applied to everything else, neither rushing nor lingering.
She had built a life where no one could take credit for her work without her permission.
A life where no one could shrink her without her consent.
A life where visibility was a choice, not a requirement.
Tomorrow, she would do it all again.
Programme Manager by day.
Ghost by design.
- Writer
