Ron Yeffet has managed concrete superstructures, power plants, and major roadways across four continents. He explains how military discipline, long-term thinking, and rigorous planning shape infrastructure that defines communities for decades.
Ron Yeffet is President of R & I Trading, a New York-based real estate development and infrastructure enterprise. Over more than 25 years, he has managed projects across the United States, Israel, Europe, and Africa, including concrete superstructures, energy supply systems, power plants, and major roadways. His work is rooted in a belief that infrastructure should outlast the people who build it, and that discipline is embedded in every decision made before ground is broken. Born in Jerusalem in 1966, he served 37 months in the Israeli Defense Forces as a Major Sergeant in the Artillery and Bomb Squad Unit before moving to the United States to begin his career in development. He is based in New York and Jerusalem.
How did your time in the Israeli Defense Forces shape the way you approach infrastructure projects today?
The work was exacting. There was no margin for improvisation. Details were not ornamental, they were the difference between completion and catastrophe. You learn very quickly that details matter. In that environment, there is no room for shortcuts. I learned to plan with precision, to execute without hesitation, and to trust the process even when the outcome was not yet visible. That discipline carried over into everything I do now. Discipline is not something you turn on later. It becomes part of how you think and act every day. When I plan a project, I do not rely on spontaneity or instinct. I rely on structure. Every phase is mapped in advance. Contingencies are planned. Risks are assessed. Teams are briefed. The goal is not to eliminate uncertainty, but to reduce it to a manageable level so that when problems arise, and they always do, the system can absorb them without collapsing.
You started in New York City real estate with no network and no formal business training. What did you rely on instead?
I had a direction and a willingness to work. I did not have a perfect plan. I had a direction and a willingness to work. New York real estate is unforgiving. High stakes, narrow timelines, tight margins. You are coordinating across contractors, engineers, municipal agencies, and financiers. The work is not glamorous. It is methodical. Every project taught me something about how systems function under pressure, how teams respond to complexity, and how trust is earned through consistency. I never wanted to stay in one lane. Every project teaches you something new, and that knowledge compounds over time. That is how the scope expanded. New York first, then New Jersey and Pennsylvania. Then Israel. Then Italy. Then parts of Africa. The projects grew in scale and ambition. Concrete superstructures, energy supply systems, power plants, major roadways. These are the backbone of regional infrastructure, the kind of work that shapes how entire communities function for decades.
If the plan is weak, the outcome will be weak. Strong planning allows the team to execute with confidence.
What do people consistently get wrong about your work?
They think big ideas are the hard part. Big ideas are easy. The hard part is turning them into something real. Anyone can propose a power plant or a major roadway. The question is whether you can deliver it. That requires planning, coordination, technical expertise, and the ability to manage complexity over years, not months. People also underestimate how much infrastructure work is about relationships. You are working across governments, private entities, local communities. Trust is built over time, through consistent delivery and transparent collaboration. Relationships are built on trust and results. If you deliver consistently, people want to work with you again. In infrastructure, where projects can span years, that trust becomes currency.
You have worked in regions with political complexity and logistical constraints. What is the first thing you assess when entering a new environment?
Who the local experts are and whether they are reliable. I operate through a hybrid model. In-house leadership, trusted external partners. Depending on the region and the nature of the project, specialized teams are brought in. Engineers, contractors, local experts. The structure allows for flexibility without sacrificing control. I need to know who understands the regulatory environment, who has the technical capability, and who can navigate the cultural and political realities of that place. If you do not have the right people, the project will not succeed. Great projects are never done alone. You need the right people, and you need to trust them. I value expertise and I delegate accordingly. I do not micromanage, but I do hold teams accountable to the standards established at the outset.
What is a mistake you believed was avoidable early in your career that you now see as part of the learning process?
I used to think that if the plan was detailed enough, you could avoid most problems. That is not true. You can reduce problems, but you cannot eliminate them. Projects are complex. Variables shift. What I learned is that the plan is not there to prevent every problem. It is there so that when problems arise, you have a system that can absorb them. The mistake was thinking that planning was about perfection. It is not. It is about resilience. You build the structure so that when something breaks, the whole thing does not collapse. That took time to understand, and I do not think you can teach that in a classroom. You have to live through a few projects where things go wrong and see how the system holds or does not hold.
What changed in your work when you stopped treating infrastructure as a series of projects and started treating it as long-term commitment?
The timelines got longer, but the work got better. Infrastructure is not something you build quickly. It is about building something that works for decades. When you build a community, you are building something that continues long after the project is done. It creates stability and connection. I started thinking about what happens five years after completion, ten years after, twenty years after. Who maintains it? How does it integrate with future development? What happens if the region grows faster than expected? Those questions changed the way I plan. They also changed the way I choose projects. I am less interested in short-term returns and more interested in whether the work contributes something lasting to the environment and the communities within it.
Infrastructure is not just about building something quickly. It’s about building something that works for decades.
What actually improved the quality of your work over the last decade?
Better planning tools and better partnerships. The tools allow you to model scenarios, assess risks, and coordinate teams in real time. The partnerships allow you to bring in the right expertise at the right moment. I also got better at saying no. Not every project is worth doing. Some projects look good on paper but do not have the structural support to succeed. Weak plans produce weak outcomes. If the foundation is not there, politically, financially, technically, I walk away. That discipline has improved the quality of everything I take on. If the plan is weak, the outcome will be weak. Strong planning allows the team to execute with confidence.
What is overrated in infrastructure development right now?
Speed. There is pressure to deliver quickly, to cut timelines, to show results. That pressure often leads to shortcuts, and shortcuts create long-term problems. Infrastructure is not a sprint. It is a marathon. You are building something that has to function for decades, not just pass an inspection at completion. I would rather take an extra year in planning and deliver something that lasts than rush to a ribbon-cutting and deal with failures later. The other thing that is overrated is novelty. People want the newest technology, the newest design, the newest materials. Sometimes that is right. Often it is not. Sometimes the proven approach is the better approach. You have to know the difference.
What part of infrastructure work do you think technology can take over in the next ten years, and what part will still require human judgment?
Technology can take over modeling, risk assessment, and a lot of the coordination logistics. It can simulate scenarios faster than any team could manually. It can flag risks before they become problems. It can manage timelines and budgets in real time. What it cannot do is build relationships. It cannot read a room. It cannot make the judgment call when two good options are on the table and you have to choose based on context, not data. It cannot negotiate with a government official or a local community leader. Those are human skills, and they are not going away. The best projects will use technology to handle complexity and free up human judgment for the decisions that actually require it.
You work across the United States, Israel, Europe, and Africa. How does your approach change depending on the region?
The principles do not change. Planning, discipline, teamwork, long-term thinking. Those are consistent. What changes is how you apply them. In some regions, the regulatory environment is more predictable. In others, it shifts frequently and you have to adapt. In some places, local expertise is highly developed. In others, you bring in more external support. Cultural differences matter. Political stability matters. Infrastructure readiness matters. You have to assess each region on its own terms and build the project accordingly. But the foundation is always the same. If you do not plan properly, if you do not build trust, if you do not think long-term, the project will fail no matter where you are.
Great projects are never done alone. You need the right people, and you need to trust them.
What advice would you give to someone starting in infrastructure development today?
Learn to plan before you learn to build. The industry rewards people who can manage complexity, and complexity starts in the planning phase. Understand how systems work. Understand how teams function. Understand how governments, private entities, and communities interact. Do not chase the biggest project. Chase the best project. The one where the planning is solid, the partners are trustworthy, and the long-term impact is real. Also, do not expect quick results. This is a field where success is measured over years, not quarters. If you are looking for fast returns, go somewhere else. If you want to build something that lasts, stay disciplined and stay patient.
What stays true in infrastructure development no matter how much the industry changes?
Planning matters. Relationships matter. Long-term thinking matters. Those three things will be true in ten years, in fifty years. The tools will change. The materials will change. The regulatory environments will change. But if you do not plan properly, if you do not build trust, and if you do not think beyond the next year, your work will not last. Infrastructure is not about building something quickly. It is about building something that endures. That has always been true, and it will always be true.
