Olivia Brown pushed open the glass doors of the openplan office in Shoreshore just before nine, and a habit of hers made her pause, noting how the space had been stripped of its old steel filing cabinets and replaced with sleek glass partitions and monitortopped desks on rolling stands. By the long window table a handful of screens flickered, a developer hunched over a keyboard with headphones glued to his ears.
She slipped off her coat, draped it over the back of her chair, booted up her laptop and opened the days agenda. In bold type the top task stared at her: Onboard interns Mentor: Olivia. Beneath it three surnames she had memorised the night before while nursing a cold brew at home.
At fortyfive, Olivia was older than most of the clientprojects team, but it felt less like a sentence than a settled fact. She remembered five years earlier, when the firm was still fumbling with the rollout of a new CRM, and how everything seemed to be moving too fast. Shed pulled herself together then, and now she was the one showing newcomers where to click and what to leave untouched.
The interns were due at ten. Before that she needed to finish the report for the finance director and print a few simple process diagrams shed sketched the previous afternoon plain flowcharts, not flashy animations, just who does what, when.
She already had three folders of basic instructions laid out on her desk, with notepads and pens within reach. She inhaled, doublechecked the names, and reminded herself she hated being addressed as hey, you.
The first to appear was a tall woman in a pale sweater, a battered backpack slung over one shoulder. She peeked cautiously into the department and halted at the entrance.
Good morning. I think Im here for you. Im Emma, she said, a nervous smile tugging at her lips.
Come in, Emma. Im Olivia, Olivia replied, standing to shake her hand. Take a seat over there, right next to me. The others will be here shortly.
A few minutes later a young man in a checked shirt and a short crop haircut entered, a laptop case tucked under his arm.
Hi. Im Jake, he said, scanning the desks. Im on the projectmanagement apprenticeship.
Exactly, Jake. Have a seat.
The third arrived petite, darkhaired, in a black blazer and trainers. She walked in with confidence, though a flicker of tension crossed her eyes.
Morning. Im Poppy. Im here too, she said, pulling a notebook from her bag.
Olivia glanced at the trio, felt a faint smile rising. They were younger than her eldest son, and that struck her as both odd and familiar: fresh faces, a new cycle.
Glad youre on time, she said. Lets get started. Today is an induction. Ill explain what the department does, what we expect from you, and you can ask anything. Then well look at current projects and see where you might fit.
Her voice was steady, the words fitting a wellworn script, yet each new group made her shift the emphasis slightly. The world around them was evolving, and they needed a firm footing, not just a rulebook.
First, a few ground rules, she continued. Number one: if you dont understand something, ask. There are no stupid questions. Pretending everythings clear and then breaking a project is the real folly. Number two: we dont live in chat. Written communication is important, but complex matters are discussed by voice. Walk over, or hop on a call. Number three: you own what you promise. If you see a deadline slipping, speak up early. Thats not failure, thats just work reality.
Jake nodded, already opening his laptop. Emma scribbled each rule diligently. Poppy fixed her gaze on Olivia, as if matching the words to an internal checklist.
Will we have a common chat? Emma asked. Just to sort out the little things quickly.
Absolutely, Olivia replied. We have a channel on our corporate messenger. Ill add you. Remember, chat is a tool, not a life.
She gave a brisk overview of the companys structure, its key clients, and the way projects are built. She skipped the long history of the brand and instead shared two concrete anecdotes: one where a contract error spotted just in time saved a deal, and another where a team missed a deadline because they were too proud to admit confusion.
Our job isnt to pretend everythings under control; its to actually keep it under control, she summed up. Thats the foundation of client trust and team cohesion.
After the briefing they toured the office. Olivia pointed out where the analysts sat, where the accounts team worked, and where the meeting rooms were. She introduced colleagues, offering brief explanations of each role. The interns exchanged shy greetings, curiosity flickering in their eyes rather than fear.
When they returned to her desk it was nearly noon. Olivia opened the corporate taskmanagement system and projected the project list onto the main screen.
We have three streams you could jump into, she said. First, a rollout of a new service for a large retail chain lots of routine work but youll see the whole cycle. Second, a pilot with an online platform where things move fast. Third, an internal processoptimisation project.
Id like the pilot, Jake said straight away. Im keen on testing in a live environment.
Noted. Emma?
I think Id prefer something more structured, Emma replied cautiously. Maybe the retail rollout. I like having a clear plan.
Alright. Poppy?
The internal project, Poppy answered without hesitation. I want to understand how things work inside, not just outside.
Olivia logged their choices, already picturing how to balance their time so nobody felt superfluous or buried in minutiae.
In the weeks that followed, the interns fell into the rhythm. Olivia met with each individually, unpacking tasks, showing the correct way to correspond with clients, and how to log agreements. She stressed the importance of being precise about what will be delivered and by when, rather than overpromising.
But if you sound too harsh, the client might take offense, Emma remarked, rereading a draft email.
You can be clear and still be polite, Olivia replied. Instead of we cant do that, say we propose this alternative. You guide, you dont push away.
Emma rewrote the line, her shoulders relaxing just a fraction.
Meanwhile Jake was already navigating the new platforms interface, demonstrating to Olivia how to pull user reports and build simple dashboards.
Could we push these metrics straight to the team channel, so everyone sees the trend? he asked one day. I could script a quick update that runs each morning.
Olivia listened, not pretending she knew every detail.
If it doesnt breach security or break anything, lets try it, she said. First, run it by IT and the security team.
They approached the sysadmin, discussed the idea, and Jake explained his plan clearly. Olivia asked clarifying questions, ensuring nothing was left vague. Within a couple of days the script was live, and tidy daily summaries began appearing in the channel. Colleagues thanked them, some dropped an emoji, and Jakes posture visibly relaxed.
Poppy threw herself into the internal project, quickly mastering employee surveys and suggesting they be anonymous for honesty.
Can we add a couple of questions about how they use our tools? she asked in a meeting. Many dont even know half the features.
Sure, Olivia replied. Just phrase it so no one feels stupid.
Together they reworded the items. Olivia noted how swiftly Poppy picked up the nuances. At her age she often felt she was the one catching up, yet she now appreciated how vital tone was, even in a questionnaire.
The exchange was twoway. When Olivia opened the task spreadsheet and began manually adjusting deadlines, Jake nudged gently:
Did you know you can automate that? There are templates and dependencies that recalc dates automatically.
She stared at the screen, a flicker of annoyance at her own extra work, but also gratitude.
Honestly? I havent looked into it, she admitted. Show me?
Jake sat beside her, explained everything in plain language, no jargon. Fifteen minutes later Olivia was linking tasks herself, feeling a mix of irritation at wasted effort and relief at the newfound efficiency.
Why didnt you say earlier? she asked.
I thought youd prefer I didnt intrude, Jake stammered. I didnt want to overstep.
Dont hold back, Olivia said gently. If you see an improvement, speak up. Its help, not criticism.
Days slipped by. Spring light grew brighter, people shed coats, and the office buzzed a little louder each morning.
By the middle of the second month a major project loomed: senior management had signed a contract with a national pharmacy chain, and a threeweek deadline was set to launch a loyalty service. The client was demanding, the timeline tight, the system still in beta.
At the department meeting the director spoke:
Olivia, youll lead. Bring the interns in if you think it helps, but keep the deadline in sight. The client is highvalue.
She nodded, feeling that familiar knot in her shoulders. Shed been through similar storms; the difference now was that three fresh eyes were beside her, each under her mentorship.
After the meeting they gathered in a small conference room. Printed requirements lay on the table, laptops open, the citys rooftops visible through the window.
The situation is this, Olivia began. Weve got three weeks to roll out a loyalty program for the pharmacy chain. We need to configure the system, integrate it with their POS, train staff, and test on real sites. The client is tough but reasonable. Mistakes will happen, but we must ensure they dont affect shoppers.
I can take the testing side, Jake said immediately. And I could set up alerts for the pharmacies so they see any failures instantly.
Noted. Emma, youll handle client communication draft emails, meeting minutes, keep the task board tidy. Ill be nearby but I want you to own it, Olivia instructed.
Emma swallowed, then nodded.
Alright.
Poppy, youll run internal coordination. Gather status updates, prepare short briefs for the director. He needs a clear picture, not a novel.
Got it, Poppy replied. Can I also draft a quick guide for the pharmacy staff what to do if something fails?
Great idea.
The first days were relatively smooth. The client sent over specifications, the team configured the platform, tested scenarios. Olivia ran several calls a day, logging agreements and assigning tasks. She stayed a bit later each evening, doublechecking everything.
In week two small glitches appeared. One pharmacy wasnt crediting points, anothers checkout froze when a discount was applied. The team fixed the bugs, the client grew uneasy, but progress continued.
The climax hit unexpectedly. Friday evening, three days before the launch, a frantic message popped up in the client chat: Four sites are dead. No points, POS errors. Tomorrow we have a massive promo. This cant happen.
Olivia felt the room collapse inward. She was about to close her laptop and head home. Her hand froze above the bag. She sat back down, took a breath, and spoke aloud, though the office was empty.
Okay, breathe.
She called the clients point of contact, let him vent, recorded every complaint, then repeated back the issues and proposed a plan: assemble the team now, give an hourlong status, run overnight tests, reconvene at nine.
She hung up and dialed Jake.
Did you see the message? she asked.
Yes, he replied. Im already pulling the logs. Looks like an integration hook broke.
Good. Jump on the group call in fifteen minutes. Ill pull Emma and Poppy in too.
Fifteen minutes later they were huddled in the almostempty conference room. Outside the sky was darkening, the hallway silent.
This is unpleasant, but not catastrophic, Olivia began. First rule: no panic. We need to pinpoint the failure and see what we can fix before morning.
Ive traced it, Jake said, swivelling his screen toward them. During a library update the configuration for the pharmacy module was wiped. We can restore it, but we need time and then run tests.
How much time? Olivia asked.
Three to four hours if I stay focused, plus testing.
Alright. Emma, draft a client email outlining our action plan no excuses, just facts and timelines. Can you do a quick draft for me to review?
Emma inhaled deeply. Yes. May I write it first and then you check?
Of course. Poppy, put together a concise status for the director clear, calm, factual.
They split up. Olivia felt the tension like a stretched string, ready to snap. She knew it would be easy to point fingers, but that would solve nothing for the client or the interns.
Twenty minutes later Emma returned with a laptop.
May I? she asked.
Olivia read the email. It still carried a hint of uncertainty, but the structure was sound. She trimmed a few apologies, added firm deadlines, and sent it off with a copy to herself and the director.
Poppy handed over a threebullet briefing: what went wrong, what were doing, and the risks.
Send that to the director as well, Olivia said. Copy me.
Night wore on. Jake stared at code, muttering his thought process aloud as he ran checks. Olivia helped verify scenarios, suggesting which sites to prioritise. Emma kept the client looped, answering followup questions. Poppy updated the internal dashboard so no one would wake up to a surprise.
Around two in the morning Jake leaned back.
Looks like were done, he said. The three pharmacies weve tested are clean. Two more to go, but no errors yet.
Olivia felt the pressure ease slightly.
Run those last two tests, then well send a midnight update to the client. A full report in the morning.
When the final tests passed, they fired off a short confirmation to the client. Olivia closed her laptop, looked at the three interns, and said, Well done today, all of you.
Honestly, I expected you to yell at us, Emma whispered, relief in her voice. We missed something, didnt we?
Olivia smiled. Shouting doesnt fix systems. Mistakes are part of the process. What matters is that we see them and correct them. If youd run away and pretend nothing was happening, thered be a reason to shout.
They dispersed to their homes just after three. Olivia took a taxi, fatigue weighing her limbs, but her mind already mapped tomorrow: a morning call, a director report, a debrief.
At dawn, as she slipped back into the office, the clients phone rang. The tone was still tight, but the edge had softened. Olivia calmly outlined the nights work, the tests completed, and the contingency plan. The client thanked her, noting the swift response.
She gathered the team around her desk.
The clients still on edge, and thats normal, she said. But they see were not hiding. Today we need to sweep every critical point again, doublecheck, and stay reachable.
Can I set up monitoring so we get alerts for specific errors? Jake asked. So we dont wait for the client to call.
Yes, do that. Just run it past IT first.
Emma suggested a short checklist for pharmacy staff to run before calling in support. Poppy refined the internal report, adding a lessons learned section from the nights incident.
By days end the system held. Minor hiccups appeared, but nothing catastrophic. The client sent a brief note: Thanks for the rapid fix. Lets keep moving.
Olivia felt a quiet click inside not triumph, but a deep satisfaction. Theyd weathered a crisis together and hadnt fallen apart.
A few days later, at the weekly planning meeting, the department head singled out the interns.
I want to thank the new team, he said. You didnt bolt at the first fire.
The interns smiled sheepishly. Olivia watched them, thinking how crucial it had been that she hadnt tried to solve everything alone. It was risky, but it forced the newcomers to own responsibility.
After the meeting they returned to their desks, the hum of work settling back into its usual rhythm. Someone joked in the chat, someone else floated a new task.
Olivia, Poppy called softly. Can I have a minute?
They stepped to the window.
I just wanted to say thanks for how you lead us, Poppy began. At my previous placement the mentor just dumped tasks and vanished. Here it feels different.
Olivia shrugged lightly. I need you as much as you need me, she replied. You see things I miss. Those survey tweaks, for example Id have made them far more formal.
Just our habit, Poppy laughed. But without your framework wed drown.
Jake later approached with a printed sheet.
Ive drafted a proposal to automate department reports,Jake handed the sheet to Olivia, his eyes bright with optimism, and said, If we get this approved, the whole team will spend hours each week on real work instead of chasing numbers.