March 30, 2030.
Elena did not announce her acceptance with enthusiasm.
She sent an email.
Six sentences. No attachnts. No congratulations to herself.
I’ll take the role under the mandate discussed. Effective imdiately. First priority: staffing discipline. We do this quietly.
Timothy replied with a single line.
Agreed. Proceed.
That was how TG dSystems moved from an idea protected by structure into sothing that had weight. Not by expanding. By narrowing. By deciding exactly who was allowed inside.
The next two weeks were not spent interviewing in bulk. There was no job blast. No recruitnt firm paid to flood inboxes. Hana and Elena built the list themselves, line by line, function by function, with a whiteboard that stayed deliberately incomplete.
They started with absences rather than titles.
"What breaks first if it’s missing," Elena asked, marker in hand.
"Regulatory continuity," Hana said imdiately.
Elena wrote it down. Regulatory affairs lead.
"What else."
"Quality," Timothy said. "Not just compliance. Quality that understands manufacturing reality."
Quality systems lead.
"Service," Elena added. "Field engineers who’ve actually fixed devices under pressure, not just certified them."
Service operations head.
The board filled slowly. Not with nas, but with constraints.
No one whose last role was purely sales-facing.
No one who needed a hospital to validate their authority.
No one whose resu peaked during a growth bubble.
They weren’t building a startup. They were assembling a failure-resistant organism.
The first call went to a man Elena had crossed paths with years earlier during a joint recall investigation. His na was Victor Ramos. Mid-fifties. Regulatory affairs by training, quality auditor by reputation. He had a habit of saying very little and writing very long mos that people hated until they saved companies from fines.
Victor joined the video call from a quiet room with no visible branding behind him.
"You’re forming a dical device manufacturer," he said without greeting.
"Yes," Elena replied.
"In the Philippines," he added.
"Yes."
"And you want soone who will slow you down," he said.
Elena nodded. "Repeatedly."
Victor considered that.
"You understand that if I do this correctly," he said, "your engineers will complain about within six months."
"They’re supposed to," Elena replied.
"And your executives will occasionally think I’m being difficult."
"I will support you," Timothy said, speaking for the first ti.
Victor looked at him carefully.
"Then I’ll listen," he said.
They talked for forty minutes. No hypotheticals. Just situations.
An undocunted supplier change.
A calibration lapse discovered late.
A regulator asking the wrong question at the wrong ti.
Victor didn’t posture. He answered with process.
At the end, he asked one question.
"Do you want approval speed," he asked, "or approval durability."
"Durability," Elena replied imdiately.
Victor nodded. "Then send your QMS draft. I’ll tell you where it lies to you."
That was his acceptance.
The next role took longer.
Service operations was harder to staff because it sat between engineering arrogance and hospital reality. Elena refused to hire soone who hadn’t worn both hats.
They interviewed five candidates. Four were cut quickly.
Too polished.
Too theoretical.
Too eager to scale before stabilizing.
The fifth arrived late to the interview, apologized once without excuses, and imdiately asked where the service manuals would live.
Her na was Maria Velasco.
She had spent twelve years running regional service teams for imaging and monitoring devices. Her resu showed no promotions that made headlines, but a steady expansion of responsibility across increasingly underfunded environnts.
"I don’t care how good your device is," she said early in the conversation. "If spare parts take three weeks and your engineers don’t answer phones, hospitals will blacklist you quietly."
"That’s consistent with our assumptions," Hana said.
Maria leaned forward. "Assumptions don’t fix outages."
"Then what does," Timothy asked.
"Redundancy and humility," Maria replied. "And engineers who are allowed to say ’I don’t know’ without being punished."
She walked the floor with Elena later that day, stopping in the service training area and frowning.
"This needs lockers," she said. "Field engineers carry their work on them. Tools, ters, laptops. If they don’t trust storage, they don’t trust the company."
Elena made a note.
"And your training schedules," Maria continued. "They need to be boring. Sa weeks. Sa slots. Hospitals plan around predictability, not excitent."
At the end of the walk, Maria turned to Elena.
"You’re serious about service," she said.
"Yes," Elena replied.
"Then I’ll join," Maria said. "But I won’t make it pretty."
"Good," Elena said. "We don’t want pretty."
Quality systems ca next.
This role nearly caused friction.
One candidate ca highly recomnded from within TG Holdings. Impressive credentials. Familiar face. Safe.
Elena rejected him.
"He’s used to systems where quality is a checkbox that exists to protect production," she said privately to Timothy. "That doesn’t work here."
They found their answer in soone almost no one knew.
Jun Alonzo. Forr manufacturing quality lead at a contract device manufacturer that had never had a major recall but had also never chased aggressive growth. His resu was short. His references were blunt.
"He’s boring," one forr colleague said. "But nothing ever slips past him."
Jun’s interview lasted an hour and felt longer.
"What do you do when production wants to ship despite unresolved anomalies," Elena asked.
"I stop the line," Jun said.
"And if they escalate," Hana pressed.
"I docunt everything and wait," he replied. "Soone eventually realizes shipping bad devices costs more than delays."
"And if they don’t."
"Then they fire ," Jun said. "Which hasn’t happened yet."
That was enough.
Engineering hires ca last.
Deliberately.
They did not hire brilliant generalists. They did not hire founders-in-waiting.
They hired people who hated rework.
A power electronics engineer who had spent a decade designing modules that ran hotter than expected because hospitals never kept rooms at spec.
A firmware engineer who had learned to log everything because logs saved him in audits.
A systems integrator who spoke more about cable routing than algorithms.
Every engineer interviewed had to answer the sa question.
"What’s the worst failure you’ve been responsible for."
Anyone who deflected didn’t pass.
One candidate admitted to shipping a monitoring subsystem that failed under humidity conditions they hadn’t simulated properly. The fix took six months and a recall notice.
"What did you change," Elena asked.
"I stopped trusting lab conditions," the engineer said. "Now I assu reality is worse."
He was hired.
By the end of the month, TG dSystems had a skeleton team.
No excess.
No redundancies beyond intent.
No one who didn’t know why they were there.
Elena called the first full-team eting on a Monday morning.
No slides. No welco speech.
She stood in the center of the open floor, tape lines still visible beneath their feet.
"This is not a startup," she said. "If you want adrenaline, you’re in the wrong place."
No one left.
"This is a manufacturing and service company operating under dical regulation," she continued. "Your job is not to impress. Your job is to prevent harm, downti, and embarrassnt."
She looked around the room.
"We will be audited," she said. "We will be questioned. We will be slow when others are fast."
No one objected.
"And if we do this correctly," she finished, "nothing we build will ever need to be explained loudly."
Timothy watched from the edge of the room.
This was the phase most companies rushed.
They hadn’t.
Instead, they had built sothing dense. Quiet. Resistant.
Not a team designed to chase growth.
A team designed to survive it.
Reviews
All reviews (0)