Rami Hammouri on Turning Complex Ideas Into Working Systems

Big technology projects rarely fail because people lack ideas. More often, they struggle because too many priorities compete for attention, timelines shift, and technical decisions become disconnected from the people who actually have to use the system.

Rami Hammouri has spent much of his career working inside that complexity. A former Director of IT Infrastructure, Hammouri has led enterprise technology projects where the challenge was not simply choosing the right technology. It was figuring out what mattered most, what could wait, and how to keep teams moving when the original plan stopped making sense.

That approach was shaped early in his career by one particularly demanding telecom project.

How Rami Hammouri learned to manage complex IT projects

Hammouri earned a bachelor’s degree in Computer Information Systems and built his career around IT infrastructure, enterprise systems, and large technology initiatives.

Early on, he was tasked with helping lead a major telecom upgrade for an enterprise call centre. The vendor estimated that a project of that size would normally require about 18 months.

The business needed it completed in eight.

Then another problem appeared. The vendor’s primary project manager became seriously ill during the deployment, leaving Hammouri responsible for much more of the project than originally expected.

“I had to step up and directly manage every moving piece of the project, from vendor coordination and technical logistics to cross-functional stakeholder alignment,” Hammouri says.

Trying to compress an 18-month plan into eight months without changing anything would have created unnecessary risk. Hammouri decided the project itself needed to be redesigned.

Why phased rollouts can work better than a big launch

The first change was to abandon the idea of launching everything at once.

Hammouri divided the project into phases and worked with call centre leadership to identify which functions were essential to daily operations. Features that were useful but not immediately necessary were moved into later stages.

That distinction became critical.

“When everything feels urgent, you still have to identify what is truly business critical,” he says. “Otherwise, you put pressure on the entire project without improving the outcome.”

He also introduced daily meetings with technical teams, established direct communication with vendor engineers, and created clear progress reporting for leadership.

The core telecom infrastructure went live by the eight-month deadline without disrupting call centre operations. Less critical features were introduced later.

The experience changed the way Hammouri thought about bringing large ideas to life.

What makes a technology project successful?

For Hammouri, completing a project is only one measure of success.

He looks at three areas: measurable results, stakeholder experience, and the quality of the work itself.

“Success means setting clear goals and delivering measurable, high-quality results,” he says. “It’s not just about crossing the finish line. It’s ensuring the outcome actually solves the underlying problem.”

That could mean improving efficiency, reducing friction for employees, meeting a deadline, staying within budget, or creating something end users actually trust.

It also means asking whether the process left the team stronger.

Hammouri pays close attention to feedback from colleagues, technical specialists, stakeholders, and mentors. Two mentors in particular have remained important influences throughout his career.

He sees feedback as part of the work rather than something reserved for the end of a project.

How do you solve a technology problem when the plan breaks?

Another project reinforced that philosophy when Hammouri encountered a compatibility issue between an older system and a new tool being introduced.

The problem threatened to stop progress for weeks.

Instead of simply waiting for an outside fix, Hammouri worked with technical leads to understand the workflow in detail. The team developed a temporary workaround that allowed data to continue moving securely while the underlying issue was addressed.

A permanent fix followed later.

“The experience taught me the value of staying calm under pressure, digging into root causes, and keeping cross-functional communication wide open,” he says.

That combination of technical curiosity and practical decision-making has become central to his approach.

Why prioritisation matters in IT leadership

Technology teams are often asked to do more than time and resources realistically allow. Hammouri believes one of the most useful leadership skills is knowing what not to do yet.

He starts by defining the goal, the hard deadline, and the constraints. He then separates work that is merely urgent from work that will have the greatest impact.

Large objectives become smaller operational milestones, with clear ownership and regular check-ins.

That structure still leaves room to change direction.

“Once I master a role or land a major win, I actively seek out harder problems, larger scopes, or unfamiliar territory rather than repeating the same successful playbook,” he says.

Outside of technology, Hammouri enjoys camping, fishing, and hiking with his children. The slower pace offers a contrast to enterprise IT, but the appeal is similar: prepare carefully, stay aware of changing conditions, and adjust when the path in front of you looks different than expected.